Exchange 2007 Knowledge Script generates a PowerShell error in the AppManager console. (NETIQKB71788)

  • 7771788
  • 03-Sep-2009
  • 13-Jul-2011


NetIQ AppManager 6.x
NetIQ AppManager 7..0.x


How do I increase the logging level for the Microsoft Exchange 2007 Module when the Knowledge Scripts results in PowerShell errors?


In order to get a get a detailed error message which could help is diagnosis the PowerShell errors perform the folllowing steps which will increasing the logging level for the Knowledge Scripts in the Exchange 2007 Module:

On the Exchange 2007 server running the Exchange 2007 module follow the steps below:

  1. Browse to C:\Program Files(x86)\NetIQ\AppManager\Bin\PowerShell
    • Locate and edit the following two files:
      • MCPSHostServer.exe.config
      • MCPSHostClient.dll.config
    • Change the logging level from "Error" to "Debug" in both files and save the changes.
  2. Execute the knowledge script that is generating the error, and allow the error to appear.
  3. Browse to C:Program Files(X86)\NetIQ\Temp\NetIQ_Debug

Two PowerShell log files will be shown here the MCPSHostClient.log and the MCPSHostServer.log.  These logs will show the detail of the PowerShell commands being passed to the Exchange server as well as errors generated.  You can take the commands shown in the logs and execute them in Exchange Management Shell while logged in at the service account running the agent on the Exchange Server to verify if the command executes properly.  If the command fails in Management Shell as well, the informational error presented in the Management Shell should be provided to the Exchange Administrator to review for reasons as to why the call is failing.  If the command succeeds in Management Shell, but not from the knowledge script then the error logs will have to be monitored for additional details as to the cause of the failure. In this situation contact NetIQ Technical Support for further assistance in resolving the issue.


Exchange 2007 knowledge script generates a PowerShell error in the AppManager console but no additional information is reported in order to determine the root cause of the problem.

Additional Information

Formerly known as NETIQKB71788