Publishing Wizard not connecting to Valid APS?

[MJRBIM]

I have two CE 8.5 servers, one development (CRYDEV)and one production (CRYSTAL) running on Win-2000 boxes with IIS. Both work fine when connecting to CMC and ePortfolio via a browser.

However, when I connect using the Publishing Wizard from my local desktop I get the following error when connecting to CRYDEV

Logon Error : Unable to connect to APS CRYDEV to retrieve cluster members. Logon can not continue.

This is not a uniform problem...

1.) I do NOT get this error when connecting to "CRYSTAL" using the Publishing Wizard from my local desktop.

2.) I do NOT get this error when connecting locally to "CRYDEV" using the Publishing Wizard from the "CRYDEV" desktop.

3.) I do NOT get this error when connecting accross the network to "CRYDEV" using the Publishing Wizard from the "CRYSTAL" desktop.

My guess is network or NT/2000 permissions - but I can't find anything different between the two "CRYSTAL" and "CRYDEV" servers.

Any advice would be appreciated.

 

[Turkbear]

Hi,
From your local desktop, can you ping CRYDEV ?

 

[MJRBIM]

Yes, I can ping CRYDEV.

Is there a way to Ping the port 6400 that the APS uses?

 

[Turkbear]

The APS name is 'connected' to the IP address of the server on which the WCS is running so a DNS lookup ( or the equivilant) should be able to 'find' CRYDEV by its name and not its address...

 

[MJRBIM]

That's true...but I don't think the Publishing Wizard tool connects using the WCS. It's not web-based, the Publishing Wizard tool is a windows 32-bit application that communicates directly with the APS.

I can add reports without problems to "CRYDEV" through the CMC web tool, but this Publishing Wizard tool will NOT connect to "CRYDEV" (it's 100% OK with "CRYSTAL&quot.

Crystal Decisions doesn't have much info on-line about how the tool connect to the APS...and the fact that it is only failing from certain desktops is also frustrating.

 

[Turkbear]

Hi,
That's right - sometimes I have a CRAFT attack
[Can't Remember a Freakin' Thing ]

The local workstation may not 'know' where the CRYDEV aps server is located..
( Is it MSDE on the same box, or some remote one like SqlServer or Oracle)

 

[MJRBIM]

Both CRYSTAL and CRYDEV are set-up with local MSDE databases.

I think my local machine is having problrms connecting to port 6400 (the APS port) on CRYDEV, but my network guy swears that all the ports are open.

That's why I'm trying to find a way to ping a specific port.

 

[Turkbear]

By Local, do you mean the both are on the
local workstation you are using to connect
and you can connect to one but not the other?

 

[MJRBIM]

The two servers CRYSTAL and CRYDEV are separate stand-alone servers that are located in two different server rooms.

I'm am trying to connect to each of them using the Publishing Wizard tool that is installed on my personal machine in a different part of the building.

CRYSTAL I can connect to fine.

CRYDEV gives me -

"Logon Error : Unable to connect to APS CRYDEV to retrieve cluster members. Logon can not continue."

 

[MJRBIM]

I have also been able to ping the CRYDEV server and Telnet to CRYDEV 6400 - the port where the APS connects.

So the port appears open, but the APS is not available....?

 

[johnwalker]

Not sure if this applies but ... We discovered a quirk with the publishing wizard when the name of the APS cluster is different from that of the server that it is installed on. The first time you connect you must use the server name and subsequent times you can use the cluster name. In our case we had the APS as CEDEV on server W2CE01, the first time using the wizard we enter W2CE01 as the APS then after that we can enter @CEDEV for the clustered APS.

 

[MJRBIM]

SOLUTION

It was a bad set-up on the 2nd network card on CRYDEV. We disabled the 2nd network card and everything is working fine.

We caught ir by pinging CRYDEV from CRYDEV, it returned a different TCP/IP number than you got when pinging CRYDEV from the local workstations.

The local hardware guys are going to check the set-up of 2nd network card later this week.

Thanks for all your suggestions - they helped a lot in my "detective" work.

Mark