Fix Sage 50 Error Connecting to Database

The error message may appear in different forms, depending on the version of Sage 50 being used and the underlying cause of the issue. Some common error messages include “Sage 50 cannot connect to your database,“ “Sage 50 has encountered a problem and needs to close,” and “Error: “Your connection to the database has been lost”.

Because of its enhanced features and user-friendly navigation, Sage 50 is extremely popular among the business community across the world. It is also preferred widely by small and medium businesses and accounting professionals as with the help of it, they can streamline their accounting activities more efficiently. However, we should not forget one thing that like every other software, Sage 50 is also not fully free of bugs and errors.

Many users have intimated to us that they have faced the ‘Sage 50 Error Connecting to Database’ error message frequently of late. If you are also troubled by this issue, you are in the right place. In this blog, we are suggesting some easy solutions to this common issue. Just go through this blog, carry out the steps shown here and do away with this issue, for good!

Here we go! 

What is the Sage 50 Error Connecting to Database issue?

The Sage 50 Error Connecting to Database issue is experienced by the users usually while trying to open a company file or a sample company. The error can vary and may include problems with the database server, network connection issues, incorrect login credentials, or corrupted files. When this error occurs, it can disrupt business operations and cause frustration for users who rely on the software to manage their finances.

Read More-: Sage 50 Cannot find the Connection Manager when opening the company file

What Causes the “Sage 50 Error Connecting to Database” Error Message?

Many functional and technical issues often lead to the occurrence of this issue. Some of these are mentioned below-

• The folder Sage 50 is connecting to is attached with a Read-Only attribute.
• The .SAI and .SAJ folder missing/corrupt
• The connection manager is blocked by the Firewall installed on your system.
• The Log Service of the Windows Event is disabled.
• An issue in the .NET framework.
• The Connection Manager is either not installed or has not been started on the server 
• The UNC address is being used.
• The shared location used by the server has a permission issue.
• The anti-virus installed on your system may have detected the Connection Manager as a potential threat and may have redirected it to the quarantine.

How to Resolve the Sage 50 Error Connecting to Database?

Here, we are going to discuss multiple methods to resolve this issue –

Method 1-Restart the Sage 50 Cconnection Manager

Please follow the steps below –

• Log in to your computer as an Admin
• Go to Control Panel
• Click on Administrative tools
• Go to the Services section
• Locate the Sage 50 Database Connection Manager. Right-click on it.
• Select Stop.

Please Note– if you do not have administrator privileges, you will receive a prompt stating “The Connection manager service could not be started”.

• Open the company file and check if you are able to connect to the Sage 50 database or not.

Method 2- Make sure all the Folders are Files are visible in .SAJ Folder

Please follow the procedure below-

• Navigate to the location where you have saved the company file 
• Now, do a right-click on the folder with the extension .SAJ.
• Click on Properties
• Clear the hidden box checkmark, if exists
• Click on the tab named Apply and press OK.
• Now, open the folder with the .SAJ extension.
• Make sure all the files and folders within the .SAJ folder are visible when restoring a backup or opening a data file.

Method 3- Check if the SAJ Folder has a ‘read only’ Attribute

• Navigate to the location /folder where you have stored the company data 
• Right-click on Sage 50 Data File
• Click on the Properties tab
• Remove the checkmark next to the Read-only attribute (in case it is checked)
• Click Apply
• Now, right-click on the SAJ folder
• Choose Properties
• Remove the checkmark next to the Read-only attribute (in case it is checked)
• Click Apply
• Click the checkmark named Apply changes to this folder, subfolders and files.
• Click OK to finish

Error: “Sage 50 cannot Connect to its Database, Actian Zen on Computer [Server].”

On how to resolve the following error message, which is preventing Sage 50 from opening: Error: “Sage 50 cannot connect to its database on a computer server. Ensure that the system is logged in or that the database service is currently running. Also, ensure that the firewall is set to allow Sage 50 and Pervasive to pass through. You can also Click Help for more information. Finally, Click Retry to attempt to connect again.”

The Main Causes

