Update 14/03/2023: We have release new software and articles to resolve the reported error. Click here to view the post with more information.

We have received a few reports of customers experiencing the error message "Object reference not set to an instance of an object" after the update. 

We have 2 reported scenarios:

Error when launching the system and converting the data from Release 5.9a to 6.0a, after installing the update:

During the data conversion process (after the software was installed and you open the system the first time), the employee information is written to a new database for Employment Verification Services), and some records might have preceding spaces (employee codes, names), which result in the records unable to create.

Work-around suggested:

Review the data on Release 5.9a to identify any records with spaces in the employee code.

Error messages when saving and closing the Employee Information screen, or performing tasks within the system:

This issue is experienced in a multi-user network environment, where the system is accessed either via mapped drives or remote desktop protocol.

During the installation and update of the data, the Employment Verification Services (EVS) database is created for each company based on the registry settings of the user profile at that point in time.

In some instances, other users accessing the system, might have different location data path on their registry key, and it is possible that the other users might not be able to access the new database created.

When accessing certain functions that interfaces with the EVS database, the database cannot be found and result in the error message. These include:

• Creating new employees
• Saving and closing the Employee Information screen
• Importing Flexi Fixed import
• Transfers of employees

Work-around suggested:

• Access the VIP System folder, and copy the file EVS.VDB6 to your desktop 
• Access the computer / profile where the company data was updated
• Access REGEDIT and locate the following registry keys:
  • Computer\HKEY_CURRENT_USER\SOFTWARE\Connected Services
    • Confirm the location of the ESS Data Path - this should point to the VIP system folder
    • If it does not, make note of this location
  • Computer\HKEY_CURRENT_USER\SOFTWARE\EVS
    • Confirm the location of the Data Path - this should point to the VIP system folder
    • If there is no such location, a registry key must be created
    • If the location is not the same, the database was created in a location, not available to all other users
    • Access the location you made note of and copy the file EVS.VDB6 file, to the VIP System folder 
    • Correct the data paths for both mentioned registry keys, to point to the VIP system folder
• Access the impacted users, and ensure that the following registry keys are also pointing to the VIP System folder
  • Computer\HKEY_CURRENT_USER\SOFTWARE\Connected Services
  • Computer\HKEY_CURRENT_USER\SOFTWARE\EVS

Our development team is currently reviewing the reported issues. 

Should you require assistance, please contact Sage Customer Support.

Take note: We noticed that some users copied the files mentioned in the error from previous software releases - Sage does not recommend users to follow this action as the program files are designed to interact with functions of the same release, and may result in other errors.