Open Database setup and assign verified DSN to Company and System databases.Enter SQL credentials and test the connection.If server name is used, the program creates System DSN named 32. Verify that System DSN used in ODBC is using the correct SQL login credentials.The connection user ID specified in the system database profile is not valid." If you are running Sage Accpac ERP 5.6, then you probably have seen this error when opening up a company:Įrror: "Invalid user ID. To resolve, the first step is to remove any ODBC connections in ODBC setup in Windows referencing to that database server and set up only the SQL Native Client (or SQL Native Client v10.0). This issue seems to only affect those on Microsoft SQL Server 2005 onwards with Sage 300 ERP 5.6 and up. Finally, before making any changes, please make sure you’ve performed a full backup of your database. We here at Customer Support are not responsible for assisting with these steps and cannot be responsible for errors resulting from changes to the database engine or databases. So if you are not knowledgeable in this area, please do not attempt to follow these steps on your own instead contact an authorized business partner or database administrator for assistance. Please note that the troubleshooting steps below require knowledge of database engines and application databases used by Sage 300 ERP (including Microsoft/Transact SQL, Pervasive SQL, or MySQL, etc.). After that try logging in again.Īnd remember the letters ODBC as you will be seeing a lot of it in this blog.Īlso while logging into Sage 300 ERP, some people have encountered this error: If a DSN doesn’t exist, create the appropriate one. If all is okay on that end, delete the existing ODBC DSN on the problem workstation and re-create it. To troubleshoot, check the SQL driver installed on the bad workstation and make sure the appropriate ones are installed. Complete the configuration of the DSN using the correct settings.Īnother error occurs when logging into Sage 300 ERP you find that the database is locked.Select the appropriate DSN and click Configure.Open Data Sources (ODBC) (on a 64 Bit operating system ensure the 32 bit Data Sources (ODBC) is used.The fix is to configure DSN correctly using the correct database server. You will normally encounter this error when the Data Source Name (DSN) used in database setup points to an incorrect server. The first is Error: “Cannot access database (error=40960). This week, we continue to look at troubleshooting more database errors particularly around issues involving Open Database Connectivity aka ODBC In a previous blog, we took a look at database errors when you cannot connect to database in Sage 300 ERP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |