Troubleshooting the following Error:
Box 36, Springville, Utah - 84663, USA +1 888 900 4529. 2016-01-22 04:48:36.53 spid118 Error: 1456, Severity: 16, State: 3. 2016-01-22 04:48:36.53 spid118 The ALTER DATABASE command could not be sent to the remote server instance ‘TCP://Witness:5022’. The database mirroring configuration was not changed. Verify that the server is connected, and try again. Click below button to copy the code. 2014-01-08 18:11:22.87 spid3s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file C:Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLDATAPROD.mdf in database PROD (6). The OS file handle is 0x00098C. The simplest way reproduce the error is with the following script: DECLARE @DecimalValue DECIMAL(4,2) SET @DecimalValue = 100.00 Since the precision of the. If a system database encounters these errors, the SQL Server instance will not start and you cannot connect to this instance of SQL Server. This could also result in a SQL Server failover cluster resource to go offline. If the problem is related to your SQL Server FileStream filegroup, then you will notice that only the full directory path is.
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:
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 1017
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.