• Actian service stopped on the server
• Unable to ping the server
• Network location/profile set to Public instead of Private on workstation and/or Server
• Firewall blocking program
• The incorrect server name in ~PVSW~.LOC file
• Using distributed file system (DFS) for the mapped drive
• Damaged Windows Management Instrumentation (WMI)
• Incorrect data path on the workstation
• Server and workstations on different versions
• More than one NIC enabled
• IPv6 is used instead of IPv4

Solutions for Error Sage 50 cannot Connect to its Database, Actian Zen on Computer [Server]

Part 1: Actian is Hung or Stopped

• Begin by first Stopping and then start the Actian database engine on the system.
• Next Following the same steps, top and then start the Actian database engine on the workstation(s) as well.

Part 2: Incorrect Data Path

• Start by Locating your data. 
• Start by Locating your data path. 
• Now you need to Compare the two directories. They should be the same except for the company folder listed at the end of the data directory. For example, if your data directory is C:\Sage\Peachtree\Company\abc123, then the data path should be C:\Sage\Peachtree\Company.
•  Note: If you find the data path is incorrect, you can correct it in one of two ways

Part 3: Network Profile set to Public on workstation and/or Server

Make sure that Your network location/network profile should not set to Public.

Note: In case the network connection is set as Public, firewall exceptions might be configured for a different profile like Domain or Private. Such exceptions added will not function normally under the Public profile.

• Start by Locating the network connection. This can be either Wi-Fi or Ethernet in the service tray in the bottom right corner of your Taskbar. 
• Next, Right-click your network connection and select Open Network and Internet Settings.
  • In case the network status is Private network or Domain Network, then it is set correctly
  • If the network status is set at Public network, then you need to change it by clicking on the Properties button
• Within the  Network profile change the radio button from Public to Private.
• Now click the back arrow at the top left twice and shut the Settings window.
• Next Test connectivity.
• In case you still have the error proceed to part 4: you need to Configure the firewall

Part 4: Configure Firewall

Configure the firewall to allow the files for Sage 50 through:

Note: GEO Blocking should not be enabled.

When Configuring the Firewall or proxy server allow access to the following URLs:

• elspv.pervasive.com
• bkpelspv.pervasive.com
• Sage Activation URL: https://licensing.services.sage.com/lic/services/LicenseService/
• aatrix.com

Note: When using a 32-bit operating system, open Program Files instead of Program Files (x86) where the latter is listed.

The following files must be allowed through your firewall and added to your anti-virus exceptions list:

• Ports 443, 1583, 3351
• Located in the Program Path (by default it’s located at C:\Program Files (x86)\Sage\Peachtree\).
  • Peachw.exe
  • PeachtreePrefetcher.exe
  • SmartPostingService[Version].exe
  • PeachUpd.exe
  • SageReg.exe
  • Sage.overdrive.cloudbackup.exe
• Located within data path: OverDriveData.txt file
• Located within C:\Program Files (x86)\Common Files\Sage Data Exchange:
  • Sage.Data.Exchange.Client.exe
  • SageOverDrive.exe
• Located within C:\Program Files (x86)\Actian\PSQL\bin: In case using Sage 50 2022 and earlier versions.
  • w3dbsmgr.exe
  • w3lgo103.exe
  • NOTE: If using Sage 50 2023 and later. Located in C:\Program Files (x86)\Actian\Zen\bin:
  • zenengnsvc32.exe
  • zenengnapp.exe
  • w3lgo103.exe
• Located within C:\Program Files (x86)\Common Files\Peach\FormViewer
• Note: In case not currently using the payroll service, this folder may not be present.
  • Aatrixforms.exe
  • Updater.exe
  • Updater2.exe
• C:\Users\[Windows Username]\AppData\Local\Aatrix Software
• Note: If AppData is not listed, turn on the folder option to Show hidden files and folders
• C:\Users\[Windows Username]\AppData\Roaming\Aatrix Software
• To enter exceptions for Sage URLs that might be blocked and preventing the software from downloading, for this add an exception for *.sage.com
• Within the Program Files(x86) or Program Files, if a 32-bit OS, search for the file peachw.exe.config and enter an exception for every URL found in that file

