Error: 'Access denied attempting to launch a DCOM Server.' (NETIQKB31963)

fact
VigilEnt Security Manager 4.0

fact
VigilEnt Security Manager 4.1

symptom
Error: 'Access denied attempting to launch a DCOM Server.'

symptom
Error appears in the Event log when trying to log into VigilEnt Security Manager.

symptom
A DCOM error shows in the event log.

cause
The error indicates that the VigilEntService user does not have access or launch permissions for Machine Debug Manager.

fix

Complete the following steps to resolve this problem:

1. At a command prompt, type the following command to open Distributed COM Configuration Properties:

   dcomcnfg.exe

2. On the Applications tab, in the list of DCOM servers, browse to the Machine Debug Manager entry. If this entry does not exist, close the program and type the following command at a command prompt to add the entry:

   mdm.exe /regserver

3. Re-open Distributed COM Configuration Properties, browse to the Machine Debug Manager, and click Properties.

4. On the Security tab, click Use Custom Access Permissions, and click Edit.

5. Add the VigilEntService user to the existing access permissions for Machine Debug Manager.

6. Click OK twice to return to the Security tab.

7. On the Security tab, click Use Custom Launch Permissions, and click Edit.

8. Add the VigilEntService user to the existing launch permissions for Machine Debug Manager.

9. Click OK twice to return to the Security tab.

10. On the Identity tab, click the Interactive User to set the user account identity of Machine Debug Manager. If no one will be logged on to the computer, click this user, and type the user name and password of a user in the Administrators group.

11. Close all instances of Mdm.exe, or restart the computer, so that these changes take effect.

Formerly known as NETIQKB31963