Sage 50 Unable to Connect to its Database Error – Actian Zen on computer or server

When installing the Sage 50 accounting system on the system, you cannot link to the database. There are many reasons associated with the failure of Sage 50 Error Connecting Database; for instance, the Actian service is blocked on the server, failure to ping the server, or the network location is set to public rather than private, or more. The AccountsPro team provides a troubleshooting guide to fix Sage 50 unable to connect to its Database, Moreover, users can get help from the Sage 50 Error Support team.

What won’t Sage 50 connect to Its Database Error?

Common errors encountered in Sage 50 when connecting to the database are as follows:

• Cannot connect to the database server.
• Database login failed.
• Error: Failed to establish a connection to the database.
• The database server is not responding.
• Database connection error: [specific error code].
• Unable to access the database.
• Network connection error.
• Sage 50 error connecting to the database

Here’s a quick checklist to help you fix it:

1. First, ensure the Actian service is running on your server.
2. Double-check that the IP address and port number in the Database Configuration window are correct.
3. Finally, look for any firewall restrictions or incorrect data paths that could be getting in the way.

These steps usually resolve the issue of Sage error connecting to server quickly, so you can get back to business without delays.

What are the causes of Sage 50’s failure to connect to its database?

• The Actian service is paused on the server
• Failed to ping the server
• When the Profile or network location is set to public
• If the configuration file does not contain the right path
• Incorrect ini file
• The firewall-blocking application
• The wrong server name is in a file named ~PVSW~
• Mapped driver, Use distributed file system (DFS)
• Corrupted WMI(Windows Management Instrumentation)
• The workstation contains the wrong data path
• If workstations & servers are on different versions
• Enabled Multiple NIC
• Used IPv6 in place of IPv4

Find about Sage 50 Database Repair Utility Tool which fix almost all system and database warning messages.

Methods to Resolve Sage 50 Unable to Connect to Its Database Error

When cannot connect to Sage 50 database, then the error message will provide specific details, but it can be caused by many issues including Sage 50 database connection error, problems with the Sage 50 Connection Manager, Actian service stopping, problems with the Sage 50 Data Service, network connectivity issues, Sage 50 Actian Zen connection issue, sage 50 database engine on computer is unavailable, etc., or even corrupted data files.

Following is the list of resolutions to fix the “cannot connect to Sage 50 database on network error:

Solution 1: Verify the data path

Check that there is a correct datapath on a stand-alone system/server with the following steps:

1. The datapath acts as the location for data. If the application is searching in the wrong directory, then there might be several issues. Thus, it is essential to have the right data path.
2. Search the data
3. Now, find the company directories with the following instructions:
   • Hit the File button
   • Click the Open Company tab
   • Choose the main Sage page with the No companies open option
   • Select the option named Open an existing company
   • It will appear an active company history and the company file location will appear in the column that says Directory
   • Now, check the data path
4. Discover the data path from the Sage icon properties with the following instructions:
   • Open Sage 50-US Edition
   • Choose the File button
   • Click the Open Company tab
   • Now, drag the box corner to show the full directory
   • It includes a minus and the company name truncated, which is known as the data path
   • After this search for the program path by right-clicking on the Sage icon
   • Choose the Properties tab
   • It will display the blue highlighted path, minus Peachw.exe, known as the program path.
   • Click Open file location to open the program path.
   • Now, start a comparison between the two directories. Make sure they match, except for the company folder appearing in the data directory.
   • In case there is a wrong data path now, fix it by moving data to the data path, or fix the data path by changing the data path, and also, you can take a backup of your Sage 50 data.

Solution 2: Check if Actian is paused or hangs

1. Hit Windows+R button
2. Enter SERVICES.MSC in the search box
3. Hit OK
4. Now, right-click on the option named Actian PSQL workgroup engine
5. Choose the Stop button
6. Select the Actian PSQL Workgroup Engine and right-click on it
7. Check if the workstation can open

Know about the Sage 50 workstations update installation issues and solutions in many ways.

Solution 3: Set the Network profile to Server/workstation

1. Verify the network profile or network location failed to Public
2. Search the network connection
3. Choose the network connection and right-click on it
4. Click the option named Open Network & Internet Settings
5. If the network status is set to the Public network tab
6. Now, switch to the button named Properties option
7. Below the Network, the profile tab modifies the option from Public to Private
8. Click on the back arrow
9. Now, close the window that says Settings
10. Next, the Test Connectivity tab

Solution 4: Check the Configure Firewall

1. Start firewall configuration to permit access to the following URLs:
   • elspv.pervasive.com
   • bkpelspv.pervasive.com
   • Sage Activation URL: https://licensing.services.sage.com/lic/services/LicenseService/
   • aatrix.com
