Ever had problems connecting to your server hosting the NT process scheduler or App Server using Remote Desktop and not being able to use“psadmin” to perform administrative tasks?

Here is what happens when you connect to the server using remote desktop and invoke psadmin.

Psadmin_remote_desktop_1

You will receive the above message when you try to check the status of process scheduler.
So, how do you determine if you NT process scheduler is running? There are multiple ways to determine if your process scheduler is running.
1.Look at the task manager
2.Look at the log files
3.Check status using psadmin
In this post, I will cover the last method since the other two are straighforward.
Here is how you can use psadmin when connected using remote desktop.

1.Ensure that the “Telnet” service is started on the server

Psadmin_remote_desktop_2_2

2.Go to Start > Run > Telnet <servername>

Psadmin_remote_desktop_3_2

3.You will get a command prompt window

Psadmin_remote_desktop_4_2

4.From this prompt, go to your PS_HOME/appserv
5.Invoke psadmin

Now, you should be able to use the “psadmin” utility for monitoring, configuring, start, stop, etc.

Posted by Nitin Pai
Comments (4)
September 17th, 2007

Comments (4)

Valathappan Sivaraman - June 20th, 2009

Hi Nitin, Thanks for your posting on this kind of tips. I tried to create seperate services for each domain in the same home and I am not able to create a seperate service and I even tried sc command as below. Please give me your thoughts. C:\>sc create PeopleSoft_D__psoft_fscm90_EPDMO binPath=D:\psoft\fscm90\bin\server\winx86\epdmo.exe DisplayName= "PeopleSoft_EPDMO"

RD - February 21st, 2008

Thank you. I will try that out.

Nitin - February 15th, 2008

If you disable telnet the other option is to connect using console option. In this case, you can access psadmin without having to telnet. Regarding services, it is possible to configure multiple services for process schedulers using the same PS_HOME. You can copy the psntsrv.exe and rename it to your domain name. Modify the psprcs.cfg parameter PrcsServerName to use the domain name. Now create the service. I currently do not have admin access on my current assignment to demonstrate this example. I will try and post an article sometime next month with screenshots to walk you through this setup. Let me know if you have any questions. Thanks Nitin

RD - February 11th, 2008

Some clients have security policy to disable telnet and block port 23. To work around that I use to configure it as service. The drawback I have is that unless you have different PS_HOME, we can configure only one service for all the app servers and process schedulers in that box. Do you have any suggestion on configuring them seperately as different services. It becomes a problem if I want to restart just one process scheduler alone and not all of them.

Comments are closed.