How do I increase debug logging for the Knowledge Scripts in the Microsoft Exchange 2007/2010 Module? (NETIQKB72416)

  • 7772416
  • 22-Jun-2010
  • 07-Dec-2010


NetIQ AppManager 7.x
NetIQ AppManager for Microsoft Exchange 2007 and 2010 Module and later
Microsoft Exchange 2007
Microsoft Exchange 2010


How do I increase debug logging for the Knowledge Scripts in the Microsoft Exchange 2007/2010 Module?


This Knowledge Base (KB) article, and the executable contained in the file that is linked to this KB, allow for the automatic creation of a debug Knowledge Script for the Exchange 2007/2010 Module beginning with version of the module.  This process does not apply to earlier versions of the knowledge scripts.

For assistance in increasing debug logging for Knowledge Scripts in earlier versions of the NetIQ AppManager for Microsoft Exchange 2007 module, please see NETIQKB71852.

Once the linked file has been downloaded and extracted, the following command line syntax can be used to easily expose the hidden variables to create additional logging that can be used to determine the case of certain types of failures when executing Exchange knowledge scripts.

An example of the syntax used to create the diagnostic version of the knowledge scripts are shown below.  The first example should be used if you wish to use SQL Authentication, and the second example will use NT Authentication.

  • CreateDiagnosticKS myqdbhost:QDB:sa:mypassword Exchange2007_MBS_MailboxUsage
  • CreateDiagnosticKS myqdbhost:QDB:: Exchange2007_MBS_MailboxUsage

The ?Exchange2007_? prefix and the ?.QML? suffix are optional on the KS name.  The tool checks out the knowledge script into the current directory and creates a copy of it with the diagnostic parameters exposed and with proper default values, then checks the copy into the QDB and deletes the original and diagnostic knowledge scripts?s from the current directory.  The diagnostic knowledge script is named the same as the original KS, but suffixed with ?_WITH_DEBUGGING?.

  1. From within the Operator Console, make a copy of the Exchange script that is generating the error.
  2. Rename the Script to indicate it contains additional tracing.
  3. Check the knowledge script out, and save it to your preferred location.
  4. Open the saved QML file with Notepad, not with the developer console.
  5. Search for "FDR_Tracing".
  6. Delete the entire line two lines below it that contains <I_Type>I_HIDDEN(0)</I_Type>
  7. Search for ?Raise event with job execution log?
  8. Edit the line four lines below that from <Value>n</Value> to <Value>y</Value>
  9. Search for "PRM_TraceLevel".
  10. Change the line two lines below that from <Value>Debug</Value> to <Value>Trace</Value>
  11. Delete the entire entry <I_Type>I_HIDDEN(0)</I_Type> that is two lines below the previous value.
  12. Save the file that you have made these changes to.
  13. Open the modified script in the Developer Console and check it back in being certain it has been renamed.
  14. Execute modified script on the Microsoft Exchange server with a Run Once schedule.
  15. Allow the job to complete.
  16. If an event is raised with the execution log for the job, copy and paste the text into a file and send it to NetIQ. If not, continue.
  17. Remote into the Microsoft Exchange server.
  18. Browse to C:\Program Files(x86)\NetIQ\Temp\NetIQ_Debug\{ServerName}
  19. Send the MCPSHostClient and MCPSHostServer files to NetIQ Technical Support for further review.

    Additional Information

    Formerly known as NETIQKB72416

    The linked tool is a .NET application therefore .NET Framework must be installed on the computer on which it is to be run.  Due to .NET security restrictions, it must be run from a local disk rather than a file share.  Also, it must be run from a machine that has kscheckout.exe and kscheckin.exe installed, and the directory where they are located must be in the PATH.


    If you need further assistance with the subject matter discussed in this Knowledge Base Article, please contact NetIQ Technical Support.