2. Follow the instructions if you are getting a Sage 50 Activation Problem.
3. If you have a 32-bit operating system, click the Program Files option
4. Follow the files that should be let through the firewall & embedded in the list named antivirus exceptions:
5. Ports 1583, 443, 3351
6. Search for the program path:
   • Peachw.exe
   • PeachtreePrefetcher.exe
   • SmartPostingService[Version].exe
   • PeachUpd.exe
   • SageReg.exe
   • Sage.overdrive.cloudbackup.exe
7. Check the file named OverDriveData.txl
8. Search the C:\Program Files (x86)\Common Files\Sage Data Exchange
   • Sage.Data.Exchange.Client.exe
   • SageOverDrive.exe
9. Find the C:\Program Files (x86)\Common Files\Sage Data Exchange:
   • Sage.Data.Exchange.Client.exe
   • SageOverDrive.exe
10. Check the data path: OverDriveData.txt file
11. Fill in the Sage URL exceptions that might be blocked or prevent Sage from downloading
12. So, locate the Program Files below, if a 32-bit OS, find the file peachw.exe.config & write an exception for every URL that appears in the file

Solution 5: Check if there is a black server name or a wrong name in ~PVSW~.LOC file

1. Find the data path
2. Now, launch the ~PVSW~.LOC file through Notepad
3. Change the wrong server name with the right one

Solution 6: Check the network communication issue

1. Open the workstation
2. Search by server name
3. Now hit on Windows key+R button on the server to open the Run window
4. Enter cmd
5. Hit OK
6. Enter ipconfig
7. Hit the Enter key
8. Note down the IPv4 Address
9. Enter Hostname
10. Hit the Enter key
11. Remember the system name, then open the workstation and repeat the steps
12. Enter Ping[server computer name]
13. Hit the Enter key
14. Check the workstation gets a response with a Server IP address
15. Repeat the same process

Solution 7: Check the confirmation files

1. For this, open the system
2. Locate
3. 2018 release
4. – C:\Program Files\Common Files\Peach or C:\Program Files (x86)\Common Files\Peach
5. 2019 release
6. – C:\ProgramData\Sage\Peach
7. Now, open the configuration file for the Sage 50 version
8. Check the line with DATAPATH with the active mapped drive & the company folder, if required
9. Check the line with DATAPATHUNC=
10. It comprises an active server name instead of the old server name; if not, then apply the changes. Hit the File button and click Save.
11. Now, close the Notepad window

Solution 8: Uninstall Pervasive PSQL

1. Locate the Program & Features button
2. Now click Uninstall Pervasive PSQL[version] or Actian PSQL[version]
3. Delete or give a name to the folder below if present:
   • C:\ProgramData\Pervasive Software
   • § C:\Program Files (x86)\Pervasive Software
   • § C:\Program Files\Pervasive Software)
4. Now type Regedit in the run window to open Registry Editor, and then search for the below field and rename it.
   • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Pervasive Software
   • HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software
   • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Actian
   • HKEY_LOCAL_MACHINE\SOFTWARE\Actian
   • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Pervasive Software
   • HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software
   • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Actian
   • HKEY_LOCAL_MACHINE\SOFTWARE\Actian

Condition 1: Error: “Sage 50 cannot connect to its database, Actian Zen, on computer [server].”

Sage 50 cannot connect to its license on the server. Ensure that the computer is logged in, the database service is running, and the firewall allows Sage 50 and Pervasive to pass through. Click Help for more details and Retry to reconnect.

Reasons why Sage 50 fails to connect with the database, the Actian Zen on the computer [server]?

1. The Actian service has stopped running on the server.
2. The server cannot be pinged.
3. The network location/profile is set to Public instead of Private on either the workstation or server.
4. The firewall is blocking the program.
5. The server name in the PVSW.LOC file is incorrect.
6. DFS is being used for the mapped drive.
7. Windows Management Instrumentation (WMI) is damaged.
8. An incorrect data path is set on the workstation.
9. The server and workstations are running different versions.
10. More than one NIC is enabled.
11. IPv6 is being used instead of IPv4.

Resolving the issue of Sage 50’s inability to connect with the database on the Actian Zen on the computer [server].

If you encounter “Sage 50 cannot connect to its database on 169” or 192, etc., the error displays the computer name as the initial three digits of an IP address.

