An application-specific permission settings prevent COM Server application from running locally

KB ID:
1034
Product:
Veeam Smart Plug-in (SPI) for VMware
Version:
5.x
Published:
Last Modified:
2011-11-29

Challenge

The nworks discovery is not working and topology is not created.

Cause

This is a permission related issue. The account NT AUTHORITY\SYSTEM does not have permission to create a COM object.

Solution

Grant the correct permissions to the System account. To grant the correct permissions to the System account, follow these steps:

1. Click Start, click Run, type dcomcnfg in the Open box, and then click OK.
2. In Component Services, double-click Component Services, and then double-click Computers.
3. Right-click My Computer, and then click Properties.
4. Click the COM Security tab.
5.
In the Launch and Activation Permissions area, click Edit Default.
6. Click Add, type System, and then click OK.
7. W
hile System is selected, click to select the Allow check boxes for the following items:
  • Local Launch
  • Remote Launch
  • Local Activation
  • Remote Activation

8. Click OK two times.
9.
In the Access Permissions click Edit Default
10.
Choose account and grant permissions for local and remote access. (Allow)
11. R
estart computer.

Once resolved, this issue would lead to the following messages in OMW console:

"SVCDISC" message after which discovery will start working.

Rate the quality of this KB article: 
5 out of 5 based on 2 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text:

Submit