Sage 100

v4.45 premium. the application server is set up to execute when the server is re-booted. However, users are no able to access Sage 100. The application program appears to be running in the task manager. If you then launch it manually from the menu it works fine and everyone can get in. Does anyone have any idea what is causing this?

Are the users getting any type of error message?

The users get the message ""Unable to Connect to Server"". It is the message displayed on the screen shot. It looks like the program is running but users can't connect. If I start the application program from the menu then everyone can connect. The server is set up to start the application program when the server is re-booted. However, users get the ""unable to connect"" message even though the program appears to be running in the task manager.

Were they ever able to connect? Sounds almost like a firewall issue or an incorrect port being used... IMHO. I am not a genius by any stretch of the imagination.

Yes. They have connected fine for 5 years and can connect now if the application server is started from the windows server menu. There isn't an active windows firewall because there is a Sonicwall hardware firewall. The application program is set up to start automatically if the server is re-booted. When the server is re-booted the Sage host application program (not using the service due to previous instability) doesn't start correctly.

How is the application program set up to start automatically at reboot time, but not be run as a service?

When you manually run the desktop app server from the Start menu (the scenario that works) are you logged in as mcs at the time or as administrator? If you are using something like Autorun from sysinternals to configure a specific account for App Server, try configuring it to use mcs then logoff server then logon again to see if you can connect from a client. Presuming that works you could research the difference with administrator.

The program starts from the Task Scheduler at system start up. The task runs the following command: ""D:\Sage Software\MAS 200 SQL\Version44\MAS90\Home\pvxwin32.exe"" with the following arguments -mn lib\_appserv\apssrv.ini lib\_appserv\server -ARG SAGE The task was set to run immediately on startup.

Yes but even with the Task Scheduler you have to choose a specific account to run the task with.

@AlnoorCassim When I run it manually I log in as administrator. IT set up the task scheduler job. I am going to find out what credentials are used. I am also going to suggest we delay the execution of the program for a minute or two after startup to avoid any conflicts with other programs that may me loading into memory. Stay tuned for further information. :-)

Perfect.