SQL Server Errors or Failures from Error: 17197 to Error: 17310

 

Error: 17197, Severity: 16, Login failed due to timeout; the connection has been closed. This error may indicate heavy server load. Reduce the load on the server and retry login.%.*ls
Error: 17198, Severity: 16, Connection failed because the endpoint could not be found. This may result if an endpoint is dropped while a connection attempt is in progress. Attempt to connect to a different endpoint on the server.%.*ls
Error: 17199, Severity: 10, Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag %d. This is an informational message only. No

Error: 17200, Severity: 16, Changing the remote access settings for the Dedicated Admin Connection failed with error 0x%lx, status code 0x%lx.
Error: 17201, Severity: 10, Dedicated admin connection support was established for listening locally on port %d.
Error: 17202, Severity: 10, Dedicated admin connection support was established for listening remotely on port %d.
Error: 17203, Severity: 16, SQL Server cannot start on this machine. The processor(s) (CPU) model does not support all instructions needed for SQL Server to run. Refer to the System Requirements section in BOL for further information.

Error: 17204, Severity: 16, %ls: Could not open file %ls for file number %d. OS error: %ls.
Error: 17205, Severity: 10, File %ls in database %ls has been set to sparse by the file system but does not belong to a database snapshot. The file should be restored to correct the problem.
Error: 17207, Severity: 16, %ls: Operating system error %ls occurred while creating or opening file ‘%ls’. Diagnose and correct the operating system error, and retry the operation.
Error: 17208, Severity: 16, %s: File ‘%s’ has an incorrect size. It is listed as %d MB, but should be %d MB. Diagnose and correct disk failures, and restore the database from backup.
Error: 17253, Severity: 10, SQL Server cannot use the NO_BUFFERING option during I/O on this file, because the sector size for file ‘%s’, %d, is invalid. Move the file to a disk with a valid sector size.
Error: 17255, Severity: 10, Secondary TempDB file ‘%.*ls’ resides on a removable drive and therefore will not be attached during startup.
Error: 17256, Severity: 10, Secondary TempDB file ‘%.*ls’ will not be attached during TempDB startup; Drive check failed with error ‘%ld’.
Error: 17257, Severity: 10, System error while trying to initialize disk info; Error ‘%ld’
Error: 17258, Severity: 10, No free space in the TempDB database
Error: 17300, Severity: 16, SQL Server was unable to run a new system task, either because there is insufficient memory or the number of configured sessions exceeds the maximum allowed in the server. Verify that the server has adequate memory. Use sp_configure with option ‘user conn
Error: 17303, Severity: 16, The session with SPID %d was found to be invalid during termination, possibly because of corruption in the session structure. Contact Product Support Services.
Error: 17308, Severity: 16, %s: Process %d generated an access violation. SQL Server is terminating this process.
Error: 17310, Severity: 20, A user request from the session with SPID %d generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.