Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Friday, January 24, 2014 4:36 AM
I made a change to Protocols for SQLEXPRESS, TCP/IP, IP Addresses, IPALL and now receive an error when attempting to restart SQL Server. Can anyone help with this? Is it possible to restore system to prior checkpoint in order to correct this?
Please help.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0xd, status code 0x10. Reason: Unable to retrieve registry settings from TCP/IP protocol's 'IPAll' configuration key. The data is invalid.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0xd, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The data is invalid.
Error: 17826, Severity: 18, State: 3.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
Error: 17120, Severity: 16, State: 1.
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Monday, January 27, 2014 7:44 AM ✅Answered | 2 votes
Hi Chuck,
The Error "TDSSNIClient initialization failed with error 0xd, status code 0x10. Reason: Unable to retrieve registry settings from TCP/IP protocol's 'IPAll' configuration key. The data is invalid" Suggest that there is a problem with the data stored in one of the registry keys related to SQL server start up. Although the information provided is not sufficient to pinpoint to a specific issues. Still try the following step open the SQL server configuration manager
Select SQL server Network Configuration->Protocols for <Your SQLExpress instance Name>
On the right side double click TCP/IP.Select IPAddresses Tab. Scroll the way down till you file IPALL
Make sure that there are only a valid TCP/IP Port number is present. Even the leading or trailing whitespaces could make a difference here. Once you have verified that above two conditions are met. Try starting the SQL server instance.
Also make sure that the TCP/IP port is not being used by any other program.
You can run the command netstat -aon on the command prompt to see the list of ports being used. Make sure that the port you have specified for SQL server is not listed under the TCP protocols.
Hope this helps.
Regards
Sathish S N
Please click the Mark as answer button and vote as helpful if this reply solves your problem
Monday, January 27, 2014 3:08 AM | 2 votes
Check if the VIA protocol is enabled disable it and then try starting the SQL Server service again.
Check the similar threads
Please click the Mark as answer button and vote as helpful if this reply solves your problem
Tuesday, January 28, 2014 2:29 AM
Thanks for the response. This information was helpful in researching the problem. I restored my system to a prior checkpoint and it corrected the issue with SQL start.
Monday, March 4, 2019 12:00 PM
yes true, IPAll should empty.