Part 5: Incorrect or Blank Server Name in ~PVSW~.LOC File

Solution 1: Go to the Data Path

• Click on WINDOWS KEY+E.
• In File Explorer, find the directory for the .INI file
  • Sage 50 2019 and later: Browse to C:\ProgramData\Sage\Peachtree
  • Sage 50 2018 and previous: Browse to C:\Program Files (x86)\Common Files\Peach (C:\Program Files\Common Files\Peach on a 32-bit computer)
• Launch the configuration file for your version of Sage 50—U.S. Edition:
• Note: when prompted to select a program, select  Notepad.
  • Version 2023: Peachtree300.ini
  • Version 2022: Peachtree290.ini
  • Version 2021: Peachtree280.ini
• To locate the data path, go down to the bottom of the third paragraph and find the line starting with DATAPATH=.
• To locate the program path, go down to the bottom of the sixth or seventh paragraph and look for the line starting with PROGRAMPATH=.

Solution 2: From Inside Sage and its Icon Properties

To find the data path:

• Launch Sage 50—U.S. Edition.
• Click File, Open Company.
• Note: Do not select Open Previous Company
• Drag the corner of the box so the full directory is displayed.
• Within the directory, minus the truncated spelling of the company name, is the data path.
• To find the program path:
• Start by Right-clicking on the Sage shortcut icon.
• Click Properties.
• The blue highlighted path on the Target line, minus Peachw.exe, is the program path.
• Note: In case you select Open File Location, the program path will open for you
• Open the ~PVSW~.LOC file in Notepad.
• Next, Replace the incorrect server name with the correct server name

Part 6: Network Communication Problem

Within the workstation ping the server by name

• Within the server, press WINDOWS KEY + R to bring up the Run command.
• Next Type cmd, and then click OK.
• Now Type ipconfig,
•  and press ENTER.
• Note the IPv4 Address.
• Type Hostname and press ENTER.
• Take Note of the computer’s name.
• Navigate to the workstation.
• Repeat Steps 1-6.
• Now Type ping [server computer name], and press ENTER.
• You need to Verify that the workstation receives a response and that it is coming from the server’s noted IP address.
• Finally, go back to the server and repeat Steps 9 and 10, using the workstation’s computer name.

Now Follow the same steps at the server to ping the workstation(s) by name

In case you receive a Request timed out message on either step above or if you have a latency of greater than 10ms (time=10ms), you will need to contact your IT network administrator.

Part 7: Mapped the Drive Using the IP Address

Within the release 2021.1 and higher, UNC (Universal Naming Convention) paths may be utilized for the data path instead of mapped drives. For example, \\server01\Peachtree\Company.

• Start by launching File Explorer and go to C:\ProgramData\Sage\Peachtree.
• launch the configuration file for your version (2023: Peachtree300.ini).
• Now, Change the DATAPATH= line to the correct company data UNC path; for instance, \\server01\Peachtree\Company. In case you have other workstations running Sage, you can copy the UNC path from the DATAPATH line of their configuration file.

Part 8: Damaged Actian Database on Server

Completely remove and reinstall Actian. For this follow the below steps:

Section 1: Remove Actian

• Start by Closing Sage 50 and check if all the users have exited before removing Actian PSQL Workgroup Engine at the server.
• Now Press the Windows+R keys on the keyboard and type AppWiz.cpl in the Open box and click OK to access Programs & Features.
• Next, uninstall any listed version of the Actian PSQL Workgroup Engine
  • If you are using Sage 50 U.S. Edition 2019 or earlier, the database engine name will appear as Pervasive PSQL Workgroup Engine.
• Now Close the Control Panel and press the Windows+R keys again.
• Next Type C:\ and click OK.
• If present, delete the folders pvsw and pvswarch.
• If present, delete any file named ActianZen_v[version number]_Install.log and/or ActianZen_v[version number]_Patch.log
  • when using Sage 50—U.S. Edition 2019 or earlier, the files will be named PSQL_v[version number]_Install. log and/or PSQL_v[version number]_Patch. log
