When fiddling around using the SQL Server Configuration Tool yesterday, I changed the 'log on as' user to my domain user for all SQL Server services. This in turn stopped the service and when I try to start the service I get an error like 'Failed to respond in a timely fashion'. If I try resetting the 'log on as' users to Network Service and Local Service, I get an error saying 'Cannot find object or property'.
How can I reset these users and restart the SQL Server?
Answer by Matt Whitfield ·
Just a thought, have you tried changing the Log On As property through services control panel, rather than using the configuration manager?
an alternative step, which sometimes helps:
Answer by S Graham ·
thanks for your responses. Just to fill you in a few more details.....
It was definitely not a fresh install and prior to my tinkering had been working for a good few months. I'm sure the machine had been rebooted several times after the SQL Server installation.
Its a Windows 2003 Standard Edition server. Looking at the error logs, I get the following reports....
Application Event Log
Event Type: Error Event Source: MSSQL$SQL2008 Event Category: Server Event ID: 17120 Date: 16/11/2009 Time: 09:00:57 User: N/A Computer: SKIP Description: SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
System Event Log
Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7024 Date: 16/11/2009 Time: 09:00:57 User: N/A Computer: SKIP Description: The SQL Server (SQL2008) service terminated with service-specific error 2148081668 (0x80092004).
I've tried rebooting again, and also tried logging out and back in as my user, but this hasn't helped. I still cannot change the 'log on as' property of either SQL Server or SQL Server Agent using the configuration manager.
WMI Provider Error: Cannot find object or property (0x80092004)
Any help would be much appreciated.
Answer by Blackhawk-17 ·
Was this a fresh install and had you rebooted prior to changing the users?
It is possible some DLLs wre not registered yet and that may be an underlying issue.
I would begin with a reboot to see if A) any delayed file actions completed, B) to clear the memory and C) it is Microsoft fix #1 :)
If the reboot does not alleviate the issue you may need to try a repair.
Are there any other issues showing up in the NT Event logs around the same time?
What O/S was the install on? Is this on a laptop/desktop/virtual machine/server/cluster?