SQL Server Errors or Failures from Error: 17105 to Error: 17127

SQLServerF1

 

Error: 17105, Severity: 10, Could not open master database in system task thread context. Terminating server.
Error: 17106, Severity: 10, Common Criteria compliance mode is enabled. This is an informational message only; no user action is required.
Error: 17107, Severity: 10, Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
Error: 17108, Severity: 10, Password policy update was successful.

Error: 17109, Severity: 10, FallBack certificate was successfully created.
Error: 17110, Severity: 10, Registry startup parameters: %.*ls
Error: 17111, Severity: 10, Logging SQL Server messages in file ‘%s’.
Error: 17112, Severity: 16, An invalid startup option ‘%s’ was supplied, either from the registry or the command prompt. Correct or remove the option.
Error: 17113, Severity: 16, Error %ls occurred while opening file ‘%ls’ to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.

Error: 17114, Severity: 16, Error %ls occurred while opening file ‘%ls’ to obtain configuration information at startup time. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
Error: 17115, Severity: 10, Command Line Startup Parameters:%.*ls
Error: 17116, Severity: 16, Failed to initialize distributed COM; DCOM is not installed. Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel.
Error: 17119, Severity: 10, The number of concurrent user connections was reduced to %ld, because it exceeded the allowable limit for this edition of SQL Server. To avoid this message in the future, use sp_configure to permanently adjust the number of user connections within the lic
Error: 17120, Severity: 16, SQL Server could not spawn %s thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Error: 17121, Severity: 10, SQL Server is started with trace flag %d, this may cause user to see some error messages masked using ‘%ls’.
Error: 17123, Severity: 10, Logging to event log is disabled. Startup option ‘-%c’ is supplied, either from the registry or the command prompt.
Error: 17124, Severity: 10, SQL Server has been configured for lightweight pooling. This is an informational message; no user action is required.
Error: 17125, Severity: 10, Using dynamic lock allocation. Initial allocation of %I64u Lock blocks and %I64u Lock Owner blocks per node. This is an informational message only. No user action is required.
Error: 17126, Severity: 10, SQL Server is now ready for client connections. This is an informational message; no user action is required.
Error: 17127, Severity: 16, initdata: No memory for kernel buffer hash table.

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.

 

Leave a Reply

Your email address will not be published. Required fields are marked *