• Go to C:\Windows and if present, delete pvsw.log.
• Go to C:\ProgramData.
• Note: You may need to show hidden files and folders to see this folder. 
• If present, rename the Actian folder to OldActia
  • when using Sage 50 2019 or earlier, rename Pervasive Software as OLDPervasive Software if present.
• Go to C:\Program Files or C:\Program Files (x86).
• When present, rename the Actian folder to OLDActian
  • when using Sage 50 2019 or earlier, rename Pervasive Software as OLDPervasive Software if present.
• Go to C:\Program Files\Common Files or C:\Program Files (x86)\Common Files.
• When present, rename the Actian folder to OLDActian
  • When using Sage 50—U.S. Edition 2019 or earlier you need to rename Pervasive Software Shared to OLDPervasive Software Shared.
• Close File Explorer.
• Click the Windows+R keys again and type regedit, and click OK.
• Now Right-click Computer, left-click Export, and save a backup of Registry to the Desktop of the system.
• Go to HKEY_LOCAL_MACHINE\Software or HKEY_LOCAL_MACHINE\Software\Wow6432Node
• Note: Do NOT delete the Wow6432Node folder itself – only the individual registry keys named in Step 19 below.
• When present, delete Actian, Pervasive Software, and PEYX489ZK.
• Close Registry Editor.

Section 2: Manually Reinstall Actian

• Within the File Explorer, go to the installation folder located at C:\Sage\Sage50_[version] OR browse to Program Path to open PeachtreeInstaller20xx folder. 
• Launch PervasiveMin folder and double-click SetupWorkgroup32_x86.exe
  • When using Sage 50 2019 or earlier double-click PervasivePSQLv11WGE_x86.msi.
• Click Next.
• Now Accept the license agreement
• click Next.
• Click Run as a Service
• click Next.
• Click Complete
• click Next.
• Click Install
• Click Finish.

Now Open the program and verify that the issue no longer occurs.

Part 9: Using DFS for the Mapped Drive

You need to be aware that Sage 50 cannot use a DFS share. In this case, you will need to disconnect the drive and map the drive using the standard UNC path.

Part 10: Server and Workstations on different Versions

Make sure that the server and the workstation(s) are within the same version and update. In case not, then apply the latest update to the server and all the systems. One can view the updates by going to Services, and Check for Updates in the software.

Part 11: Damaged WMI

• Start by clicking the Windows key + R.
• Within the Run box, type eventvwr.
• Now Select OK.
• Next Select Windows Logs, and then Application.
• If you locate the error messages referencing WMI, you will need to consult your IT professional or Microsoft Support.

Part 12: IPv6 is being used Instead of IPv4

• In case IPv6 is in use, then it may try to use that first instead of IPv4.
• Disabling IPv6 is not a recommended option as it has been confirmed to break components of Windows functionality.

Sage 50 Cannot Open the Database because the Database Engine Reported an Error-when Opening the File Locally

Before performing the following tasks:

• Start by Verifying if the sample company is opening
  • If it does not open, you need to follow How do I restart Connection Manager in Windows 10?
• In case your file is shared on Remote Data Access, see Option 4 below.
• If the file is shared on a network, resolve Error: “Database engine reported an error” or “Database engine timed out” in a network environment. 
• Make sure that the.SAJ folder is clean of unwanted items.
• Check the information in the log file in the SAJ folder with the correct timestamp on it for when the error occurred.

Fix Sage 50 Cannot Open the Database because the Database Engine Reported an Error-when Opening the File Locally

Solution 1: Restart the PC

• Verify if the connection manager is running.
• Next, Try opening the file again

Solution 2: Run as Administrator

• Start by right-clicking on the Sage 50 icon.
• click Properties.
• Within the Compatibility tab, Privilege Level, select Run this program as an administrator.
• Click OK.

Solution 3: Move the Data to a New Folder

