B
Br1ckman
I am running a Server 2012 deployment at one of my clients with networked printers loaded onto the server. I recently had an issue where one of my users was unable to print from a specific printer. When I then proceeded to check on the server side through Remote Desktop I was unable to remote into the server. Unfortunately during the time I did not record the error because I was able to physically gain access to the machine with no problem. However I had to restart the server because of the services that the server provided.
Now after the reboot and during some down time I went through the event viewer and these two DCOM errors kept repeating themselves for a long time within a 24 hour period. Please see below for the DCOM errors.
Log Name: System
Source: DistributedCOM
Event ID: 10010
Level: Error
User: System
The server {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} did not register with DCOM within the required timeout.
Log Name: System
Source: DistributedCOM
Event ID: 10010
Level: Error
User: System
The server {A677570A-2BA2-4E9A-B2E2-8A02CD8B4FD3} did not register with DCOM within the required timeout.
Now I checked in my registry with the SID's in the brackets to try to narrow it down.
The 73 had the following parameters:
%systemroot%\sysWOW64\wbem\wmiprvse.exe
The A6 had the following parameters
%SystemRoot%\system32\PrintIsolationHost.exe
PrintSys.CoPrintIsolationHost.1
Now I am not sure exactly what caused the issue. My theories are either a possible print driver or something that was not fixed in Server 2012. After hours I ended up updating that Server 2012 with latest windows updates thinking maybe Microsoft had release some type of fix. However I am not super confident to make this server my backbone because of this issue with the printer locking up and not being able to remote desktop into the server until after a reboot. If someone has seen this specific issue with the above mentioned DCOM errors any help is appreciated. I have looked at many technet articles and other postings, but nothing seems to point to this error.
Continue reading...
Now after the reboot and during some down time I went through the event viewer and these two DCOM errors kept repeating themselves for a long time within a 24 hour period. Please see below for the DCOM errors.
Log Name: System
Source: DistributedCOM
Event ID: 10010
Level: Error
User: System
The server {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} did not register with DCOM within the required timeout.
Log Name: System
Source: DistributedCOM
Event ID: 10010
Level: Error
User: System
The server {A677570A-2BA2-4E9A-B2E2-8A02CD8B4FD3} did not register with DCOM within the required timeout.
Now I checked in my registry with the SID's in the brackets to try to narrow it down.
The 73 had the following parameters:
%systemroot%\sysWOW64\wbem\wmiprvse.exe
The A6 had the following parameters
%SystemRoot%\system32\PrintIsolationHost.exe
PrintSys.CoPrintIsolationHost.1
Now I am not sure exactly what caused the issue. My theories are either a possible print driver or something that was not fixed in Server 2012. After hours I ended up updating that Server 2012 with latest windows updates thinking maybe Microsoft had release some type of fix. However I am not super confident to make this server my backbone because of this issue with the printer locking up and not being able to remote desktop into the server until after a reboot. If someone has seen this specific issue with the above mentioned DCOM errors any help is appreciated. I have looked at many technet articles and other postings, but nothing seems to point to this error.
Continue reading...