About SQL Server cannot generate FRUNCM thread (incomplete)

Tag: Code user run reload Word Eve Protocol computer request

The day before 51, ready to start the database complete my remaining project code, the database Configuration Manager has a problem with the pain of the egg
Sqlserv Configuration Manager requests failed or the server is not responding in a timely manner
On this issue of the treatment method, after my two-hour Baidu, online on the problem of the solution there are two ways,
One, disable the VIA protocol in the MSSQLSERVER protocol in the SQL Server network configuration
Second, close the TCP/IP protocol
However, two hours, countless posts of the quest told me a fact that these things can not solve my current problems
In the computer right-click Event Viewer to find the application, SQL verbose error log, although online can be found
Probably, but still useless to the problem I'm currently meeting.

The details of the error are as follows:

error log one: {

Journal name: Application
Source: MSSQLSERVER
Date: 2017/4/30 10:56:58
Event id:17120
Task Category: Server
Level: Error
Keywords: classic
User: N/A
Computer: DESKTOP-LA0ONVD
Description:
SQL Server could not generate the FRUNCM thread. Review the SQL Server error log and the Windows event log for information about possible issues that may occur.
Event Xml:
<event xmlns= "Http://schemas.microsoft.com/win/2004/08/events/event" >
<System>
<provider name= "MSSQLSERVER"/>
<eventid qualifiers= "49152" >17120</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<timecreated systemtime= "2017-04-30t02:56:58.568064600z"/>
<EventRecordID>12134</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-LA0ONVD</Computer>
<security/>
</System>
<EventData>
<Data>FRunCM</Data>
<binary>e042000010000000100000004400450053004b0054004f0050002d004c00410030004f004e0056004400000000000000 </Binary>
</EventData>
</Event>
}

error log two:{
Journal name: Application
Source: MSSQLSERVER
Date: 2017/4/30 10:56:58
Event id:17826
Task Category: Server
Level: Error
Keywords: classic
User: N/A
Computer: DESKTOP-LA0ONVD
Description:
The network library could not be started because there was an internal error in the network library. To determine the cause, check the error log for those errors that precede this error.
Event Xml:
<event xmlns= "Http://schemas.microsoft.com/win/2004/08/events/event" >
<System>
<provider name= "MSSQLSERVER"/>
<eventid qualifiers= "49152" >17826</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<timecreated systemtime= "2017-04-30t02:56:58.568064600z"/>
<EventRecordID>12133</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-LA0ONVD</Computer>
<security/>
</System>
<EventData>
<binary>a245000012000000100000004400450053004b0054004f0050002d004c00410030004f004e0056004400000000000000 </Binary>
</EventData>
</Event>
}

error log three: {
Log name: Application
Source: MSSQLSERVER
Date: 2017/4/30 10:56:58
Event id:17182
Task Category: Server
Level: Error
Keyword: classic
User: N/a
computer: DESKTOP-LA0ONVD
Description:
tdssniclient initialization failed with error 0x5, status code 0x1. Cause: The initialization failed with an infrastructure error. Please check for previous errors. Access denied.

Event Xml:
<event xmlns= "Http://schemas.microsoft.com/win/2004/08/events/event" >
<System>
<provider name= "MSSQLSERVER"/>
<eventid qualifiers= "49152" >17182</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<timecreated systemtime= "2017-04-30t02:56:58.568064600z"/>
<EventRecordID>12132</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-LA0ONVD</Computer>
<security/>
</System>
<EventData>
<Data>5</Data>
<Data>1</Data>
<Data> failed to initialize, infrastructure error occurred. Please check for previous errors. </Data>
<Data> denied access.
</Data>
<binary>1e43000010000000100000004400450053004b0054004f0050002d004c00410030004f004e0056004400000000000000 </Binary>
</EventData>
</Event>

}

error log four : {
Log name: Application
Source: MSSQLSERVER
Date: 2017/4/30 10:56:58
Event id:17182
Task Category: Server
Level: Error
Keyword: classic
User: N/a
computer: DESKTOP-LA0ONVD
Description:
tdssniclient initialization failed with error 0x5, status code 0x51. Cause: The MDAC-compliant Named Pipes protocol pipeline name cannot be configured in the registry. Access denied.

Event Xml:
<event xmlns= "http://schemas.microsoft.com/win/2004/08/events/event";
<system>
<provider name= "MSSQLSERVER"/>
<eventid qualifiers= "49152" >17182</EVENTID>
<Level> 2</level>
<task>2</task>
<keywords>0x80000000000000</keywords>
< timecreated systemtime= "2017-04-30t02:56:58.552507600z"/>
<eventrecordid>12131</eventrecordid
<channel>application</channel>
<computer>desktop-la0onvd</computer>
< Security/>
</system>
<eventdata>
<data>5</data>
<data>51</data
<Data> cannot configure MDAC-compliant Named Pipes protocol pipeline names in the registry. </data>
<Data> deny access.
</data>
<Binary> 1e43000010000000100000004400450053004b0054004f0050002d004c00410030004f004e0056004400000000000000</binary
</eventdata>
</event>
}

Final Solution: Reload the database

About SQL Server cannot generate FRUNCM thread (incomplete)