Description
Cause
- Other user sessions not closed out properly
- Many hung Peachw.exe processes in the Task Manager
- Outdated or damaged files in the data path folder
- DDF files are incorrect version
- Network connection is set to Guest/Public and Actian/Pervasive is being blocked by the firewall
- Damaged data path folder
- Another user is exporting a report to Excel
- Sage Exchange is open
- Wrong data path
Resolution
Note: If another user in the process of exporting a report from Sage 50 to Excel receives this message, wait until the export completes, and then try the action again.
IMPORTANT: Check to see if the individual company folder is in the wrong data path before trying all options below. If it is, move it to the correct data path noted in the INI file; then check to see if you still get the error message after moving to correct data path.
Option 1: Sage running in the background
Option 2: User sessions not closed out properly (MOST COMMON)
Option 3: Run program as Administrator
Option 4: Remove lock files in your company data folder
Option 5: Remove damaged files in the data path
Option 6: Actian is damaged
Option 7: Perform an expendable file cleanup on the company's data folder
Option 8: Using Paya Connect Desktop
Refer to: Error: "Another Sage 50 user or workstation is accessing this company area or performing a similar company process" and you are using Paya Connect Desktop.
Option 9: Change network/firewall settings
Option 10: Verify that data file permissions are set correctly
Refer to: Error: "Another Sage 50 user or workstation is accessing this company area or performing a similar company process" and data file permissions are incorrectly set.
Option 11: Create a new data path
Option 12: Error happens while running a Backup
Option 13: When Importing data in Quantum Version
Chat with support