Within the application server startup, what method or argument can be used to have Sage 100 application server "Start" when it launches.
Within the application server startup, what method or argument can be used to have Sage 100 application server "Start" when it launches.
Sage should make their WndX server a Windows service that automatically starts when Windows does.
Look at the target of the shortcut called "Sage 100 Application Server Startup" that should be added to your start menu. It should look something like this.
"C:\Sage\Sage 100 Advanced 2019\MAS90\Home\pvxwin32.exe" -mn lib\_appserv\apssrv.ini lib\_appserv\server -ARG SAGE
The last argument, "SAGE", is the server that the command will start. So if you open the "Application Server Configuration", you should see a drop down that lists the servers configured.
You don't need to launch the "Application Server Configuration" to start the application server. Just use the shortcut or command for "Sage 100 Application Server Startup" and it will start the application server.
hmmm, are you trying to start it with it with a script.
It can be configured as a service but you may run into the issue documented in this KB if you have 20+ users.
https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=20344
There are issue with running this instance of sage as a windows service. Right now for stability it runs as an application. Thanks for the suggestion.
There are two ways to run the Sage 100 service.
As a Windows service, which you control through the regular Windows interface for Services.
As an application, which you run manually within a user session (on the Sage server). There is no way to make this start automatically after a server reboot. Someone has to log in to the server and run the program.
Also, you can use SysInternals AutoLogin tool (it encrypts the password too) to configure the server to auto login using a dedicated "service" account to run sage 100. Then throw that "Sage 100 Application Server Startup" shortcut in the service account's StartUp folder along with a shortcut that has the following target.
C:\Windows\System32\rundll32.exe user32.dll, LockWorkStation
When the server restarts, it will auto login and that will trigger the two shortcuts in the StartUp folder, which will start the application server and lock the user session.
The registry hack in the KB article works great to solve the WindX errors, so Sage can run as a Windows service without a problem.
Yes, the sysinsterals Autologin tool is great for that. Thanks!
I will need to test this. I was under the understanding that when the application server startup launched it brought the server configuration and then you selected start. From the voices here I must be mistaken on that. Thanks for the assistance.
*Community Hub is the new name for Sage City