Sage 50 Cannot be Started when Pervasive PSQL is not Running

Sage 50 cannot be started

The corporate world, especially small and mid-size organizations or growing start-ups are increasingly using Sage for their important projects related to finance and accounting. The Sage software and its various tools make work quite smooth and faster. Sage 50 has many features that can be understood and used easily by a user from a non-accounting background too. One can learn all about Sage while working on the software.

There can be situations where a user might face doubts or issues while working on the Sage software. Contact the proficient team at Accounting Advice for detailed instructions regarding any Sage related issue. One can contact the Sage 50 tech support via this toll free number . Let’s talk about more about one such Sage related problem.

Sage Error Messages Displayed

This ‘Sage 50 cannot be started’ when Pervasive PSQL is not running or needs to be restarted error can be a result of power failure or while re-starting the computer.

Also, the Event Viewer may show the following messages:

  • Source = “Pervasive PSQL
  • General = “Error creating grace period record: -2147024891“.

The program crashes after opening immediately on the server. Program may open on a second attempt.

Reasons of Sage 50 Cannot be Started when Pervasive PSQL is not Running

  • On the host computer, Pervasive PSQL is not running.
  • Even after re-starting the computer, Pervasive PSQL did not start.
  • After installation of a new program update, Pervasive PSQL did not restart.
  • Hanging of Pervasive PSQL
  • Disabling of Pervasive
  • Operating system upgradation
  • Pervasive on server was stalled due to crash of work station
  • Windows 10 updates can also lead to this error.

Also Read: Sage 50 Cannot Install the Update SageMgr.exe Error With Window 10 Pro

Steps to Fix Sage 50 Cannot be Started when Pervasive PSQL is not Running

  • Setup in a Stand-Alone way
    • The computer has to be re-booted. In a stand-alone setup, this might troubleshoot the problem. If not, go to the next step.
  • Pervasive PSQL has to be re-started.
    • If the user is using Sage 50 on a network, follow the below methods first at the server. Make sure that Sage has been closed on all systems before going forward.
  • WINDOWS+R keys has to be pressed
  • msc has to be typed in.
  • Choose OK.
  • Pervasive PSQL Workgroup Engine has to be right-clicked and choose Restart. (If Restart tab is not there, choose Start).
  • Pervasive PSQL Workgroup Engine has to be double-clicked.
  • Recovery tab has to be chosen.
  • Choose ‘Restart the Service in the First failure and Second failure’ in the drop down boxes.
  • Reset Fail Count has to be set after 1 day.
  • Choose OK.
  • Check if Sage opens on the server and on the workstation without any issues.
  • Check if Windows 10 Updates were Successfully Done

Automatically the services will not be started by rebooting. It will have to start manually. Take help from Sage technical support at Accounting Advice.

Final Words!

We hope the troubleshooting options mentioned above would help you a great deal to fix the ‘Sage 50 Cannot be Started when Pervasive PSQL is not Running’ issue on your computer. If you are still unable to resolve this decline error or if you encounter any difficulties in performing the steps outlined above, we recommend that you should consult with an experienced Sage professional.

contact us 1 24

Frequently Asked Questions (FAQs)

How can I Reinstall the pervasive Engine?

Please follow the steps below-
💠 Browse to the path- C:>Sage >Sage 100 20XX and open the Sage installation folder  
💠 Browse to the folder labelled Pervasive Min
💠 Run the MSI
💠 Click Next
💠 Accept the license agreement
💠 Click Next
💠 Click on Run as a Service
💠 Click Next
💠 Click on Complete
💠 Click Next to proceed
💠 Click on the Install button to proceed with the installation 
💠 Wait till the installation is complete
💠 Click Finish
💠 Now try to install the software

What causes the Sage 50 Pervasive Invalid Date Error?

Many technical issues may contribute to this error. Some of these are as follows-
💠 Trying unsuccessfully to change the fiscal year date.
💠 The transaction was posted on a date before the fiscal end date.

Why can a system admin lose access to an instance of SQL Server?

Some major reasons for this issue are listed below-
💠 The Windows Groups that are parts of the sysadmin fixed server role may have been deleted by mistake.
💠 The account of the system administrator may have been  disabled 
💠 The password used for  the system administrator account may be  incorrect
💠 The login details of the sysadmin fixed server role members may have been removed by mistake.
💠 The login credentials of the sysadmin fixed server role members may be assigned to those who may have left the organization or to those who are not available.

How can I Stop and Restart the Pervasive service from the Task Manager?

Please follow the steps below-
💠 Make sure to close the Sage application on all systems.
💠 On the taskbar, right click on a blank spot, 
💠 Select Task Manager 
💠 Please note- To open the task manager, you can also press the Ctrl + Alt + Delete buttons together on your keyboard.
💠 Click on the Details tab 
💠 Locate exe.
💠 Select  the concerned process and click on End Task.
💠 Click on the Services section at the top
💠 Arrange by name and locate psqlWGE.
💠 Right click on it
💠 Click Start.

Sage Chat help desk
Sage Chat help desk

Customer Service

AVAILABLE 24/7

Chat with us

HOURS OF AVAILABILITY VARY
Related Posts:

Report Your Issue

(Didn't find what you were looking for! Report your issue and get customized help from our Sage experts.)



    Sage Version

    Edition Year

    No of User: Licence

    Operating System:

    Help Needed:

    Write your Issue

    Further Reading