Resolved Activation Key for Sage 50 is Invalid or Could not be Read

Activation Key for Sage is Invalid or Could not be Read

Getting a problem for the activation key for sage 50 and getting the error message “Activation key for sage 50 is invalid or could not be read”, if yes then don’t worry you are on the right page and in the below article we will discuss the causes and solutions.

Let’s come to the causes first. Below are some causes that result in the error.

  • Problem with Windows Management Instrumentation
  • Copying the data path from one server to another
  • Opening older version of the program
  • Incorrect serial number
  • Missing file in the data path
  • Option .dat is hidden
  • Pervasive database engine is damaged
  • Incorrect data path
  • Incorrectly set permission
  • Program is not activated on the server
  • The pervasive database engine is not running as service

The Solution of the Error Sage 50 is invalid or could not be read

Below are some steps through which you can resolve the above error.

Steps 1: Activate the program on the server

  • Open sage and activate the same
  • Make sure you didn’t receive the message again

Steps 2: Pervasive on server

  • Stop the pervasive and restart the pervasive service on the server
  • Reboot the computer/server
  • To work as system device configure the pervasive database engine

Steps 3: Verify Permissions (Windows 8, Windows 10, server 2012)

  • Select properties after right-clicking on the shared folder
  • Choose the sharing tab
  • Go to Advanced Sharing
  • Select share this folder box
  • Click Permissions
  • Click Add
  • Type in the individual username or groups which that needs access to sage 50
  • Provide each user/group Full control
  • Click ok once you are on Advance sharing window
  • Go to the Security tab
  • Check if administrator and systems have full control
  • Click ok

Steps 4: Configure firewall and anti-virus

  • Allow sage and pervasive through the firewall and make it exclude it from antivirus

Steps 5: Verify data path

  • Make sure that the server and the workstation having the correct data path

Steps 6: Pervasive is damaged as multiple versions of pervasive installed or wrong version is installed on the server

  • Manually first uninstall and reinstall the service

Steps 7: Missing files in the data path due to bad or incomplete install

  • Run the repair program
  • Verify if you can activate and open sage

Steps 8: Older version of Peachtree using Btrieve

  • Restart the computer
  • Open the sage on the server
  • Go to Help>>About sage 50 accounting
  • Close sage
  • Open the run window by pressing Window +R keys
  • Type msc
  • Stop sage50smartposting and Pervasive PSQL Workgroup Engine
  • Now you should be able to access the older version of peachtree
  • Once all tasks finish in old peachtree press Windows+R keys
  • Type msc
  • Start Sage50Smartposting and Pervasive PSQL Workgroup Engine
  • Check if you are able to access sage without any error

Steps 9: Restart WMI

  • Search to the data path
  • Rename xml
  • Change the file name to xml
  • Stop and restart pervasive from task manager
  • Right click on WMI(Windows Management Instrumentation ) and select Restart
  • Right-click on Pervasive PSQL Workgroup Engine and choose start
  • Close services windows and Open Sage
  • Check if you can activate sage now

How to Contact us

Still, struggling to solve the error? Don’t worry just dial our Sage 50 technical support number 1800 964 3096 and our technical team will be there to help you to solve your issues to work you without errors. You can also do a Sage 50 live chat with our team or email us at [email protected] and we will get back to you soon.

Related Posts

Further Reading