Solution Properties
Solution ID:
222924850025359
Last Modified Date:
Mon Nov 21 09:40:32 UTC 2022
Taxonomy Path:
Category//Transactions
Author:
LegacyAuthorUS
Error: "This program has quit. I/O Error. Pervasive status code 170" or "Pervasive status code 171"
Description
Cause

Pervasive status code 170 and 171 errors generally occur due to a problem at the local workstation. This can occur due to various reasons, but the usual causes are:

  • Another Windows profile logged in at the same workstation. Don't use the Switch User option. Log a Windows user off before you log on another user if this is a workstation operating system.
  • Pervasive/Actian on the local workstation is corrupt.
  • Pervasive/Actian is communicating over a wireless network.
  • Pervasive/Actian at workstation not running with domain administrator privileges.
Resolution

CAUTION:

This solution requires advanced knowledge of Windows security and network settings. Sage isn't responsible for any issues that arise from changes to these settings. Ensure you back up all system and application databases necessary for a complete restoration. It's advisable to contact a certified consultant or your system administrator for assistance.

If you use version 16.1 or earlier, see Potential security vulnerability with Pervasive System Analyzer

Considerations

Reboot the workstation if the issue only occurs on one machine. If rebooting doesn’t resolve the issue, follow the troubleshooting steps below.

If the issue happens to all users on all computers, have users exit the Sage products and restart the Pervasive/Actian services at the file server.

  1. Click the Windows start menu, Search programs and files, type in: services.msc and click OK.
  2. Locate the Pervasive/Actian services.
  3. Stop and start them (in no particular order).

Troubleshoot and resolve

  1. Log on the affected workstation as an administrator.
  2. If the computer connects to a wireless network, connect it to the network with an ethernet cable. Disable the wireless adapter.
  3. Click the Windows start menu, Search programs and files, type in: services.msc and click OK.
  4. Locate the Pervasive/Actian services and stop and start them (in no particular order).
  5. If using a terminal/Citrix server, verify that the Pervasive workgroup service logs on as a domain admin. Confirm you didn't change the password recently.
  6. Verify that there’s no other program installed that also uses Pervasive/Actian. For example, Sage 50 U.S. Edition or Accpac.
  7. Disable antivirus on the affected machine as a test and set antivirus exclusions as necessary.
  8. Verify permissions on the file server and local workstations.
  9. If the issue continues:
    • For issues only affecting one workstation, uninstall Pervasive/Actian from the affected workstation.
    • For issues affecting all computers, uninstall Pervasive/Actian from the server.
  10. If restarting Pervasive/Actian services at the file server didn’t help, attempt to reboot the file server.
  11. Uninstall Pervasive/Actian on the server or workstation.
  12. Reinstall Pervasive/Actian on the server or workstation.

 

[BCB:156:Chat 300 CRE US:ECB]

 

 

Steps to duplicate
Related Solutions

Sage 300 Construction and Real Estate and Sage Estimating antivirus exclusions

Sage 300 Construction and Real Estate and Sage Estimating Required Windows Permissions

How do I add Domain Administrator credentials to Pervasive/Actian services

Can I use Sage 300 Construction and Real Estate software on a wireless network?

Error: "Data folder open validation error: I/O Error. Pervasive/Actian status code 94. The application encountered a permission error. Data files require user and system permissions."

Error: "I/O Error. Pervasive status code 170." (only domain administrator works)

Can I install Sage 300 Construction and Real Estate on the same machine as Peachtree (Sage 50—U.S.Edition)?