Don't let database errors slow down your productivity. Here is how to deal with some of the database issues that Sage 300 Customer Support often gets contacted about.
Error: "Cannot access database Error=49153" with a newly installed server
The "Cannot access database Error=49153" error can occur when logging in, or using Verify in Database Setup, to test the database connection. This is related to a newly installed system not being able to connect to the database and can be resolved by doing the following.
On the SQL Database server, check:
- The SQL Server Service is running
- The TCPIP Static port is set (default is 1433) in SQL Server Network Configuration, Protocols for <service name>, TCPIP properties, IP Addresses tab, and that the TCP Dynamic
- Ports are blank
- Ensure the SQL Server instance is configured to use the correct port (e.g. 1433, static connection)
- The Firewall allows for incoming traffic to the configured TCPIP port.
- Security system (group policy, router) is not blocking the service.=
If these checks do not resolve the error, please continue with the client-side verification steps in our Error: "Cannot access database (error=49153)" during login to an existing system Sage Knowledgebase article.
The information above can also be found in our Error: "Cannot access database Error=49153 with a newly installed server" Sage KB article.
Error: "Invalid database specification"
As our Error: "Invalid database specification" Sage Knowledgebase article mentions, this error is a result of incomplete system configuration and can appear during a new installation, when launching the program. To resolve the error, you will need to configure the default database. This is the screen where you'll make configuration changes, for reference, but keep in mind your values will differ from what's displayed below.
Still need help?
Here are some other Sage Knowledgebase articles for the "Invalid database specification" error:
- Error: "Invalid database specification" occurs when logging into a database
- Error: "Invalid Database Specification" occurs when logging into Sage 300 ERP
- Error: "Invalid Database Specification." when logging in from one workstation only
Error: "Cannot access database (error=49153)" during login to an existing system.
This error occurs as a result of the system not being able to connect to the database and will display as "Cannot access database (error=49153)" when attempting to login.
The steps below should resolve the error when experience during login to an existing system.
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.
Still need help?
If none of the above tests are successful, continue troubleshooting using the Error: "Cannot access database Error=49153" with a newly installed server Sage KB article with a newly installed server to further test the SQL Server.
You can find this information in our Error: "Cannot access database (error=49153)" during login to an existing system Sage Knowledgebase article.