1. Restart the Actian database engine on the server if it’s hung or stopped.
2. On the server or standalone computer, confirm the correct data path.
3. If the network profile is set to Public, switch the radio button to Private under Network Profile.
4. Allow Sage 50 files through the firewall configuration.
5. Replace the incorrect server name with the correct one in the ~PVSW~.LOC file.
6. Ping the server by name from the workstation.
7. Map the drive using the IP address.
8. Uninstall and reinstall the Actian database engine on the server.
9. Disconnect the DFS share and map the drive using the standard UNC path because Sage 50 cannot use the DFS share.
10. Ensure that both server and workstation(s) are updated to the same version.
11. Check if IPv6 is being used instead of IPv4.

Condition 2: Error: “Sage 50 cannot connect to its database on computer [computer name].”

If you receive the error message “Sage 50 cannot connect to its database on computer [computer name]” after installation or during the installation process, there may be issues with the server or the network settings. When attempting to ping the server by either name or IP address, you may receive “Request Timed Out” or “Not recognized as an internal command” error messages.

However, a successful ping from 127.0.53.53 may be returned when pinging the server by name. These issues could be due to various factors, such as an incorrect data path on the server or workstation, a misconfigured firewall, or an incorrect server name in the ~PVSW~.LOC file. Other potential problems could be a damaged Windows Management Instrumentation (WMI) or running different versions of Sage 50 on the server and workstation(s).

Reasons for the error message “Sage 50 unable to connect to its database on computer [computer name]”

Possible reasons for the error could be:

• A disabled, damaged, or blocked network connection
• Non-functional Domain Name System (DNS)
• Non-running Actian / Pervasive service on the server
• Using the UNC path instead of the mapped drive letter
• Using the IP address instead of name resolution for the mapped drive
• DNS servers provided by the ISP are returning 127.0.53.53 for internal network computers
• Computers are not a part of the domain.

Solutions for the “Sage 50 unable to connect to its database on computer [computer name]” Error

The “Sage 50 unable to connect to its database on computer [computer name]” error can be resolved by checking the database engine, firewall, and antivirus settings.

Step 1: Please verify that Actian is currently running on the server.

1. In case the service is already running, kindly opt to restart it.
2. You can start or stop the Actian/Pervasive service as per your requirement.
3. If the issue persists, we recommend uninstalling and then reinstalling the Actian database engine.
4. Once done, please launch the program and check if the issue has been resolved.

Step 2: Please ensure that the shared folder has the appropriate permissions.

• Please ensure that the shared folder has the appropriate permissions. Additionally, kindly verify if the data file permissions are configured correctly.

Step 3: DNS Problem

If you are experiencing DNS issues, you can try pinging the server by its hostname from a workstation or vice versa. If the ping request times out or fails, it may indicate a network communication issue that requires the attention of your IT professional to correct.

Workaround: Update the host’s file

Note: This is a temporary fix. If the server loses or renews its IP Address, the host’s file must be updated again.

Step 4: UNC path is being used instead of a mapped drive letter

Instead of using a mapped drive letter, the UNC path is being used. To resolve the issue, you can right-click on the mapped network drive and select “Disconnect”. After disconnecting, you can remap the drive.

Step 5: Disable the anti-virus

To install the program, you may need to disable your antivirus. After disabling the antivirus, verify that you can successfully install the program. Note that once the anti-virus is disabled, you should also be able to ping by both IP address and name.

Step 6: The IP address is being used instead of name resolution for the mapped drive

The mapped drive is using the IP address instead of name resolution. It is not recommended or supported to map Sage 50—U.S. Edition by server IP address. For optimal performance, it is recommended to map using the server hostname.

Step 7: The workstation is not part of the domain network.

If the server or host computer is on a domain and the workstation receiving the error is not, the above error message will be displayed. To connect the workstation to the domain, please seek assistance from an IT professional.

Step 8: The server returns the IP address of 127.0.53.53.

If the server returns an IP address of 127.0.53.53, it indicates an issue with the DNS server configuration.

Step 9: Verify network is set to ‘Private. ‘

1. To confirm if the network is set to ‘Private,’ right-click on the ‘Network & Internet Settings‘ icon, which is typically located on the start bar (the symbol of a computer with a cable going to it).
2. Then, click on ‘Open Internet & Network Settings. ‘ Check that the ‘Network Status‘ is set to ‘Private‘ or shows the appropriate domain.
3. If it is set to ‘Public,’ it is advised to contact IT support to change the network settings to ‘Private.’
4. After verifying or changing the network settings, you can hit ‘Cancel‘ to see if the installer finishes, or run the installer again.

Conclusion!

Here, the write-up is complete! Now, if you face any difficulties while implementing the above methods or if you have any other doubts, then get connected to the professional team. The experts are here to assist you with the best resolutions. Connect now, the Sage 50 Live Chat team.

Frequently Asked Questions