October 6, 2022 at 12:49 pm
Hi,
We have a VM running SQL. This VM crashed and since coming back up we cannot connect to the SQL instance running on it from outside of the VM itself. SSMS works fine when connecting to the local instance.
Also, the SQL Server service will now only start if the domain account used is in the local admin group - this has never been required.
Checking the SQL CLUSTER.LOG logs, we're getting the following errors:
2022-09-29 12:10:43.38 Server Error: 8319, Severity: 16, State: 1.
2022-09-29 12:10:43.38 Server The operating system kernel object 'Global\SQL_ 150 _MEMOBJ_ 32 _<SQLINSTANCENAME>_0' already exists. It's not owned by the SQL Server service account. SQL Server performance counters are disabled.
2022-09-29 12:10:43.38 Server Error: 3409, Severity: 16, State: 1.
2022-09-29 12:10:43.38 Server Performance counter shared memory setup failed with error -1. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions.
2022-09-29 12:10:45.75 spid9s Server name is '<SERVERNAME>\<INSTANCENAME>'. This is an informational message only. No user action is required.
2022-09-29 12:10:45.76 spid23s Error: 17182, Severity: 16, State: 1.
2022-09-29 12:10:45.76 spid23s TDSSNIClient initialization failed with error 0x5, status code 0x51. Reason: Unable to configure MDAC-compatibility Named Pipes protocol pipe name in registry. Access is denied.
2022-09-29 12:10:45.76 spid23s Error: 17182, Severity: 16, State: 1.
2022-09-29 12:10:45.76 spid23s TDSSNIClient initialization failed with error 0x5, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Access is denied.
2022-09-29 12:10:45.76 spid23s Error: 17826, Severity: 18, State: 3.
2022-09-29 12:10:45.76 spid23s 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.
2022-09-29 12:10:45.76 spid23s Error: 17120, Severity: 16, State: 1.
2022-09-29 12:10:45.76 spid23s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.
Never come across these before! Any pointers?
Thanks
October 6, 2022 at 12:58 pm
Have you looked for disc corruption? It honestly looks like things are messed up at a low level.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 6, 2022 at 2:40 pm
yeah the OS disk needed a chkdsk (I split out SQL data files as per best practice).
October 6, 2022 at 2:41 pm
also the OS is generally not great - none of the application shortcut icons from start menu show properly. Considering cutting my losses with this VM!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply