"Cannot access database (error=49153)" in existing system Sage 300
Summary
The following message appears when attempting to login:
“Cannot access database (error=49153)”
This system has been working without error for some time.
These steps require knowledge of database engines and application databases (DBs) used by your Sage product (including Microsoft/Transact SQL, Pervasive SQL, or MySQL, etc.). Customer Support is not responsible for assisting with these steps and cannot be responsible for errors resulting from changes to the database engine or DBs. Before making changes, backup all system and application DBs required for a full restore. Contact an authorized business partner or DB administrator for assistance
Cause
The system is not able to connect to the database.
Resolution
On the client system:
- Open Sage Database Setup and the Company and System Database Profiles. Verify what Data Source or Server name, Login ID and Database names are set.
- Open the 32-bit version of ODBC Data Source Administrator, either from Control Panel > Administrative Tools > Data Sources (ODBC), or from C:\Windows\SysWOW64\odbcad32.exe on 64-bit PCs.
- On the System DSNs tab find the Data Source name or Server name (if Server name is used a 32 is appended to it). Confirm the name of the SQL server in the DSN entry.
- Enter the User ID and password in the SQL Authentication, and confirm that the remaining settings are left as default.
- Test the database connectivity from the DSN.
- If the above test failed, then in a Windows Command Prompt (cmd.exe) ping the server name to test address resolution and connectivity.
- If the ping test is not successful, try using the IP address directly for the ping.
- If successful, enter the IP address in the DSN entry and test the database connectivity again.
- If the database connectivity is not successful with the IP address:
- The User ID being used may not have permission to access the SQL Server.
- The SQL Server may not be prepared to service the connection.
If none of the above tests are successful, then continue troubleshooting using the article:
Error: “Cannot access database Error=49153” with a newly installed server to further test the SQL Server.