Discovery_MFXP fails to discover Metaframe objects with errors and does not generate an event (NETIQKB44460)

  • 7744460
  • 02-Feb-2007
  • 10-Jan-2011

Environment

NetIQ AppManager 6.x
NetIQ AppManager 7.0.x
Discovery_MFXP Knowledge Script

Situation

Discovery_MFXP fails to discover Metaframe objects with multiple errors and does not generate an event message.

MFXP Discovery encountered errors, causing it to fail. The errors were: 'Failed to create MetaFrameCOM.MetaFrameFarm object.'

'Error: 2 Description: Metaframe License Server is not installed on this computer.'

'Error: 46 Description: Permission denied Extended Information:'

Resolution

To enable the DCOM Access Security for the service account of the NetIQmc service, follow these steps to verify and/or specify access for the Log On account or the account specified for the NetIQmc service on the Management Server if using any of the AMADMIN_AgentUpdate Knowledge Scripts.

For Windows 2003:

  1. Verify the Log On account has access to the registry of the target machine.
  2. Verify the Log On account has Full Administration rights to the Citrix MetaFrame objects.
  3. Verify and\or explicitly add permissions for the AppManager service account to the DCOM objects (DCOM Security) in the following locations:

    Start | Programs | Administrative Tools | Component Services | My Computer | Properties | Default DCOM Security | Access Security

    and

    Start | Programs | Administrative Tools | Component Services | My Computer | Properties | Default DCOM Security | Launch Permissions
  4. Restart the NetIQmc service on the MetaFrame server.
  5. Drop a new Discovery_MFXP job.

For Windows 2000:

  1. Verify the Log On account has access to the registry of the target machine.
  2. Verify the Log On account has Full Administration rights to the Citrix MetaFrame objects.
  3. Verify and\or explicitly add permissions for the AppManager service account to the DCOM objects (DCOM Security) in the following locations:

    Start | Run | DCOMCNFG | Default Security | Default Access Permissions | Edit Default

    and

    Start | Run | DCOMCNFG | Default Security | Default Launch Permissions | Edit Default

    and

    Start | Run | DCOMCNFG | Default Security | Default Configuration Permissions | Edit Default
  4. Restart the NetIQmc service on the MetaFrame server.
  5. Drop a new Discovery_MFXP job.

For more information, contact Technical Support at www.netiq.com/support.

Cause

DCOM Object Security is not set for the NetIQmc (NetIQ Client Resource Monitor) service account.

Additional Information

Formerly known as NETIQKB44460