Resolve .NET Agent Installation Issues

If the Agent installation is failing, check these configurations in your environment:

Verify Administrative Privileges

Ensure that you have administrative privileges when you launch the installer. If the current user doesn't have sufficient privileges, the installer prompts you for an administrator password.

Verify MSDTC is Enabled and Running for the Correct Account

If you encounter an error that MSDTC is not enabled or it is running for the wrong account, launch an elevated command prompt with full administrative privileges and execute this command:

msdtc -install

Even if MSTDC is already installed, this command resets the service to run using the "NT Authority\NetworkServices" account.

Generate a Log for Agent Installation Failures

If the installer fails, use this command-line utility to launch the installer:

msiexec /i $Path_to_the_MSI_File /l*v verbose.log

A verbose log for the .NET Agent is created at the same location where you saved the installer file.

Rectify Failed Installation Caused by Other APM Products

The .NET Agent installation may fail if there are other Application Performance Management (APM) products installed in the same managed environment. Remove the associatedEnvironmentsubkey for certain services for the installed APM products.

To remove the associated environment subkey for W3SVC and WAS services in the registry:

  1. Run Regedit or regedt32.
  2. In regedit.exe, locate these registry keys: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W3SVC HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WAS
  3. Expand the keys.

  4. Modify the Environment subkey to delete these values:

    COMPLUS_ProfAPI_ProfilerCompatibilitySetting=EnableV2Profiler
COR_ENABLE_PROFILING=1
COR_PROFILER= {a GUID}
  5. Restart the services. See How to restart the W3SVC and WAS services?