CAUTION: Sage Customer Support does not assist with issues related to third-party products or enhancements, hardware, report customizations, state or federal tax-related questions, or specific accounting questions. Please get in touch with your Sage business partner, network administrator, or accountant for assistance. Please refer to our Scope of Support document for details.

Note: Try the solutions in Error: "This program has quit. I/O Error. Pervasive status code 170" or "Pervasive status code 171" first. If reinstalling Pervasive/Actian does not help, then proceed with this fix. This fix is only recommended if other solutions do not work.

Since the symptoms point to the Windows profile on the affected workstation not having enough Windows rights or permissions to access domain resources (i.e. data) on the file server, even though the Windows user may be assigned an administrator role, the solution is to bypass this limitation by having Pervasive/Actian run as a service. Windows services do not require a Windows user to log in. Windows services automatically load when starting up the computer, with or without user interaction.

1. Log on as an administrator on the affected workstation.
2. Uninstall Pervasive/Actian from Control Panel.
3. Refer to the Related Resources section for article on how to reinstall Pervasive/Actian.
4. Locate the Pervasive/Actian workgroup service and change the login credentials from Local System to the domain administrator (i.e. domain\Administrator).
5. Restart the Pervasive/Actian workgroup service to have changes take effect.
6. Verify you can now launch Sage 300 on the affected workstation.

How do I manually install Actian PSQL version 12 Engine?
Sage 300 Construction and Real Estate and Sage Estimating Required Windows Permissions