• Move the.SAI &.SAJ folder to the C:\\ or Desktop and open the file from there.
• Makes sure that the file has not been synchronized to a folder on One Drive, Google Drive, or other cloud services.
  • In case the file generates an inflated error log and there are conflicted file versions in the SAJ folder, the backup software should only be turned on after the time when you are not using Sage 50
  • In case you moved the SAJ SAI combo to the C:\\ from the server, copy it back to the server and see if it opens remotely

Solution 4: Remote Data Access

• Start by Re-downloading the company file from the welcome screen. 
• Navigate to Connect to a shared company, or from within an existing company file that can open, click on File, and Connect to a shared company.
• Next Log in with your Sage account email address when prompted.
• Click on the company file with the issue
• click Connect.
• Select the location and file name you would like 
• click Save
•  In case you want to overwrite the existing file that has the error, click the same name and location as that the file was saved in.
• click Yes.
• Once the company file downloads and synchronizes, it should open normally.

Solution 5: Anti-Virus

• Shut off the antivirus real-time protection.
• Open the data file again.

Solution 6: ODBC

• Start by Right-clicking on Windows Start, Apps, and Features.
• Locate for MySQL Connector / ODBC 5.2(a).
  • In case found, uninstall then reinstall it 
  • In case not found, install MySQL Connector/ODBC 5.2(a) by opening the folder for the latest version of the installer files, typically in C:\Sage\Sage 50 Accounting Installer Files – CDN Release 202X.X.
• Launch the BIN and MySQLODBC folders sequentially.
• Click on mysql-connector-odbc-commercial-5.2.4-ansi-win32 and follow the installation wizard to install MySQL Connector/ODBC 5.2(a)

Solution 7: MySQL

• Shut the Sage 50 on all the computers.
• Open Windows Task Manager of the computer hosting the database.
• Click the Process tab.
• Check the Show processes from all users button.
• End any mysqld.exe (or mysqld-nt.exe) from the Image Name list.
• Open your data file again.

Solution 8: Check the Drive for Free Space

Error: “The Connection Manager could not start the database engine

Solution 1: Restart the Sage 50 Connection Manager

• Start by Selecting Control Panel, Administrative Tools, then Services
• Right-click on Sage 50 Database Connection Manager
• Click Select Stop
• Right-click on Sage 50 Database Connection Manager
• Click Select Start
• you get a message stating: “The Connection Manager could not be stopped. You need administrator rights.“
• Try to open the company file.

Solution 2: Reinstall the Program

• Start by Uninstalling Sage 50.
  • Now Right-click on the Windows Start, Apps, and Features
  • Locate the Sage 50 version you are trying to repair and click Uninstall
  • Follow the wizard to complete the uninstall
• Reinstall Sage 50 
• Verify that the company file will now open.

Solution 3: Move the Files out of a Cloud-Synchronized Folder

• To help identify if your data is in a cloud folder
• If the files are in a cloud-synchronized folder, relocate the files to a new folder that is not synced.
  • The best folder location for your data is on the C:\\ Drive.

Solution 4: Verify that mysqld.exe and mysqld-nt.exe Exist

• Start by Verifying the mysqld-nt.exe file exists in: C:\Program Files (x86)\winsim\ConnectionManager\MySqlBinary\5.0.38\mysql
• Now, Verify the mysqld.exe file exists in C:\Program Files (x86)\winsim\ConnectionManager\MySqlBinary\5.6.10\mysql
• In case they do not exist, your security software, firewall, or anti-virus. may have quarantined the executable file or it was removed manually
• In case the file was quarantined, you need to contact the security software provider on how to restore or whitelist this executable.

Solution 5: Reinstall the Connection Manager

• Start by Right-clicking the Command Prompt, Now select Run as Administrator from Windows Start
• Type: sc delete “Sage 50 Database Connection Manager”
  • In case you receive an error “[SC] OpenService FAILED 1060:” on the command line type in on the command line type: “sc query type= service state= all” then re-enter “sc delete “Sage 50 Database Connection Manager”
