November 30, 2015 at 1:09 pm
Hi,
I have a client running SQL Server Express 2008 R2 for a couple of years now. As of last Friday everything was great. Saturday morning they could not connect to the database. I checked and the service was not running and the error reported in the Event viewer was this:
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.
If I change the user for the service to log on as to Local System, then the service starts, but this is not recommended and also the remote PCs are still unable to connect to the database whereas they were able to before.
I am telling the client it looks like some security rights was changed but they say they are unaware of any changes. Is there any other possibility or any solution to get them back running?
December 1, 2015 at 12:07 pm
Hmm, nobody ever seen this before or have I not given enough detail?
December 3, 2015 at 1:10 am
Do you possibly have more detail from the error log?
December 3, 2015 at 5:48 am
I'll try to connect to the client today and pull the event log.
December 4, 2015 at 4:58 am
This was the errorlog they sent me:
2015-11-28 11:44:33.23 Server Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (Intel X86)
Jun 28 2012 08:42:37
Copyright (c) Microsoft Corporation
Express Edition on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (WOW64)
2015-11-28 11:44:33.23 Server (c) Microsoft Corporation.
2015-11-28 11:44:33.23 Server All rights reserved.
2015-11-28 11:44:33.23 Server Server process ID is 5616.
2015-11-28 11:44:33.23 Server System Manufacturer: 'Dell Inc.', System Model: 'OptiPlex 9010'.
2015-11-28 11:44:33.23 Server Authentication mode is MIXED.
2015-11-28 11:44:33.23 Server Logging SQL Server messages in file 'c:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS2008R2\MSSQL\Log\ERRORLOG'.
2015-11-28 11:44:33.24 Server This instance of SQL Server last reported using a process ID of 2788 at 15/11/2015 10:01:17 AM (local) 15/11/2015 02:01:17 PM (UTC). This is an informational message only; no user action is required.
2015-11-28 11:44:33.24 Server Error: 17053, Severity: 16, State: 1.
2015-11-28 11:44:33.24 Server UpdateUptimeRegKey: Operating system error 5(failed to retrieve text for this error. Reason: 15100) encountered.
2015-11-28 11:44:33.24 Server Registry startup parameters:
-d c:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS2008R2\MSSQL\DATA\master.mdf
-e c:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS2008R2\MSSQL\Log\ERRORLOG
-l c:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS2008R2\MSSQL\DATA\mastlog.ldf
2015-11-28 11:44:33.25 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-11-28 11:44:33.25 Server Detected 4 CPUs. This is an informational message; no user action is required.
2015-11-28 11:44:33.32 Server 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.
2015-11-28 11:44:33.34 Server Node configuration: node 0: CPU mask: 0x0000000f:0 Active CPU mask: 0x0000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-11-28 11:44:33.36 spid7s Starting up database 'master'.
2015-11-28 11:44:33.46 spid7s SQL Trace ID 1 was started by login "sa".
2015-11-28 11:44:33.46 spid7s Starting up database 'mssqlsystemresource'.
2015-11-28 11:44:33.48 spid7s The resource database build version is 10.50.4000. This is an informational message only. No user action is required.
2015-11-28 11:44:33.57 spid7s Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key.
2015-11-28 11:44:33.57 spid10s Starting up database 'model'.
2015-11-28 11:44:33.57 spid7s Server name is 'XXXXXXXX\SQLEXPRESS2008R2'. This is an informational message only. No user action is required.
2015-11-28 11:44:33.58 Server Error: 17182, Severity: 16, State: 1.
2015-11-28 11:44:33.58 Server 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.
2015-11-28 11:44:33.58 spid7s Informational: No full-text supported languages found.
2015-11-28 11:44:33.58 Server Error: 17182, Severity: 16, State: 1.
2015-11-28 11:44:33.58 Server TDSSNIClient initialization failed with error 0x5, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Access is denied.
2015-11-28 11:44:33.58 Server Error: 17826, Severity: 18, State: 3.
2015-11-28 11:44:33.58 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.
2015-11-28 11:44:33.58 spid7s Starting up database 'msdb'.
2015-11-28 11:44:33.58 Server Error: 17120, Severity: 16, State: 1.
2015-11-28 11:44:33.58 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply