Remote Desktop Service start failed. The relevant status code was 0x800706b ...
-
Friday, July 13, 2012 1:15 PM
Hi,
We reboot our RDSH servers every morning. We have been getting get alerts from the Microsoft-Windows-TerminalServices-LocalSessionManager log (event id 17 level 1) when the servers are rebooted, it doesn't every time and when it does occur it doesn’t appear to reduce functionality.
I’ve just done a quick poll across 5 RDSH servers and found errors going back as far as 26/07/2011 …..
68 x “Remote Desktop Service start failed. The relevant status code was 0x800706b5.”
48 x “Remote Desktop Service start failed. The relevant status code was 0x800706be.”
5 x “Remote Desktop Service start failed. The relevant status code was 0x800706ba.”
I’ve also noticed that these errors seem to have been occurring consistently across 2 or more servers since 15/06/2012 which is also when a number of Windows Updates were installed but that might be a red herring.
I’ve seen some posts talking about having a Firewall rule for Remote DesktopFX, I’ve added that to the firewall but still get the errors.
Anyone had any experiences with this?
Thanks,
John
All Replies
-
Monday, July 16, 2012 9:25 AMModerator
Hi,
Have you installed KB 2667402? There is a known issue on KB 2667402 release on March 13. For more detailed information, please check the following article.
http://support.microsoft.com/kb/2667402
For the warning message Event ID 17, please refer to the following article.
Event ID 17 — Remote Desktop Services Availability
http://technet.microsoft.com/en-us/library/ee891136(v=ws.10).aspx
This event ID generate when Windows failed to start Remote Desktop services. Only when the RDS server reboot, all services to restart. So the log may shows up. Beside the error message, please let me know if the services always fail to start after RDS server reboot? Did we need to manually start it? Is this cause any Remote connection issue for client to the RDS server? Just curious, why you need to reboot the RDS server so frequently?
Best Regards,
Aiden
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Aiden Cao
TechNet Community Support
-
Thursday, July 19, 2012 1:07 AMModerator
Hi,
How are things going? I just want to check the status of the issue. If you have any update or concern, please feel free to let us know.
Aiden
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Aiden Cao
TechNet Community Support
-
Thursday, July 19, 2012 9:56 AM
Hi,
Sorry for the delay in getting back to you. I've just checked across all the servers and we do have KB2667402 installed.
Since my day's with Citrix on Server 2000 and up to 2008R2 it's always been consider good practice to bounce your server daily. We've moved away from Citrix but continue with the "best practice" for a nightly reboot to clear the system.
J
-
Monday, July 23, 2012 2:42 AMModerator
Hi,
Generally, the Event ID 17 indicates that the Remote Desktop services is failed to start. This provided useful information to troubleshoot when we cannot to RDP to the RDS server. So when the log generated, dose the client cannot to RDP to the session host server? Is this cause any problem in your RDS environment? I understand that you reboot the server daily for improve the performance, but I think the Remote Desktop services may fail to start when the server initializing. However, after all based services were started. The automatic to start remote desktop services attempt is working, so no functional issue appears. If this is the case, you can safely ignore this warning message.
Best Regards,
Aiden
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Aiden Cao
TechNet Community Support
- Marked As Answer by Aiden_CaoMicrosoft Contingent Staff, Moderator Friday, July 27, 2012 8:09 AM
-
Wednesday, July 25, 2012 7:54 AMModerator
Hi,
How are things going? I just want to check if the information provided was helpful. If there is any update or concern, please feel free to let us know.
Best Regards,
Aiden
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Aiden Cao
TechNet Community Support
- Edited by Aiden_CaoMicrosoft Contingent Staff, Moderator Wednesday, July 25, 2012 7:55 AM
-
Wednesday, July 25, 2012 8:02 AM
Hi,
Yes, I and had already assumed that the service is erroring due to the server reboot up but then successfully starts and services rdp requests. I was hoping there would be a fix to the error rather than knowing it can safety be ignored. I monitor our environment with SCOM 2012 and have to clear the alerts daily. I appreciate that I can disable the monitor but I’m concerned if we disable this monitor we wouldn’t be alerted to other issues. Is it possible to create and override to this monitor so it checks if the service is running/accepting RDP requests?
Thanks,
John
-
Wednesday, July 25, 2012 8:50 AMModerator
Hi,
Thanks for your update.
I hope I can share my knowledge on this. However, I am not an expert on SCOM. So I cannot give effective suggestion on this. Best resource for you, I would recommend that you post this specific issue at SCOM forum. Hope other experts familiar with this topic can give more useful suggestion. Your understanding is highly appreciated.
System Center – Operations Manager Forum
http://social.technet.microsoft.com/Forums/en-US/category/systemcenteroperationsmanager
Best Regards,
Aiden
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Aiden Cao
TechNet Community Support
.png)