• Click the F5 key to refresh your Services list.
• When you will see that the service is gone
• After you confirmed that the service has been deleted, bring up task manager (CTRL+SHIFT+ESC) ◦On the process tab click or check Show processes from all users
• End the Simply.SystemTrayIcon.exe process.
• Go to the appropriate winsim folder:
  • 32-bit computers go to: C:\Program Files\winsim
  • 64-bit computers go to: C:\Program Files (x86)\winsim
  • Delete the Connection Manager folder
• Repair the Sage 50 installation

Solution 6: Start the Windows Event Log Service

• Click  Control Panel, Administrative Tools, and then select Services
• Click  Windows Event Log in the services list and double-click to open the Properties window.
• In case the service is Disabled, change the Startup Type to Automatic.
• Click  Apply and the Start button will become available.
• In case the service is available/automatic, Click the Start button to start the service, then select OK.
• In case the service starts, open Sage 50.
• In case the service is not starting, or there is an error 1053: Select Log On tab, then Add the local administrator.
• Next, you need to confirm the service status is started.
• Try to open the company file.
  • In case you get an “error 4201, the instance name passed was not recognized as valid by a WMI data provider” open Command Prompt as administrator
  • Type: cd C:\Windows\System32\LogFiles\WMI.
  • Type: rename RtBackup RtBackup2. If you get an ‘access denied’ error message, go to the next step, otherwise go to step 12
• Within the “Start” menu, find “Command Prompt”. 
• Now Right-click and select “Run as Administrator”.
•  In case you are prompted for an administrator password or confirmation, type the password or provide confirmation.
• Enter the following commands, then click “Enter” to execute them one by one. Also, note the space before the command and its parameter.
  • Takeown /f C:\windows\system32\logfiles\wmi\rtbackup cacls C:\windows\system32\logfiles\wmi\rtbackup /G administrators:F
• Exit Command Prompt.
• Reboot the system.
• In case the event log is still not starting, you need to contact your local IT person to fix this issue.

Solution 7: Open Existing Company

• In case the recently used company has a UNC path, for example,\\server\company name) click Select an existing company
• Go to the company in Windows Explorer, for example, C:\Sage 50 Data\.

Solution 8: Verify if the SAJ Folder has a Read-Only Attribute

• Shut down Sage 50.
• Go to the location where the company file resides.
• Now Right-click the folder with the extension SAJ.
• Click Select Properties.
• Clear the Read-Only box if a checkmark is there.
• Click OK.
• Restart Sage 50 Accounting and try to open the company file again

Solution 9: Verify all Files & Folders are visible in the.SAJ Folder

• Go to the location where the company file resides.
• Next Right-click the SAJ folder.
• Now click Select Properties.
• Clear the Hidden box checkmark if one is there.
• Click on  Apply.
• Click OK.
• Open the SAJ folder.
• Verify that all files and folders are located within the.SAJ folder.

Solution 10: Replace the ODBC 3.51.28 with 3.51.19

Set the data that requires to be launched or converted on the C:\\ Drive

Solution 11: Only 1 workstation is having a Problem

• Map a network drive to the data.
• Next, Verify that you can open the company

Solution 12: Save the Data Files in another Folder on the Server

• Start by Making a copy of the.SAI file and the.SAJ folder within a different folder on the server.
• Next, Verify that you can open the company.

Solution 13: My Data is on Remote Data Access

Re-download a copy of the company file giving the error from Remote Data Access:

• Select the location and file name you would like
• Click Save
• If you want to overwrite the existing file that has the error, click the same name and location file was saved in and click Yes when it asks you if you would like to overwrite the existing file
• After the company file completes downloading and syncing, it should be able to open normally.

Solution 14: Restore from Backup

• Locate a backup .CAB file 
• Restore the backup

Also Read-: Sage 50 Cannot Connect to your Sage 50 Company Data Location

Conclusion

We hope the troubleshooting steps mentioned above would help you a great deal to fix the ‘Sage 50 Error Connecting to Database’ issue on your Computer. But before you perform the above options, please ensure that you understand your operating system better. All these solutions need advanced knowledge of your system.

Frequently Asked Questions(FAQs)