Discovery_Exchange Knowledge Script Generates 'EXCH Discovery Partially OK' and failure event as well. (NETIQKB2521)

  • 7702521
  • 02-Feb-2007
  • 26-Jul-2010

Environment

AppManager Suite 6.x
AppManager Suite 7.0.x

Situation

Discovery_Exchange Knowledge Script Generates Two Events: 'EXCH Discovery Partially OK' and 'MAPILogonEX Failed: ProfileName 80040111'
Error: MAPILogonEX failed: 80040111.

Resolution

WARNING: Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. NetIQ cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Make sure that you backup your Registry prior to making any changes.

Start the Registry Editor (Regedt32.exe or regedit.exe) on the Exchange Server.

Under the hive HKEY_LOCAL_MACHINE go the following subkey:

SOFTWARE\NETIQ\NetIQmc

Insert the correct information for each of the following values:

Exchange Mailbox:

Exchange Profile:

Exchange Server:

Restart the NetIQmc service on the target machine.

Close the registry editor, then drop a new Discovery_Exchange job on the Exchange Server. The discovery should now complete without errors.

Cause

The values in the NT Registry on the Exchange Server contain incorrect values for the Exchange Mailbox and Profile information.

The Discovery_Exchange knowledge script relies on NT Registry entries for Exchange Profile and Mailbox information, not the Security Manager entries, which are used by other knowledge scripts such as Action_MapiMail or Exchange_Connectivity.

Additional Information

Formerly known as NETIQKB2521

Discovery_Exchange job completes, and objects appear in the Tree View, but the following event is generated:
EXCH Discovery Partially OK
MAPILogonEX failed: <profilename> 80040111.


The value <profilename> is either a name or is blank. The correct profile name and mailbox have been entered into the AppManager Security Manager for the server being discovered. The Action_MapiMail knowledge script works properly when used as a managed client action in conjunction with other jobs, such as NT_MemUtil, on the Exchange Server.