SQL Server Error: 53
[Microsoft)[SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
Note We enacted a disaster recovery system to protect your databases on SQL Server. Disaster recovery is a promise that we make to you that your data is stored in two Microsoft data centers in different regions to allow us to be resilient to disasters.
- In Access 2013, open the Access app that contains the data to which you want to connect.
- Click File, click Info, and then click the Manage button in the Connections section.
- Click Disable All Connections.
- Click Yes when you receive the message "Disabling all connectivity will prevent external programs or reports from accessing the app and may cause other applications to break. Are you sure you want to disable all connectivity?"
- Click the Manage button again.
- Select From Any Location.
- Select Enable Read-Write Connection or Enable Read-Only Connection.
- Click View Read-Write Connection Information or View Read-Only Connection Information to view the new connection information.
- Reconnect to the data in the Access app using the new connection information.
For information about how to connect through the ODBC administrator see Administer ODBC data sources.
If you are connecting from a Microsoft Access desktop database, you can use code to create a connection that does not use a data source name (DSN). For more information about how to create a DSN-less connection, see How to create a DSN-less Connection to SQL Server for linked tables in Access.
Note In the code in the DSN-less connection article, you must change the DRIVER from "SQL Server" to "SQL Server Native Client 11.0" as follows:
stConnect = "ODBC;DRIVER=SQL Server Native Client 11.0;SERVER=" & stServer & ";DATABASE=" & stDatabase & ";UID=" & stUsername & ";PWD=" & stPassword
You may have to contact the person who created the connection in order to re-create the connection to the Access app data.
Article ID: 2922359 - Last Review: 31 Mar 2014 - Revision: 1