KB Article 25359 may help. There are some links to other articles included on that article as well.
Error: "This program has quit. I/O Error. Pervasive status code 170" or "Pervasive status code 171"

Products
Sage 300 CRE

Description
Symptoms:

You may see the Pervasive status code 170 (PSC 170) error present itself when launching TS-Main or Sage Desktop in Sage 300 Construction and Real Estate (Sage 300).
Sometimes when launching Sage Desktop, you may see the splash screen, but nothing will happen.
When accessing data, users may receive a Pervasive Status Code 170 error.
The error may also show up as Pervasive status code 171.


Disclaimer
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
Note: Pervasive status code 170 and 171 errors generally occur due to a problem at the local workstation. This may be due to a number of reasons, but the usual causes are due to:

Another Windows profile being logged in at the same workstation. Note that using "Switch User" is not supported. You must log off a Windows user before you can log on another if this is a workstation operating system.
The Pervasive preload/processor isn't started on the workstation.
Pervasive on the local workstation is corrupt.
Pervasive is communicating over a wireless network.
Pervasive at workstation not running with domain administrator privileges.


Resolution
If issue is only occurring at one workstation, then reboot that machine. If rebooting does not resolve the issue, follow the troubleshooting steps below.
If issue is happening to all users on all computers, have all Sage 300 and Sage Estimating users exit the Sage products and restart the Pervasive services at the file server.
Click the Windows start menu, Search programs and files, type in: services.msc and click OK.
Locate the Pervasive SQL services and stop and start them (in no particular order).
If issue only occurs at one workstation, after restarting the workstation and issues are not resolved, log on the affected workstation as an administrator.
If the computer is connected to a wireless network, connect it to the network with an ethernet cable and disable the wireless adapter, then stop and start Pervasive as noted in the next step.
Stop and start the Pervasive engine on the workstation.
Click the Windows start menu, All Programs, Pervasive PSQL 11, Engines, Stop PSQL Workgroup Engine.
Click the Windows start menu, All Programs, Pervasive PSQL 11, Start PSQL Workgroup Engine.
Note: The program menu path may different for different versions of Sage 300.
Note: If rebooting the workstation does not help or the Pervasive preload does not automatically start up, but restarting or starting Pervasive preload helps, put the Start PSQL Workgroup Engine shortcut into the Startup menu.
If using a terminal or Citrix server, verify that the Pervasive workgroup service is set to log on as a domain admin and that the password has not recently changed.
Verify that there is no other programs installed that also uses Pervasive like Sage 50 U.S. Edition or Accpac.
Disable antivirus on the affected machine as a test and set antivirus exclusions as necessary.
Verify permissions on the file server and local workstations.
For issues only affecting one workstation, uninstall Pervasive from the affected workstation is issues are not resolved. If all computers are affected, uninstall Pervasive from the server.
If restarting Pervasive services at the file server did not help, attempt to reboot the file server.
Reinstall Pervasive on the server or workstation as per the manual installation process noted in the link below:

I called tech support on this. The solution was so simple. I run Windows10 so I went to Start > Actian PSQL 12 > PSQL Control Center and Documentation > Properties for MicroKernal Router > Performance Tuning > You will need to Uncheck the "Use Cache Engine" box.