on - edited on by
Nils
This page explains what the "DCOM was unable to communicate with the computer" means for your installation, and how to prevent the error.
After installing Lansweeper and scanning your network, you may start seeing entries with an Event ID like the one below in your Lansweeper server's Event Viewer. While your Event Viewer classifies these entries as errors, they are just informational messages and can generally be ignored.
When Lansweeper scans a Windows computer, it uses DCOM to establish the initial connection to the client machine. If the client machine is offline or firewalled, DCOM automatically logs an error in your server's Event Viewer. This error indicates that Lansweeper was unable to scan the client machine, but does not point to an underlying issue with your server or Lansweeper installation.
Regardless, there are steps you can take to stop seeing these events. Lansweeper automatically excludes them from scanning so they don't show up in your Lansweeper web console, but you can also prevent them from being added to your Event Viewer altogether.
Prevent DCOM from logging events in Event Viewer
- On the machine hosting the Lansweeper Server service, run regedit.exe, the Registry Editor.
- Go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Oleand Modify the ActivationFailureLoggingLevel. - Set the ActivationFailureLoggingLevel value to "2".
- If the ActivationFailureLoggingLevel value does not exist, manually create it.
Keep in mind that setting this value to "2" will prevent DCOM from logging any failures. - Reboot the machine hosting the Lansweeper Server service.
Was this post helpful? Select Yes or No below!
Did you have a similar issue and a different solution? Or did you not find the information you needed? Create a post in our Community Forum for your fellow IT Heroes!
More questions? Browse our Quick Tech Solutions.
