Error 1474 severity 16 state 1 – How we fix it?
Looking for a solution to the Error 1474 severity 16 state 1? We can help you fix it.
Normally, this error occurs during the database mirroring.
At Bobcares, we receive requests to resolve the error as a part of our Server Management Services.
Today, let’s get into the details on how our Support Engineers fix this error
What is Database Mirroring?
In Database mirroring, we can create and maintain the redundant copies of a database. Database mirroring increases the availability of an SQL Server database.
Also, the Database mirroring minimizes the downtime which reduces the data corruption or loss.
There are two copies of a single database in Database Mirroring. The principal server instance provides the database to clients and the mirror server instance acts as a standby that can take over if the principal server has any problem.
When Error 1474 occurs?
Firstly, let’s have a detailed look at the error. Usually, the error occurs while configuring the database mirroring in SQL Server.
Here the network is functioning correctly but the database is not active. The SQL Server checks for any database activity. In case, if there is no activity then it closes the database mirroring connection.
Now, let’s see how our Support Engineers fix it.
How we fix the error 1474 severity 16 state 1?
Till now we’ve discussed database mirroring in detail. Now let’s see how our Support Engineers fix this error.
1. Firstly we verify whether we are able to register the server instance on both principal and mirror servers.
2. Also, we add an entry to the hosts.etc file on both the principal and the mirror servers.
3. Next, we select the DNS section under the Local Area connection and Click Add. Then on the mirror server, we add the DNS Suffix of the principal server and vice versa.
4. After that, we configure the mirroring.
Finally, the error disappears and thus the error is fixed.
[Need any assistance with the mirroring errors? – We’ll help you]
In short, the error 1474 severity 16 state 1 occurs during the database mirroring. In today’s write-up, we discussed errors and saw how our Support Engineers fixed it for our customers.