Application popup: netiqmc.exe - Application Error : The instruction at 0x00000000 (NETIQKB13)

Application popup: netiqmc.exe - Application Error : The instruction at 0x00000000 referenced memory at 0x00000000 . The memory could not be read .
Error: 'Process Terminated Unexpectedly'
NetIQ AppManager Client Resource Monitor service fails to start with 1067 error.
NetIQ AppManager Client Resource Monitor service does not start, fails with Dr. Watson error.

For Microsoft Windows NT or Microsoft Windows 2000 Servers:

To use the Distributed COM Configuration Properties utility to configure DCOM permissions:

1. Go to Start | Run.
2. In the Open  field Type dcomcnfg.
3. In the Distributed COM Configuration Properties window, select the Default Security tab.
4. Under Default Access Permissions, click Edit Default.
5. In the Registry Value Permissions window, click Add.
6. In the Add Users And Groups window, click Show Users.
7. Select the appropriate User.
8. In the Type Of Access drop-down list, select Allow Access .
9. Click OK. (The User should now appear in the Registry Value Permissions window.)
10. Click OK again.
11. Under Default Launch Permissions, click Edit Default.
12. In the Registry Value Permissions window, click Add.
13. In the Add Users And Groups window, click Show Users.
14. Select the appropriate User.
15. In the Type Of Access drop-down list select Launch Permission.
16. Click OK. (The User should now appear in the Registry Value Permissions window.)
17. Click OK again.
18. Repeat Steps 4 through 17 for both the System and Interactive accounts on the Local Server.

For Microsoft Windows 2003 Servers:

To use the Distributed COM Configuration Properties utility to configure DCOM permissions:

1. Go to Start | Run.
2. In the Open  field Type dcomcnfg.
3. Expand Component Services.
4. Expand Computers.
5. Right click My Computer and select Properties.
6. In the My Computer Properties window, select the Default COM Security tab.
7. Under Access Permissions, click Edit Default.
8. In the Groups and User Names  window, click Add.
9. Add the appropriate User and click Check User.
10. Click OK.
11. In the Permissions list, select Allow Access .
12. Click OK.
13. Under Launch Permissions, click Edit Default.
14. Repeat steps 8 through 10.
15. In the Permissions list, select Launch Permission.
16. Click OK.
17. Repeat Steps 5 through 16 for both the System and Interactive accounts on the Local Server.

The account being used to 'LogOn As' for the NetIQ AppManager Client Resource Monitor service does not have permission to access or launch DCOM objects on the target Server.

Formerly known as NETIQKB13

To view further documentation from Microsoft's web site about "Use dcomcnfg for a Visual Basic DCOM Client/Server Application (Q268550)" please access the link provided below:

Use dcomcnfg for a Visual Basic DCOM Client/Server Application (Q268550)http://support.microsoft.com/default.aspx?scid=kb;EN-US;q268550 

Note: If the service account that is used to setup and install the AppManager Agent and run the Agent Services is this account (setup account), then DCOM permissions need not apply.  If the service account and the setup account are different, then the stated workaround would apply.