Sage 300 Error 49153: Cannot Access Database (Causes and Fixes)

Sage 300 error 49153 (“Cannot access database”) means Sage 300 couldn’t connect to its SQL Server database when you logged in or used Verify in Database Setup. The most common causes are a stopped SQL Server service, an incorrect server name or ODBC data source, a blocked SQL port, or a SQL login without permission. Start by confirming the SQL Server service is running, then check the server name and credentials in Database Setup.

AccountingAdvice.co is an independent third-party service provider and is not affiliated with Sage. The steps below follow Sage’s published knowledge base articles. Confirm them against your Sage 300 version.

What is the Sage 300 Cannot Access Database Error 49153?

Error 49153 appears when Sage 300 can’t open a connection to the SQL Server database that stores your company and system data. It shows up when you log in or when you click Verify in Database Setup.

What are the Causes of Sage 300 Error 49153?

Cause	What it looks like
SQL Server service stopped	All profiles fail
Wrong server name, data source, or credentials	One profile fails
Server name doesn’t resolve	Ping by name fails, by IP works
SQL port not static, or blocked	Fails from workstations, often on new installs
SQL login lacks permission, or SQL isn’t ready	Fails even with the IP address
Missing or mismatched SQL client/ODBC driver	Fails on one PC

Solution to Fix Sage 300 Error 49153: Cannot Access Database

In order to fix the problem, below we have discussed a couple of solutions that you can try on you own

Solution 1: Check if the Problem is due to a Specific Database Connection

1. Open Database Setup from the Start menu (Sage 300 folder).
2. Open the system database profile and each company database profile.
3. Verify the Data Source or Server name, Login ID, and Database values.
4. Click Verify to test each profile.
5. If only one profile fails, its settings are wrong. If all fail, go to Fixes 1 and 5.

Solution 2: Check the SQL Server:

1. Press Windows + R, type services.msc, and press Enter.
2. Find SQL Server (MSSQLSERVER) or your named instance, for example SQL Server (SQLEXPRESS).
3. If the status isn’t Running, right-click it and select Start.
4. Try logging in to Sage 300 again.

Solution 3: Test the ODBC DSN.

On the System DSNs tab, find the Data Source or Server name. If the entry uses a server name, Sage appends 32 to it. Confirm the SQL server name, enter the SQL authentication ID and password, and test the connection.

Solution 4: Ping the server

If the DSN test fails, open Command Prompt and ping the server name, then its IP address. If the IP works, enter the IP address in the DSN and test again.

Solution 5: Check the SQL port and firewall

Set a static TCP/IP port (default 1433) in SQL Server Network Configuration, leave TCP Dynamic Ports blank, and confirm the firewall allows incoming traffic on that port. Also check that group policy or a router isn’t blocking SQL.

Solution 6: Check SQL permissions

The user ID may lack permission to access SQL Server, or SQL Server may not be ready to accept the connection.

Solution 7: Recreate the DSN or reinstall the driver

Sage lists recreating the DSN or reinstalling the SQL Native Client driver as an option. Required drivers vary by version, so confirm yours in Sage’s compatibility documentation. Older guides cite SQL Server Native Client 11.0, while one community report mentions ODBC Driver 18.

Final Words

Sage 300 error 49153 is usually a SQL connection problem, so work from the simplest check (the SQL Server service) to the deeper ones (port, DSN, permissions, driver). If you can’t reach the SQL Server settings or the steps don’t resolve the error, ask your IT administrator or contact AccountingAdvice.co, an independent third-party Sage support provider not affiliated with Sage, at +1-800-964-3096.