Error: 1443, Severity: 16, State: 2. Database mirroring has been terminated for database 'databasename'. This is an informational message only.
Error: 1474, Severity: 16, State: 1. Database mirroring connection error 4 'An error occurred while receiving data: '64(for 'TCP://servername:5022'.
Workaround on our environment to fix the issue.
1. Verify whether you are able to register the server instance on both principal and mirror servers
2. Add entry to hosts.etc file on both servers (principal,mirror)
3. Local Area connection - status - properties - select IPV4 - properties - advanced - DNS
Under Append these DNS suffixes - Click Add and add the DNS Suffix of the principal server on mirror server and vice versa.
4. Try configuring mirroring
Troubleshooting the following Error:
Mineblocksgames. Ultimate typernitrotypecheats. Box 36, Springville, Utah - 84663, USA +1 888 900 4529.
- Syntax error converting the varchar value to a column of data type int. Error Message: Server: Msg 245, Level 16, State 1, Line 1 Syntax error converting the.
- Msg 18456, Level 14, State 1, Server server name, Line 1 Login failed for user ' We should know that the ' State ' will always be shown to be ' 1 ' regardless of the nature of the problem.
- SysTools Inc. Box 36, Springville, Utah - 84663, USA +1 888 900 4529.
- Box 36, Springville, Utah - 84663, USA +1 888 900 4529.
What I found that many times experiencing this error in SQL Server's Errorlog, that 'Error: 17189' was only a symptom, and that many times the root cause was the line above in SQL Server's Errorlog.
Case 1:
In the first case shown below, in SQL Server's Errorlog listed right above the 'Error: 17189', listed were I/O stalls occurring. In this case, the Storage Administrator found that an I/O switch to the SAN was overloaded, which contributed to SQL Server freezing up. Which no logins would occur on the database instance for the next minute.
Case 2:
Sql Server Error 1474 State 1017
Sql Server Error 1474 State 1 3
Sql Server Error 1474 State 1017
Sql Server Error 1474 State 1 3
In this case, the memory was set to high (less of 40% of the memory was used), and the 'lock pages in memory' option was not set. The following error kept appearing in SQL Server's Errorlog :
Sql Server Error 1474 State 1 Key
By correcting the 'max server memory' setting, and setting in the group policy editor to 'lock pages in memory', the 'Error: 17189' disappeared.
