Resolve: Sage 50 Cannot be Started Error

💠 Restart pervasive on the computer that hosts data
💠 Make sure to verify if the error is resolved on that computer by opening the program
💠 If you are running sage on a network and the workstation is still getting the error but the server is not, you need to restart the pervasive on the workstation.

💠 Some windows update to turn the Pervasive service off and manual restart of the service
💠 Windows update may also change your network profile from private to public, which is also a big cause to start blocking pervasive.

💠 Click start → All program → Sage 50 accounting → Sage 50 resources → help →  Technical Support Utilities → Sage advisor diagnostic tool
💠 Click Agree on button
💠 Now you need to select the test listed below and select Run to run all the selected tests
💠 .Net error check: Scroll to the bottom of this test
💠 If you don’t find any .NET errors you can continue to the next test result
💠 Company location test
💠 If at the end of each company folder found and you see OK your companies are in the correct location
💠 Needed files check: If all of the files include name, size and modified date then your data path files are fine
💠 Lock file check
💠 Product .INI files check – It will check the INI file for the versions which you have installed.

If you see the error Local path on the server – Unable to fetch server path, it seems you don’t have access rights to the machine or something is blocking communication between server and workstation.

💠 You need to check the results of the Data Path Permission check, Firewall check, Server Access Check and the Workgroup check:
💠 Data path permission check
💠 Firewalls check – This check will verify Microsoft windows firewall is correctly configured or not.
💠 IP Address check – This test will find and displays the IP address for both the server and workstation.
💠 Server access Check – If you use Sage 50 on only one computer you can skip this test
💠 This test will provide the name of the server, the UNC path of the data path to the server, and the IP address of the server. It also verifies the workstation can ping the server successfully.

💠 Recent virus or malware.
💠 Errors occur after selecting a company
💠 Norton 360 by Symantec installed
💠 Internet security is installed
💠 Using the program in a virtual private network
💠 Changed the current version through updating serial number
💠 Errors occur when using sage 50 shortcuts only
💠 It occurs when the shortcut is set to run as administrator
💠 Only one windows user receive an error
💠 Only one work station receives the error or it started after installing the program
💠 Remote desktop connection
💠 Reinstall the program.