Summary
This article will provide you with guidance on how to resolve your payroll system from hanging when accessing the payroll shortcut on Sage Classic and Sage Premier
Description
The Payroll system opens up, however no companies are loaded on the Company Listing Screen. The system seems to "hang" and could bring up the "extend 32-bit runtime has stopped working" message.
EXAMPLE:

Resolution
- Ensure the payroll system folder is excluded from active anti-virus scanning on the server and/or workstations
- Do a rebuild on all data in the folder
- Confirm that Sage Connected Services and Sage VIP Runtime is installed correctly.
NOTE: This can be reinstalled by uninstalling both from the Control Panel Programs and Features, and then run the applications in the system folder (SCSInstall.msi and SageVIPRuntime.msi).
- If the issue persist, it indicates one of the company VPCNT files might be damaged. Do a rebuild only on the CNT files in the folder (vutil -r -k 0 VPCNT*.pay).
- If the issue persist, you might need to determine which company files are damaged by following these steps:
- Copy the payroll system folder to another location
- Replace the VPFILE. PAY and VIX files with blank files
NOTE: You may request these files from payroll support desk
- Check the payroll folder for all VPCNT files. Confirm if all the companies in the folder is the same as the ones that was on the Company Listing Screen
- Import the companies one-by-one - the affected company will cause the system to "hang". You might need to repeat the steps above to check other companies
- Once the companies have been identified, focus your rebuild on the files. Check if all the company files are in the folder
- If all else fails, you will be required to restore a backup of the company. This process should be continued with caution if you are Total Solutions (ESS/Premier HR) or Sage Self Service client.
- You can test this by installing a new system of the same version in another folder, to see if you experience the same issues.
- If the new system reflect the same issue, reinstall the versions of .NET (3.5 and 4)