Blank white screen appears when starting Sage 100 Advanced or Premium; or a screen flashes, then closes
Products
Sage 100
Region
North America
Description
Blank white screen appears when starting Sage 100 Advanced or Premium editionNote: There may be a small + symbol (upside down cross or Petrine cross) that displays in the blank screen
"White Box" only on start.
"White Box" with '+' on start
May also receive an "error #12" message in the white ProvideX box
Blank white Sage 100 ERP screen appears with Help when launching Sage 100 ERP Advanced and Error: "Sage 100 ERP has stopped working" appears at the Server
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
Insufficient permissions
Anti-virus program blocking access to or affecting writing to sota.ini fileIf this causes SOTA.INI to be blank then may also get "no valid servers found" message (see Related Resources)
Resolution
Note: For Sage 100 Advanced and Premium, all users must exit the program, and you must stop the Sage 100 Application or Service, in order to perform any of the following:
A Pvxwin32 process may be stranded on the Sage 100 ERP serverAt 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 processNote: An alternative is to have all users to log out of Sage 100 ERP (and for the Advanced or Premium editions, stop the Sage 100 ERP Service or Application), and then reboot the server.
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 damagedHave all users log out of Sage 100 ERP (and for the Advanced or Premium editions, stop the Sage 100 ERP Service or Application)
In Windows Explorer, go to the \MAS90\MAS_System folder where Sage 100 ERP is installed
Rename the following files:SY_Console.m4t
SY_Workstation.m4t
For Sage 100 ERP Advanced or Premium editions only:Go to the \MAS90\Home\Lib\ _Appserv folder also rename the following files:Locate.pvk
Sessions.pvk
Restart the Application Server Configuration and have someone log in. This will automatically generate the Sessions.pvk and Locate.pvk
If Sage 100 ERP Advanced or Premium is normally run as a Service:Stop the Application
Exit Application Server Configuration
Start the Service
The port number used might not be active.Open command prompt, run the following commandNetstat -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 portOpen 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 fileRight 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.
The User Logon may still have one or more tasks open in the Master Console though they are logged out of Sage 100Make sure the User Logon (of the user experiencing the problem) is logged out of Sage 100
Access Sage 100 with another User Logon that possesses full role permissions.
Open Library Master, Main menu, Master Console
Select any tasks open for the User Logon (of the user experiencing the problem)
Click the Kill selected task (red "x") button
Close Session errors on Sage 100 ERP ServerLog into Sage 100 ERP server with Windows account running Sage 100 ERP Application service
Close all Sage 100 ERP Error windows
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
Confirm that the sota.ini file is not blank or damaged on the Sage 100 workstation
Right click and select Properties on the Sage 100 ERP workstation client icon
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 the sota.ini file
Locate the [Servers] section which is near the bottomIf Servers section is blank, then follow steps in Related Resources "no valid servers found" for information on fixing or copying a good SOTA.INI file
Confirm that an Antivirus or similar program is not scanning the local \MAS90 folder on Sage 100 workstation which can result in a blank sota.ini file or Error #12 message in the "white" box (ProvideX box) when launching Sage 100
------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176
------------------------------