This guide provides a description of troubleshooting steps for resolving issues with the Dotcom-Monitor On-Prem Load Injector and Proxy Agent installation and performance.

Troubleshooting Steps

LoadView performs a series of system checks upon registration On-Prem Load Injector and Proxy Agent with the user’s LoadView account. The basic check results are provided in the Registrator window. To run advanced checks, follow the guide below:

  1. In the Registrator window, click Options. To start Registrator, go to the Start menu > Programs > Dotcom-Monitor and select the corresponding Registrator.
  2. Under the Diagnostics tab, click Do Check.
  3. Once all checks are completed, click View Logs, Copy To Clipboard.
  4. Log in to your LoadView account and submit the log file in a support ticket.

Comprehensive List of Checks

Service Configuration

This check ensures that all necessary registry keys and environment variables are correctly set up. The service should be running under the LocalSystem account, and the startup type of the service should be set to Automatic (Delayed Start).

API Entry Points Availability

This check verifies the availability of the server endpoints required for the specific agent to function correctly. It ensures that the agent can retrieve its configuration from the server.

API Entry Point Certificates

This check confirms that Dotcom-Monitor certificates are used in requests to the server. This ensures secure communication between the agent and the server.

OS Supports IPv6

This check verifies that the operating system supports the IPv6 protocol. IPv6 support is essential for modern networking and ensures the agent can communicate over IPv6 networks.

Windows Time Service

This check ensures that the Windows Time Service (W32Time) is enabled to ensure correct load test execution and reporting.

Remote Desktop (On-Prem Load Injector only)

For On-Prem Load Injector, the check verifies the following requirements:

  • The Terminal Services (TermService) are running with an Automatic startup type.
  • The “DotcomMonitorRdpUser” system user has been created.
  • The Always Prompt for Password group policy is set to Not Configured or Is Disabled.

If the Always Prompt for Password group policy is set to Enabled and your security policy requires enforcing a password prompt, please see the LoadView On-Prem Load Injector Installation & Configuration article for policy configuration tips.

Microsoft Windows OS Version (On-Prem Load Injector only)

For On-Prem Load Injector, the check verifies that the operating system is Windows Server 2016 or later. This ensures compatibility and support for the required features.

Windows Media Player (On-Prem Load Injector only)

For On-Prem Load Injector, this check ensures that Windows Media Player (WMP) is installed on the machine. WMP is required for web application load tests executed in a real browser window.

TLS Protocols

These checks verify that the TLS 1.0, TLS 1.1, TLS 1.2, and TLS 1.3 protocols are enabled. TLS (Transport Layer Security) protocols are essential for secure communications. Ensuring these protocols are enabled helps maintain secure connections between the agent and other systems.

  • TLS 1.0: Verifies that TLS 1.0 is enabled.
  • TLS 1.1: Verifies that TLS 1.1 is enabled.
  • TLS 1.2: Verifies that TLS 1.2 is enabled.
  • TLS 1.3: Verifies that TLS 1.3 is enabled.