Sage 100

Client using Sage 100 Advanced 2014 in a Terminal Server environment. When I try to log into Sage, the system acts as if everything is fine and then the Sage menu and folder screen flashes up and exits immediately. I have tried rebooting both the Sage 100 file server and the terminal server client. Any suggestions?

Did you try it in MAS90 mode?

You might try rerunning workstation setup, but most likely you will need to get everyone out of Sage100 advanced, Rename SY_Workstation, SY_Console, and Sessions.pvk files on the server. Sessions.pvk is found in the Home\lib\_appserv directory

oops I forgot one - also rename Locate.pvk (also found in Home\lib\_appserv directory)

Don't know if this is across all users - including those not on TS? Here's the usual suspect: Description Blank, white screen appears when starting Sage 100 Advanced or Premium or Blank white Sage 100 ERP screen appears with Help when launching Sage 100 ERP Advanced. Error: ""Sage 100 ERP has stopped working"" appears at the Server or Nothing happens or something flashes when starting Sage 100 Advanced or Premium Disclaimer Backup Warning Use caution when working with the below product functionality. Always create a backup of your data before proceeding with advanced solutions. If necessary, seek the assistance of a qualified Sage Business Partner, network administrator, or Sage Customer Support Analyst. Network Warning This solution requires advanced knowledge of your network. Contact your system administrator for assistance. Modifying Windows security incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows security. Always create a backup of your data before proceeding with advanced solutions. Cause Possible Causes: Stranded PVXWIN32.EXE session on the server Damaged System Files Blocked Port Resolution Note: For Sage 100 ERP Advanced and Premium, must stop the Sage 100 ERP Application Server desktop or Application Server Service and all users must while performing the following: PVXWIN32 process may be stranded on the Sage 100 ERP server At the server, stop the application server or service. Open Task Manager, Processes Select option to Show processes from all users Sort column by Image Name and locate PVXWIN32.EXE task End all PVXWIN32.EXE process If Terminal Server / Citrix (TS/Citrix) is used, the TS/Citrix session may have timed out or disconnected while Sage 100 ERP was still open. At the Sage 100 ERP server, end the Pvxwin32.exe task System files may be damaged In Windows Explorer, go to..\Mas90\Mas_System Rename the following file SY_Workstation.M4T -- (located in ..\MAS90\MAS_System) Following files applies to Sage 100 ERP Advanced and Premium only Sessions.pvk -- (located in ..\MAS90\Home\Lib\_appserv) Locate.pvk -- (located in ..\MAS90\Home\Lib\_appserv) Restart the Application Server Configuration. This will automatically generate the Sessions.pvk and Locate.pvk If Sage 100 ERP is normally run as a Service, stop the Application, exit Application Server Configuration, then start the Service The port number used might not be active. Open command prompt, run the following command Netstat -a |More (""|"" before ""More"" is the Pipe sign) Verify the port used is listed as listening The port number might be used by another program. Change the port Open Application Server Configuration. at the server Select Server tab Change the Socket number and click Apply. Make note of the current port number before changing in case this does not resolve the issue. At the workstations, change the port number with either of the following methods: Uninstall and reinstall Workstation Setup and enter the new port number when prompted Modify the Icon properties and the Sota.ini file Right click and select Properties on the Sage 100 ERP workstation client icon Change the port in the Target and click Apply. It should be listed after the Server Name or IP address. (ex. ..\MAS90\Home\pvxwin32.exe ../launcher/sota.ini *Client -ARG ""ServerName"" ""10000"" ""Sage 100 ERP"") Click Open File Location. This will open Windows Explorer in the Home folder where the client installation is located. Go back one folder to locate the Launcher folder Open Sota.ini Locate [Servers] section which is near the bottom Change the port which is listed just after the Server Name or IP Address. Save file and close. (ex 1=ServerName;10000;APS=SAGE;APPLICATION=Sage 100 ERP;Path=) Restart the Application Server service or application and test for error. Note: If the port number is changed and the Application Server is being run as a Service. The Service must uninstalled and reinstalled to use the new port. Firewall might be blocking access to the program. Check firewall settings on the server and at the workstations. Security settings may be too high or may not be allowing bidirectional communication Windows 7, Server 2008, and later operating systems may require Firewall Inbound and Outbound rules created. An open file might be blocking access. Close open files using Server Manager Right Click Computer, select Manage Open Roles, File Services, Share and Storage Management Under Actions select Manage Open Files Select only files that are open in the MAS90 folder Reboot Server to close open files if unable to locate file causing issue.

automatic logoff? Had that exact thing happen on a client. TS and App Server may not have had the same time, not sure exactly but, disabling automatic logoff in user maint fixed it.

Thanks for all of the suggestions but I found the error and it was WEIRD! Last night I tried to kill a couple of suspended sessions using the Master Console. I should have known better but it was late and I was tired. I killed that process once the ""hung"" sessions were gone and then I went on to do some rebuilds and recalculations. Well, apparently Field 45 in the SY_System file (BroadcastShutdown$) became stuck on ""Y."" So, after I logged out last night anyone else trying to log in would be immediately logged out. Furthermore, the only ways to fix this is to restore a backup of that file or edit that file with DFDM. Fortunately, I had another Sage install on the client's server farm where I had done a trial upgrade back in November. I had not erased this trial so I was able to use DFDM from that install.

That is weird, what a royal PIA