Sage 50 Won’t Connect To Its Database
When installing the Sage 50 accounting system on the system sometimes you are unable to link to the database. There are many reasons associated with the failure to Sage 50 Error Connecting Database , for instance, the Actian service is blocked on the server, failure to ping the server, or network location is set to public rather than private or more. AccountsPro team explaining troubleshooting guide to fix Sage 50 Issue Connect to Its Database moreover user can get help from Sage 50 Error Support team .
- Sage 50 DataBase Connect Failed
- Why Sage 50 Not Connecting To Database
- Solve Sage 50 Database Connection Issues
- Question And Answer Sage 50 Database Issues ,Error , Warning
Database Connection Unsuccessful Sage 50 CA Pro, Premium, Quantum, Accountant
What Are The Causes Of Sage 50 Failure To Connect To Its Database?
- The Actian service is paused on the server
- Failed to ping the server
- When the Profile set 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 in a file named ~PVSW~
- Mapped driver Use distributed file system (DFS)
- Corrupted WMI(Windows Management Instrumentation)
- Workstation contains wrong data path
- If workstations & server is on the 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.
Fix Sage 50 Can’t Connecting To Database Error
How to Rectify Sage 50 Unable to Connect to Its Database?
Following is the list of resolutions to fix the Sage 50 unable to connect to its database error:
Data Path Verification Sage 50
Method 1- Verify the data path:
Check there is a correct datapath on a stand-alone system/server with the below steps:
- The datapath acts as the location with data. If the application is searching in the wrong directory then there might have several issues. Thus it is essential to have the right data path.
- Search the data
- Now find the company directories with the below instructions:
- Hit File button
- Click the Open company tab
- Choose the main Sage page with no companies open option
- Select the option named Open an existing company
- It will appear an active companies history, company file location in the column which says Directory
- Now check data path
- Discover the data path from Sage icon properties with the following instructions:
- Open Sage 50-US Edition
- Choose File button
- Click Open Company tab
- Now drag the box corner to show the full directory
- It includes minus and the company name truncated spell known as the data path
- After this search for the program path by right click on the Sage icon
- Choose 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 two directories. Make sure they should match with exception of the company folder appearing at the data directory end.
- In case there found a wrong data path now fix it by moving data to the data path or fix the data path by changing the data path
Method 2- Check Actian Paused or Hang?
- Hit Windows+R button
- Enter SERVICES.MSC in the search box
- Hit OK
- Now give a right-click on the option named Actian PSQL workgroup engine
- Choose Stop button
- Select Actian PSQL Workgroup Engine and give a right-click on it
- Check workstation can open
Know about Workstations Sage 50 Update Install issue and solutions in many ways.
Method 3- Set Network profile set to Server/workstation:
- Verify the network profile or network location failed to Public
- Search the network connection
- Choose network connection and give a right-click on it
- Click the option named Open Network & Internet Settings
- If the network status is set to the Public network tab
- Now switch to the button named Properties option
- Below the Network, profile tab modify the option from Public to Private
- Click on the back arrow
- Now close the window which says Settings
- Next Test connectivity tab
Method 4- Check Configure Firewall:
- Start firewall configuration to permit access to the below URLs:
- elspv.pervasive.com
- bkpelspv.pervasive.com
- Sage Activation URL: https://licensing.services.sage.com/lic/services/LicenseService/
- aatrix.com
Follow the instructions if you are getting Sage 50 Activation Problem.
- If you have a 32-bit operating system, click the Program files option
- Follow the files that should be let through the firewall & embedded in the list named antivirus exceptions:
- Ports 1583, 443, 3351
- Search for the program path:
- Peachw.exe
- PeachtreePrefetcher.exe
- SmartPostingService[Version].exe
- PeachUpd.exe
- SageReg.exe
- Sage.overdrive.cloudbackup.exe
- Check the file named OverDriveData.txl
- Search the C:\Program Files (x86)\Common Files\Sage Data Exchange
- Sage.Data.Exchange.Client.exe
- SageOverDrive.exe
- Find the C:\Program Files (x86)\Common Files\Sage Data Exchange:
- Sage.Data.Exchange.Client.exe
- SageOverDrive.exe
- Check the data path: OverDriveData.txt file
- Fill in the Sage URL exceptions that might be blocked or prevent the Sage from downloading
- So locate below Program Files, if a 32-bit OS, find the file peachw.exe.config & write an exception for every URL that appears in the file
Method 5- Check if there is a black server name or wrong name in ~PVSW~.LOC file:
- Find the data path
- Now launch the ~PVSW~.LOC file through the notepad
- Change the wrong server name with the right one
Method 6- Check the network communication issue:
- Open the workstation
- Search by server name
- Now hit on Windows key+R button at the server to open the Run window
- Enter cmd
- Hit OK
- Enter ipconfig
- Hit Enter key
- Note down the IPv4 Address
- Enter Hostname
- Hit Enter key
- Remember the system name and then open the workstation and repeat the steps
- Enter Ping[server computer name]
- Hit Enter key
- Check the workstation gets a response with a Server Ip address
- Repeat the same process
Method 7- Check the confirmation files:
- For this open the system
- Locate
- 2018 release
- – C:\Program Files\Common Files\Peach or C:\Program Files (x86)\Common Files\Peach
- 2019 release
- – C:\ProgramData\Sage\Peach
- Now open the configuration file for the Sage 50 version
- Check the line with DATAPATH with active mapped drive & the company folder if required
- Check the line with DATAPATHUNC=
- It comprises of active server name, instead of the old server name; if not, then apply the changes then Hit the File button then click Save
- Now close the Notepad window
Method 9-Uninstall Pervasive PSQL:
- Locate Program & Features button
- Now click uninstall Pervasive PSQL[version] or Actian PSQL[version]
- Delete or give a name to the below folder if present:
- C:\ProgramData\Pervasive Software
- § C:\Program Files (x86)\Pervasive Software
- § C:\Program Files\Pervasive Software)
- Now type Regedit on the run window to open Registry Editor and then search for the below field and rename
- 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
Here the write-up completes! Now if you face any difficulties while implementing the above methods or if have any other doubts then get connected to the professional team. The experts are here to assist you with the best resolutions. Connect now Sage 50 Live Chat team .
FAQs – Database Connection Failed Sage 50 Windows / Linux Server
What If the mapped driver is no longer required?
- Open the system
- Search for C:\ProgramData\Sage\Peachtree
- Now open the DATAPATH line to the right company data path
- Launch the configuration file according to the version
How to fix an error If I am using DFS for a mapped drive?
Do the program compatible with a DFS(Distributed file system)?
To handle this case, there requires a standard UNC path to map to the share on the server.
Can version incompatibility be the reason of unable to connect the database?
How would I fix the corrupted WMI?
- Open the run window
- Enter eventvwr
- Hit OK
- Choose Windows logs
- Click Application