Invalid Database Specification

Problem Details:

Invalid Database Specification error when launching Sage



1) The most common culprit – ODBC connection.  If you have recently upgraded from Pervasive to MS Sql, ensure that your Pervasive ODBC connection has been removed and that your MS SQL Native Client connection is valid. 

2) Make sure that you are running Sage as an administrator.  Right click on the Sage shortcut and select ‘run as administrator’, or make your Sage shortcut run as an administrator all the time, by editing the advanced properties of the shortcut.

3) Logon to your workstation as the administrator and run the regacc utility. 

4) Ensure the user has adequate rights to the database folder. This is different than the shared data folder – it is the actual location of the mdf files (sql database files).

5) Check the event viewer for an indication of the source of problem. For example, we have seen where the error message stated the database is inaccessible because another task has locked it. 

This list is a starting point to troubleshoot this error.  See also:

Invalid Database Specification when Opening One Company

Invalid Database Specification occurs when logging into Sage 300 ERP

Invalid Database Specification when logging into Sage 300


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk