Updated: 8/15/2016 Applies To: TestComplete Rating: AverageAverageAverageAverageAverage 1 vote(s) Click to rate: PoorNot badAverageGoodExcellent
Q.: TestComplete does not break the script running on breakpoints. How can I fix it?

A.: First of all, please make sure that the Debug | Enable Debugging item in TestComplete menu is checked and that the breakpoints are enabled (that is, they are marked with the red color).

Also, please make sure that the breakpoints are set on lines containing executable statements. The script debugger ignores breakpoints set on declaration statement (that is, lines with variable or routine declarations). The debugger also does not stop on conditional breakpoints if their condition or pass count is not met.

While following the steps described in this article, please write down the results you get so that you could send them to our Support Team if needed.

The script debugger is turned off if TestComplete is launched in silent mode (that is, with the /SilentMode parameter). If this is the case, please close TestComplete and launch it in the normal mode.

Note also, in order for you to be able use the script debugger, the user account that TestComplete is running under, must belong to the Debugger Users or Administrators group on your computer. You can check this in the Control Panel | User Accounts dialog.

In most cases, the problem is solved by installing or reinstalling Microsoft Script Debugger, which is available on Microsoft's web site.

If installing the Script Debugger does not solve the problem, please check whether the Process Debug Manager library (pdm.dll) is correctly registered in the system.

  1. Terminate the mdm.exe process via the Task Manager.
  2. Select Start | Run and type regedit in the command line.
  3. In the Registry Editor, locate the following key:


    Its default value should contain the path to the pdm.dll library. Please check if the library exists at this location.

    If the path is incorrect, please find the pdm.dll library on your hard drive (usually, it is located in the <Windows>\System32 folder) and set the correct path for this library.

  4. Close the Registry Editor.
  5. Register the pdm.dll library in the system. You can do this, by executing the following command (assuming that the library is located in the C:\WINDOWS\System32 folder):

    regsvr32 C:\WINDOWS\System32\pdm.dll

    Note: Run the Command Prompt window using the Run as Administrator command (see below).
  6. Restart the computer.

In certain cases, the path to the pdm.dll library may be reset after you reboot the computer. It happens if a program that is launched at startup changes this path. You can determine the conflicting program by using the Windows System Configuration utility:

  1. Select Start | Run and type msconfig in the command line.
  2. In the System Configuration Utility, switch to the Startup page.
  3. Disable some startup items and restart the computer.
  4. Check the abovementioned registry key value. If it has been reset, specify the correct path again and repeat steps 1-3.

If this does not help, please check whether the pdm.dll library is loaded into the TestComplete process. You can do this using the Sysinternals Process Explorer utility. This utility is free and can be downloaded from the following address:

  1. Launch Process Explorer.
  2. Select the Find | Find Handle or Dll item in the main menu.
  3. Enter pdm.dll and click Search.

If this library is loaded into the TestComplete process, you will see it in the search results. In case the library is not loaded, please contact the Support Team on the issue.

Debugging issues may also be caused by the incorrect registration of the Machine Debug Manager (mdm.exe) component in the system. To register this component, please follow these steps:

  1. Find all mdm.exe files on your computer.
  2. Register each mdm.exe component by executing the following command:

    mdm.exe /regserver

    Note: Run the Command Prompt window using the Run as Administrator command (see below).
  3. Restart the computer.

If the problem still exists, try copying the mdm.exe file from a computer where the debugger works fine to your computer (usually, this file is located in the <Windows>\System32 folder). Register this file as described above and restart the computer.

Note: We recommend that you make a back-up copy of the mdm.exe file on your computer, so that you can restore it if needed.

If the problem remains, try the steps below:

  1. Close Visual Studio and TestComplete.

  2. Check whether the VS7Debug folder is on your disk. As a rule, the folder is located here: "C:\Program Files\Common Files\Microsoft Shared\VS7Debug".

  3. If the folder exists, rename it to _VS7Debug, for example.

  4. Reinstall Microsoft Script Debugger:


    If you are using Windows 10, Windows 8, Windows 7, Windows Vista or Windows Server 2008, it is recommended to install the debugger with administrator privileges.

  5. After the installation is over, check whether TestComplete loads the modules that do not belong to Visual Studio. You can do this, for example, via the Process Explorer window.

If the debugger still does not work, run mdm.exe with administrator privileges.

To run the Command Prompt window in the Administrator mode
  • In Windows Vista or later:

    • Click the Windows button and open the All Programs | Accessories menu.
    • Right-click the Command Prompt item and choose Run as administrator from the context menu.
  • In Windows XP:

    • Click Start and then open the All Programs | Accessories menu.
    • Right-click the Command Prompt item and choose Run as from the context menu.
    • In the ensuing dialog, specify the name and password of the administrator's account.

If none of the above-mentioned procedures helps you solve the problem, please contact the Support Team.

© 2020 SmartBear Software. All rights reserved.
Email Send feedback on this document