Environment
NetIQ AppManager 6.x
NetIQ AppManager 7.0.x
Microsoft Exchange Server 2003
Situation
Error: '432 file name or class name not found during OLE operation'
Resolution
In most cases, this error is caused by a mismatch between the versions of the Managed Object and the Knowledge Scripts. For every Managed Object update, the MO must be installed on the AppManager Repository and the Agent that runs the MO (such as the Agent monitoring an Exchange server).
To verify the Knowledge Script itself:
- Confirm the Exchange Managed Object (Qexch2k1a.EXE) is running the most up to date version (check the AppManager Module upgrades page for the latest version: https://www.netiq.com/support/am/extended/modules.asp)
- Verify that the same update was performed on the Repository QDB Server and the Script version history reflects the correct version. You can right-click the Agent machine in the Operator Console Tree View and click Properties.
- Check the version history and the location of the Knowledge Script you are using. Customized Knowledge Scripts may not respond when used on an updated MO.
- Drop a new, unmodified Knowledge Script for testing purposes to verify that it is not an issue related to the existing job script
If the KS appears to be valid, confirm the AM Agent settings and registry keys:
- On the Exchange Server Managed Client
- Log on to the Server with the AppManager service account
- Go to Start | Run | Regedit
- When the registry editor comes up, certify the existence of the following Key:
HKEY_Classes_Root\NetIQAgent.<servername>\CLSID
If it exists write down the "data" number and look for the ProgID by verifying
HKEY_Classes_Root\CLSID\{WrittenNumberYouTookDown}\ProgID
More than likely one or more of these is missing. If it is missing, re-install the Agent and "replace all components" during the install. After re-installing, verify the existence of these keys and re-run the Exchange Discovery.
Cause
Exchange 2000/2003 Knowledge Scripts can not find the NetIQ Agent registry key.