DCOM error 10010 – finding the culprit
While cleaning up logs reports in check_mk – I came across a dcom error and thought it would be useful to document how to track down which supplier / app might be the cause of it. Specifically the message I was tracking down was DCOM The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM within the […]