Sage 50 US

Welcome to the Sage 50 Support Group on Community Hub! Available 24/7, the Forums are a great place to ask and answer product questions, as well as share tips and tricks with Sage peers, partners, and pros.

1 Jun 2017 Recommended

What to do if you can't start Sage 50 US

2 minute read time.

You know that feeling when you’re ready to tackle work, but work isn’t playing along?

If you’re a Sage 50 U.S. user - the odds are pretty good considering you’re reading this - you may have run in to a time where Sage 50 didn’t start as expected. This is often caused by Pervasive, the database engine used by Sage 50 U.S., either not running or missing. There are various error messages that you might see if Sage 50 U.S. won't start, including:

Most common fix

  1. Restart pervasive on the computer that hosts the data.
    - See the steps in our "Error: "Sage 50 cannot be started." when Pervasive is not running or needs to be restarted" KnowledgeBase (KB) article.
    - Note: If you do not restart or find the Pervasive PSQL Workgroup Engine in Services, follow the steps in our "Error: "Sage 50 cannot be started. " and Pervasive is service is missing or cannot be restarted" KB article.
  2. Verify the error is resolved on that computer by opening the program.
  3. If you are running Sage 50—U.S. Edition on a network and the workstation is still getting the error but the server is not, restart pervasive on the workstation.

Still won't start?

If these steps don’t result in Sage 50 U.S. being able to start, visit our Error: "Sage 50 cannot be started. " KB article for additional troubleshooting steps and links to severak KB articles that cover a variety of “Error: “Sage 50 cannot be started…” scenarios.

Pervasive specific help

Need more help with Pervasive-related issues? Just click a linked KB article below to learn more: