Troubleshooting Debugger Configuration Issues

Troubleshooting Debugger Configuration Issues

It is essential for us to ensure that you have reviewed and fully followed all the steps for configuring the debugger as outlined in the link below: Configure the Debugger

Please pay special attention to the following key points: 

  • Verify that the required library ssdebugps.dll is present.
  • Ensure the correct command prompt (%windir%\SysWoW64\cmd.exe) is being used.

Additionally, you may have noticed that a diagnostic tool is available on the same page to verify whether your debugger environment is configured correctly: Check Debugger Tool

We recommend using the tool and following the instructions to check your configuration.

If the issue persists, please send us a screenshot of the diagnostic tool results. Our team will then analyze the results and help localize the problem.

    • Related Articles

    • Troubleshooting Manual Activation issues

      If you are experiencing difficulties with Manual Activation despite following the documentation in the Licensing and Activation section for your product (available at Devart Documentation), please consider the following steps to resolve the issue. ...

    • Troubleshooting Devart Account or File Download Issues

      If you’re experiencing problems with accessing your Devart account, pages not loading correctly, or being unable to download files, please follow the steps below to troubleshoot the issue and help our support team assist you efficiently. Before ...

    • Unable to Connect Using macOS DSN Configuration

      If you’ve installed an ODBC driver on macOS but can’t proceed with setting up a DSN because the iODBC Data Source Administrator app is missing, here’s how to resolve the issue. Step 1: Install iODBC Manager To test and manage ODBC connections on ...

    • CPU Metrics Not Displayed in dbForge Monitor for SQL Server

      Symptoms When using dbForge Monitor for SQL Server, you may notice that CPU metrics are not displayed for some of the active connections. An example of this issue is shown below. The following notification will be displayed: Cause This issue is ...

    • Resolving Assembly Version Issues by Cleaning the Global Assembly Cache (GAC)

      You might encounter assembly version conflicts if an incomplete uninstall of a previous dotConnect provider leaves an empty folder in the Global Assembly Cache (GAC). This is an uncommon occurrence. Accessing the Global Assembly Cache: The Global ...