Let’s start our article about the Sage 50 could not be started. If you use Sage 50 in the United States, Canada as well as UK which is likely given that you are reading this, you may have encountered examples where Sage 50 didn’t launch as planned.
Sage 50 is available in desktop versions with any time & anywhere cloud services. The program is an outstanding accounting solution that makes your work easier but there are situations when you may come across certain issues that may hamper your work.
Sage 50 Unable to Started
One such error is Sage 50 accounting could not be started. These issues are some technical errors that are caused The database engine used by Sage 50 U.S., Pervasive, frequently causes this by either not starting at all or going missing. Another related issue Sage 50 stopped working. You will encounter this Sage 50 error in the U.S. Edition of Sage. You can reboot your system and try to open it again. You will receive the following error message getting displayed on your computer system when you encounter this Sage 50 error.
- An error occurred: “Sage 50 cannot be started please reboot.”
- Error: “There was an issue starting Sage 50 Accounting.
- This error occurs when Pervasive PSQL is not running or needs to be restarted: “Sage 50 cannot be started“.
These are very technical and tedious errors that mainly arise if you are using an older version of Sage 50. Thus it is highly recommended that you update the program as soon as possible as they will fix your issues.
Warning: Always keep in mind to take a full backup of your data as, if not done right then your system might even freeze without any recovery.
Understanding Why Sage 50 Accounting Software Won’t Start
There are various causes that are responsible for this Sage 50 could not be started, like.
- Damaged files and corrupted folders.
- Outdated files and folders.
- Company folders have some damaged reports.
- Issues with Pervasive/Actian Zen.
- The server network is Public.
- Damaged shortcuts.
- Issues with the compatibility mode setting for the shortcut.
Resolution Steps to Fix the Sage 50 Accounting Could Not be Started Issue
The Sage experts have suggested more than one solution for this Sage 50 software startup failures. In case this error persists, then you can try to resolve it by following any one of the solutions which are mentioned below.
Option 1- Restart pervasive on the computer that hosts the data
Error Sage 50 cannot be started when Actian is not running or needs to be restarted
A: Standalone setup
- You have to reboot the computer. In this way, you can fix the issue in a stand alone setup.
- However, the next sections may also be required.
B: Restart Actian/Pervasive
- Begin by clicking the Windows + R key to open a Run line.
- Then you have to type services.msc and then you have to select OK.
- Now you have to right-click Actian PSWL Workgroup Engine (or Pervasive or release 2019 and earlier)
- Then you have to select Restart (if Restart option is not there, then you have to select Start).
- Now you have to double-click Actian Workgroup Engine (or Pervasive PSQL Workgroup Engine) and then you have to select the Recovery tab.
- In the First failure you have to select restart the Service and Second failure drop-down boxes.
- To reset after 1 day you have to set Reset Fail Count and then you have to click on OK.
- Now you can verify Sage opens on the server and the workstation without error.
Option II- Find and Restart Actian service
Error: “Sage 50 cannot be started…” and the Actian service is missing or cannot be restarted.
Section 1: Verify Sage 50 is installed at the server
- Click on Windows + R.
- Then you have to Type Appwiz.cpl and then click on OK.
- Now you have to look for Sage 50 Accounting version.
- If the program is not listed, follow Installation Instructions.
- Continue to the next section if the program is not listed.
Section 2: Manually reinstall Actian
- Uninstall and reinstall the Actian database engine.
- Then open the program and verify that the issue is resolved.
Section3: Damaged Operating System Component
- Follow Error: “There was a problem activating…” when Operating System is damaged
- You will have to get that repaired if there is any kind of issue with any of the components mentioned in that document.
Section 4: Avast Cleanup is installed
You can consult the program documentation or contact Avast support to Ignore both Sage 50 Accounting and Actian PSQL Workgroup Engine in the list of sleeping programs.
Option III: Compatibility Setting
- Right-click on the Sage 50 icon on your desktop.
- Select the properties tab.
- Click on “Run this program in Secure mode“.
- Now an editor will open. Type in the key code as [k0w16] and press continue.
- Press OK and close the Sage 50 properties window.
Option IV: Recreate the shortcut
- Right-click on the Sage 50 shortcut and select the delete button.
- Don’t worry we are not going to delete the program altogether.
- Browse for its Program Path.
- Locate the icon and right-click on it.
- Choose the option to recreate a Sage 50 accounting shortcut.
- Locate the exe file and right-click on it.
- Click on the Send option and then go to the desktop.
- This way you can create a new shortcut on the desktop.
- You can even rename the newly created shortcut to distinguish it from the older one.
Option V: Reinstall the application and use Run as Administrator
- Reboot your system and log in to the system as an Administrator so that you can have the access to all the files and folders.
- Now browse to the location, “C: SageSage50_20xx_xprogram-files(where xx is the year and _x if it exists is the product update number)”.
- Right-click on the exe file.
- Go to the Run as Administrator.
- Click on the Repair option when you receive a prompt.
- Let the installation process complete.
The solutions above are suggested by Sage experts who have years of experience in resolving all kinds of Sage issues. In such situations, you can also try to update your software.
Thus, if you are still using an older version of Sage 50 then you can always ask for Sage 50 Consultant. If you have queries or you need some assistance fixing Sage 50 could not be started issue, then call a toll-free number. They will immediately get in touch with you and help you in resolving all your Sage issues in a minimum wait of time.
FAQ’s
How to run sage as an administrator to resolve Sage 50 accounting could not be started?
To run as an administrator, follow the steps mentioned below:
● First, go to the desktop.
● On the desktop right-click on the Sage product icon.
● Then choose Properties.
● After selecting properties choose the Compatibility tab.
● If desired, click the Change settings for all users option at the bottom of the screen.
● Now check the box next to Run this software with administrative privileges.
● Finally, select Apply and then click OK.
What’s the most common solution to Sage 50 Accounting doesn’t start?
This is the most common solution to Sage 50 Accounting could not be started or doesn’t start are:
● While using Sage on a network and your workstation still gets the error but the server doesn’t.
● You’ll need to restart the pervasive on the workstation.
● Pervasive should be restarted on the data-hosting computer.
● Open the program on that computer to see if the error has been resolved.
How to run an advisor diagnostic tool to fix the Sage 50 Accounting not Starting issue?
To fix the sage 50 accounting cannot starting problems, take the sage advisor diagnostic test
● First, click on the start option.
● Then go to the program.
● Now open Sage 50 accounting.
● After Sage 50 accounting is opened select Sage 50 resources.
● Go to the Help menu.
● Once on the help menu go to the option technical Consultant utilities.
● Finally, go to the diagnostic tool.
● Now they’re on the button, click Agree.
● Select the test from the list below and choose Run All Selected Tests.
● Then check Error .NET Framework: To complete this test, scroll to the bottom.
● Continue to the next test result if no.NET errors are found, then test your company’s location.
● Now if you see OK at the end of each company folder found, your companies are in the right place.
● Check for required files: Your data path files are fine if they all have the same name, size, and modified date.
● Finally, verify the lock file.
● Once done Check for product INI files.
