SQL server cannot generate fruncm thread

Time:2022-5-6

SQL Server was unable to generate the fruncm thread. The database error log is as follows:

Copy codeThe code is as follows:
2013-09-26 21:21:50.31 Server      Microsoft SQL Server 2005 – 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

2013-09-26 21:21:50.31 Server      (c) 2005 Microsoft Corporation.
2013-09-26 21:21:50.31 Server      All rights reserved.
2013-09-26 21:21:50.31 Server      Server process ID is 2680.
2013-09-26 21:21:50.31 Server      Logging SQL Server messages in file ‘C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG’.
2013-09-26 21:21:50.31 Server      This instance of SQL Server last reported using a process ID of 2884 at 2013-9-26 21:20:51 (local) 2013-9-26 13:20:51 (UTC). This is an informational message only; no user action is required.
2013-09-26 21:21:50.31 Server      Registry startup parameters:
2013-09-26 21:21:50.31 Server           -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2013-09-26 21:21:50.31 Server           -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2013-09-26 21:21:50.31 Server           -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2013-09-26 21:21:50.32 SQL server is starting at normal priority base (= 7) This is an informational message only. No user action is required.
2013-cp21.09-detected 2:50 This is an informational message; no user action is required.
2013-09-26 21:21:50.37 set awe enabled to 1 in the configuration parameters to allow use of more memory
2013-09-26 21:21:50.49 using dynamic lock allocation   Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.   This is an informational message only.   No user action is required.
2013-09-26 21:21:50.53 server attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC) This is an informational message only. No user action is required.
2013-09-26 21:21:52.54 server attempting to recover in double distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) This is an informational message only. No user action is required.
2013-09-26 21:21:52.54 database mirroring transport is disabled in the endpoint configuration
2013-09-26 21:21:52.54 spid5s      Starting up database ‘master’.
2013-09-26 21:21:52.68 spid5s      Starting up database ‘mssqlsystemresource’.
2013-09-26 21:21:52.81 spid5s      Server name is ‘SHGS1653’. This is an informational message only. No user action is required.
2013-09-26 21:21:52.82 spid8s      Starting up database ‘model’.
2013-09-26 21:21:52.93 spid8s      Clearing tempdb database.
2013-09-26 21:21:53.10 server a self generated certificate was successfully loaded for encryption
2013-09-26 21:21:53.10 server error: 17182, severity: 16, status: 1.
2013-09-26 21:21:53.10 tdssniclient initialization failed with error 0x7e, status code 0x60
2013-09-26 21:21:53.10 server error: 17182, severity: 16, status: 1.
2013-09-26 21:21:53.10 tdssniclient initialization failed with error 0x7e, status code 0x1
2013-09-26 21:21:53.10 server error: 17826, severity: 18, status: 3.
2013-09-26 21:21:53.10 server 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.
2013-09-26 21:21:53.10 server error: 17120, severity: 16, status: 1.
2013-09-26 21:21:53.10 SQL server could not spawn fruncm thread Check the SQL Server error log and the Windows event logs for information about possible related problems.

terms of settlement:

It is analyzed that some special changes lead to the activation of via protocol in SQL Server 2005 database network protocol. It can be said that the protocol can be closed.
SQL Server Configuration Manager —— SQL Server 2005 network configuration —— MSSqlServer protocol. Just disable via protocol.

SQL server cannot generate fruncm thread

Recommended Today

JSP vulnerability overview

Summary: server vulnerabilities are the origin of security problems. Hackers’ attacks on websites mostly start from finding each other’s vulnerabilities. Therefore, only by understanding their own vulnerabilities, website managers can take corresponding countermeasures to prevent foreign attacks. The following describes the common vulnerabilities of some servers (including web server and JSP server). What’s the matter […]