Getting error on sign on Page...

[mojjo]

Hi All,
I am getting an error on he sign on page for PS, the error is "The application server is down at this time". I have looked at the "configuration.properties" file and it looks right to me (Machine Nameort#)for the JOLT Listener. I was hoping somone else had some insight on this?

 

[Tim1]

Hiya,

It sounds very much like PS cannot see either the app server itself, or something that is referenced there (PS error messages are not the best sadly).

Have you got PS set up as two-tier or three-tier? It must be able to see all the various servers that are referred to.

Have a look in Config manager and check that you can ping all the IP addresses in there, one of those being slow or unavailable is normally favourite.

Tim

 

[mojjo]

I’ve got PS as a three tier…
I got it to work; I change the application Server WSL port number from 7000 to 6000 in the psadmin, as Weblogic is using Port 7001 and 7002. Thanks for your help Tim…

 

[krishnakvg]

it is definetly appserver is down.or it is not recognissing ur appserver. no other problem

kris

 

[PSJerome]

Hello,

I have had this problem intermittently although I could confirm the application server domain was running (PSADMIN - Server Status) and could be signed into using the Windows PeopleTools client. The crazy thing about it was that the development servers worked without any problems, but the production servers would experience the problem

The final resolution I can to through a conversation with with a PeopleSoft Customer Connection consultant. He stated that if the server has more than one network interface card (more than one IP address), you should use the static IP address in the PeopleSoft configurations (application server domains, process scheduler server agent, WebLogic, etc.). Don't use the machine (hostname).
Looking back at the development servers, those server have one NIC active, but the production server have two more more NICs active.

Once I replaced the hostname with the IP address, the "application server domain down" messages went away.

I have always perferred to use the PSMACH value and let PeopleSoft resolve it. I have not been able to confirm if this problem will exist with the use of the PSMACH variable, but using the IP address has worked so far.