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. Remote Desktop and log into the database server. Start SQL Server Management Studio. Right-click on your database and select Properties. Click on the Mirroring page and then click the Failover button. The database will now be listed as (Mirror, Synchronized / Restoring) and will be accessible from the other MS SQL Server. The server instance Partner rejected configure request; read its error log file for more information. The reason 1460, and state 1, can be of use for diagnostics by Microsoft. This is a transient error hence retrying the request is likely to succeed. Correct the cause if any and retry. Goto services.msc and check the sql server is running under which account. Make sure that sql server and sql server agent services should run with same credentials. In the mirror database server you should do the same step as step 1. Give the same credentials as in principal server. (Microsoft SQL Server, Error: 1456) As usual, I asked them to check ERRORLOG and found below on Principal Server 2018-03-15 07:16:12.040 spid49s Database mirroring is inactive for database ‘test’.
-->Applies to:
Returns the state number of the error that caused the CATCH block of a TRY...CATCH construct to be run.
Syntax
Note
To view Transact-SQL syntax for SQL Server 2014 and earlier, see Previous versions documentation.
Return Types
int
Return Value
When called in a CATCH block, returns the state number of the error message that caused the CATCH block to be run.
Returns NULL if called outside the scope of a CATCH block.
Remarks
Some error messages can be raised at multiple points in the code for the Microsoft SQL Server Database Engine. For example, an '1105' error can be raised for several different conditions. Each specific condition that raises the error assigns a unique state code.
When viewing databases of known issues, such as the Microsoft Knowledge Base, you can use the state number to determine if the recorded issue might be the same as the error you have encountered. For example, if a Knowledge Base article discusses an 1105 error message with a state of 2, and the 1105 error message you received had a state of 3, your error probably had a different cause than the one reported in the article.
A SQL Server support engineer can also use the state code from an error to find the location in the source code where that error is being raised, which may provide additional ideas on how to diagnose the problem.
ERROR_STATE may be called anywhere within the scope of a CATCH block.
ERROR_STATE returns the error state regardless of how many times it is run, or where it is run within the scope of the CATCH block. This is in contrast to functions like @@ERROR, which only returns the error number in the statement immediately after the one that causes an error, or in the first statement of a CATCH block.
Sql Server Error 1474 Severity 16 State 1
In nested CATCH blocks, ERROR_STATE returns the error state specific to the scope of the CATCH block in which it is referenced. For example, the CATCH block of an outer TRY...CATCH construct could have a nested TRY...CATCH construct. Within the nested CATCH block, ERROR_STATE returns the state from the error that invoked the nested CATCH block. If ERROR_STATE is run in the outer CATCH block, it returns the state from the error that invoked that CATCH block.
Examples
A. Using ERROR_STATE in a CATCH block
The following example shows a SELECT statement that generates a divide-by-zero error. The state of the error is returned.
B. Using ERROR_STATE in a CATCH block with other error-handling tools
The following example shows a SELECT statement that generates a divide-by-zero error. Along with the error state, information that relates to the error is returned.
Examples: Azure Synapse Analytics and Parallel Data Warehouse
C. Using ERROR_STATE in a CATCH block with other error-handling tools
The following example shows a SELECT statement that generates a divide-by-zero error. Along with the error state, information that relates to the error is returned.
See Also
sys.messages (Transact-SQL)
TRY...CATCH (Transact-SQL)
ERROR_LINE (Transact-SQL)
ERROR_MESSAGE (Transact-SQL)
ERROR_NUMBER (Transact-SQL)
ERROR_PROCEDURE (Transact-SQL)
ERROR_SEVERITY (Transact-SQL)
RAISERROR (Transact-SQL)
@@ERROR (Transact-SQL)
Errors and Events Reference (Database Engine)
Symptoms
Assume that you use a Transact-SQL statement to set database mirroring in SQL Server 2016. After this is configured, you see continuous errors that resemble the following in the SQL Server error log:
<Principal>
date time spid47s Error: 1479, Severity: 16, State: 1.
date time spid47s The mirroring connection to 'TCP://Node02.contoso.com:5022' has timed out for database 'MirrorDB' after 10 seconds without a response. Check the service and network connections.
date time spid47s Database mirroring is inactive for database 'MirrorDB'. This is an informational message only. No user action is required.
date time spid47s Database mirroring is active with database 'MirrorDB' as the principal copy. This is an informational message only. No user action is required.
</Principal>
<MIRROR>
date time spid53s Error: 1474, Severity: 16, State: 1.
date time spid53s Database mirroring connection error 4 'An error occurred while receiving data: '10054(An existing connection was forcibly closed by the remote host.)'.' for 'TCP://Node01.contoso.com:5022'.
date time spid44s Database mirroring is inactive for database 'MirrorDB'. This is an informational message only. No user action is required.
date time spid44s Database mirroring is active with database 'MirrorDB' as the mirror copy. This is an informational message only. No user action is required.
</MIRROR>
Cause
This error may be logged when the network is functioning correctly but the database has had no activity for 90 seconds. SQL Server checks and then closes the database mirroring connection when there is no database activity for 90 seconds. When database activities resume, a connection is reestablished, and database mirroring starts working again.
Sql Server Error 1480
Resolution
The update that fixes this issue is included in the following cumulative updates:
Cumulative Update 1 for SQL Server 2016 Service Pack 1
Cumulative Update 4 for SQL Server 2016
About SQL Server 2016 builds
About SQL Server 2016 builds
Each new build for SQL Server 2016 contains all the hotfixes and all the security fixes that were included with the previous build. We recommend that you install the latest build for SQL Server 2016.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the 'Applies to' section.
References
Learn about the terminologythat Microsoft uses to describe software updates.