-->
This article helps you resolve the problem where mirrored databases are left in a Disconnected or In Recovery state.
Original product version: SQL Server
Original KB number: 2490051
- Microsoft SQL mirror setup – error 1474 This blog will show you issues that may occur when working with a Microsoft SQL mirror. This blog will also show you how to solve it and why you need to make sure everything is setup exactly the same way.
- Error: 1443, Severity: 16, State: 2. Error: 1474, Severity: 16, State: 1. Which helps me as well as others while surfing about SQL Server. Some articles are.
- Error: 1418 – Microsoft SQL Server – The server network address can not be reached or does not exist. Check the network address name and reissue the command. The server network endpoint did not respond because the specified server network address cannot be reached or does not exist.
PREVENT YOUR SERVER FROM CRASHING! Never again lose customers to poor server speed! Let us help you. Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
Symptom
Consider the following scenario:
Sql Server Error 1474 Severity 16 State 1
You have a computer that is running a secondary instance of Microsoft SQL Server in a two-server database mirror.
CPU usage reaches 100 percent on the computer, and you cannot stop the SQL Server service by using SQL Server Management Tools.
You end the process of the SQL Server secondary instance by using Task Manager.
You restart the secondary instance of SQL Server.
In this scenario, all mirrored databases are in a Disconnected or In Recovery state. Additionally, an error message that resembles the following is logged in the SQL Server error log for each database:
Bypassing recovery for database 'Database Name' because it is marked as an inaccessible database mirroring database. A problem exists with the mirroring session. The session either lacks a quorum or the communications links are broken because of problems with links, endpoint configuration, or permissions (for the server account or security certificate). To gain access to the database, figure out what has changed in the session configuration and undo the change.
Cause
This issue occurs because of problems in the SQL Server database mirroring endpoints.
Resolution
To resolve this issue, use the following methods. If the first method does not resolve the issue, use the second method.
Method 1
Recycle the endpoint on the database mirror. To do this, follow these steps:
Sql Server Error 1480
On the principal database, execute the following SQL script to stop the endpoint:
Execute the following SQL script to restart the endpoint:
Note
If communication between the endpoints does not restart after you execute the scripts, execute the scripts on the database mirror. However, the database may enter a Suspended state after you do this. If this issue occurs, execute the following SQL script:
Method 2
Error 1474 Severity 16 State 1
Delete and re-create the database mirroring endpoints on both servers.