ADPlus Limitations and Restrictions

The following notes and restrictions apply to ADPlus:

• You must install the Microsoft Windows Script Host components before you can run ADPlus. The current version of ADPlus requires version 5.6 of the scripting host.

  You can run ADPlus with earlier versions of the scripting host if you start ADPlus in a Command Prompt window by using the install directory of Debugging Tools for Windows as the default directory. However, the -quiet switch requires version 5.5 in any event.

  Windows Script Host components might already be installed if you have installed recent versions of certain Microsoft software products. If you want to install or upgrade the Windows Script Host, visit the  Windows Script section of the MSDN Web site.

• The -iis option requires version 4.0 or a later version of Internet Information Services (IIS), formerly known as Internet Information Server.
• If you use the -quiet option, ADPlus logs information to the event log on systems that are equipped with the Windows Script Host version 5.5 or later.
• If you use the -o option, the specified path must not contain more than one nonexistent folder. For example, if you specify -o C:\Temp1\Temp2 and the C:\Temp1 and \Temp2 folders do no exist, ADPlus displays an error message and does not create these folders. If you specify -o C:\Temp1, ADPlus creates the C:\Temp1 folder if it does not exist and puts all output files in that folder. If you are specifying multiple subfolders and using the -o option, you should make sure that all of the subfolders exist before you run ADPlus.
• In COM+, you can configure a server package to start in the debugger in the Advanced tab in the Properties dialog box of the package. If you enable the Launch in Debugger option, ADPlus cannot attach the CDB debugger to a process. (By default, only one debugger can be attached to a process at a time.)
• When a remote procedure call (RPC) is made from a process that ADPlus is analyzing in crash mode to another process that has failed or has been shut down, the log file that ADPlus creates for the process that is being monitored might contain one or more of the following exceptions.

  Unknown exception - code 80010105 (first chance)
  Unknown exception - code 800706be (first chance)
  Unknown exception - code 800706ba (first chance)
  

  These exceptions are expected. RPC raises these exceptions when a call is made from a process that is being monitored to a nonexistent or failed process.

  This exception typically appears after IIS calls an out-of-process (high-isolation) Web site that has failed. This exception might be followed by two instances of the following exception.

  Unknown exception - code 800706ba (first chance)