October 10, 2008 at 1:42 am
Dear All,
We are getting below errors in SQL Server error log and Windows Application Event log.
Error in SQL Server error log,
SQLServiceControlHandler: Could not set Service Control Status. Operating system error = 6(The handle is invalid.).
Errors in Application event log,
Event Type: Error
Event Source: ProtectedStorage
Event Category: None
Event ID: 0
Date: 10/10/2008
Time: 11:55:35 AM
User: N/A
Computer: TNMAXIMO
Description:
The description for Event ID ( 0 ) in Source ( ProtectedStorage ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: ProtectedStorage error: 6, SetServiceStatus.
Event Type: Error
Event Source: SENS
Event Category: None
Event ID: 0
Date: 10/10/2008
Time: 11:55:35 AM
User: N/A
Computer: TNMAXIMO
Description:
The description for Event ID ( 0 ) in Source ( SENS ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Event System Win32 Error: No service is operating at the destination network endpoint on the remote system.
, ServiceControl(): ReportStatusToSCM() failed when logging current state.
Event Type: Error
Event Source: DWMRCS
Event Category: None
Event ID: 110
Date: 10/10/2008
Time: 12:10:34 PM
User: N/A
Computer: TNMAXIMO
Description:
Error:
DameWare Mini Remote Control
System Error: 6
SetServiceStatus failed - State: 4 Handle: 1287368
Event Type: Error
Event Source: EventSystem
Event Category: (3)
Event ID: 4101
Date: 10/10/2008
Time: 12:10:34 PM
User: N/A
Computer: TNMAXIMO
Description:
The COM+ Event System detected an unexpected error from a Win32 API call at line 179 of .\service.cpp. A call to SetServiceStatus failed with error code 6: "The handle is invalid. " Please contact Microsoft Product Support Services to report this error.
Event Type: Error
Event Source: McLogEvent
Event Category: None
Event ID: 1006
Date: 10/10/2008
Time: 12:10:35 PM
User: N/A
Computer: TNMAXIMO
Description:
Task Manager : Service Error : SetServiceStatus
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 10/10/2008
Time: 12:10:35 PM
User: N/A
Computer: TNMAXIMO
Description:
17143 :
SQLServiceControlHandler: Could not set Service Control Status. Operating system error = 6(The handle is invalid.).
Data:
0000: f7 42 00 00 10 00 00 00 ÷B......
0008: 09 00 00 00 54 00 4e 00 ....T.N.
0010: 4d 00 41 00 58 00 49 00 M.A.X.I.
0018: 4d 00 4f 00 00 00 00 00 M.O.....
0020: 00 00 ..
Configuration details,
Windows NT 5.0 (Build 2195: Service Pack4)
SQL Server 2000 Enterprise Edition with SP4
Till now we there is no issue due these errors, but to be on a safer side please let us know the cause and solution for these errors.
Thanks in advance.
Regards,
Sajid C.
March 16, 2010 at 1:25 pm
Hi,
I am having the same issue with my sql server, but nobody has answered the topic, did you solve this problem?
May 5, 2010 at 12:54 pm
Same here -- SQL 2000 EE SP4, Windows 2003 EE SP2. Suggestions are most welcome.
May 5, 2010 at 1:15 pm
As per
http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/35736/6-SetServiceStatus
Generally speaking, the event 4101 should be related with third party
software or hardware. In order to solve such issue, we may need further get
more information for further trouble shooting.
1. Please also check your event log to see if there are any DCOM errors?
2. If possible, could you check if you have installed any third party
software on your SBS 2003? Please temporally stop it to see if the problem can be resolved or not?
3. Please also make a clean reboot of your SBS server to see if the event 4101 can be cleared? You can refer to my suggestion below to make a clean reboot:
A. Click Start->Run!-->type msconfig and press Enter
B. Click Services tab and select Hide All Microsoft Services and Disable All third party Services.
C. Click Startup tab and Disable All startup items
D. Click OK and choose Restart
E. After reboot, check whether the problem still occurs
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply