Quantcast
Viewing all articles
Browse latest Browse all 8539

SBS 2008 Dead Screen and Dead Remote Desktop

Hi,

Our SBS 2008 R2 SP2 server has a problem previously described, but there doesn't seem to be any answers. 
Once booted we can interact with the screen, but overnight or after an extended period of time the screen freezes up. First thought, screen card problem.

But then you try remote desktop which works the first time, then the next time you try it it gets stuck on the welcome screen and goes no further. 

Errors we see happening around the time when the remote desktop fails are as follows: 
4 x ID 10009 Source DCOM Type Error... Exceptions with the following message: "DCOM was unable to communicate with the computer MachineName.st1.local using any of the configured protocols"
1 x ID 56 Source TermDD Type Error... The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.

After a reboot we get these errors:

1. "ID-10154, Source-WinRM, Type-Warning, Message-The WinRM service failed to create the following SPNs: WSMAN/YODA.starwars.local; WSMAN/Server1.
 Additional Data
 The error received was 8344: Insufficient access rights to perform the operation.
 User Action
 The SPNs can be created by an administrator using setspn.exe utility.
2. "ID-7026, Source-Service Control Manager, Type-Error, Message-The following boot-start or system-start driver(s) failed to load: storflt" (Apparently this can be safely ignored)
3. "ID-10149, Source-WinRM, Type-Warning, Message-The WinRM service is not listening for WS-Management requests.
 User Action
 If you did not intentionally stop the service, use the following command to see the WinRM configuration:
 winrm enumerate winrm/config/listener
4. "ID-7034, Source-Service Control Manager, Type-Error, Message-The Windows Process Activation Service service terminated unexpectedly.  It has done this 1 time(s).

There are a few more but they seem to follow the same pattern.

Main thing is ther server is actually up and running, but we can't access it via either the screen itself or remote desktop.

Was a proper solution for this ever found?

Thanks,
Jacques


Viewing all articles
Browse latest Browse all 8539

Trending Articles