How to verify:

Run the following command using Windows PowerShell (Administrator mode):

Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' -Recurse | Get-ItemProperty -Name Version, Release, SP -ErrorAction SilentlyContinue | Where-Object { $_.PSChildName -match '^(?!S)\p{L}'} | Select-Object PSChildName, Version, SP, Release

Requirements:

• Confirm that .NET Framework v3.0 is listed and has SP ≥ 1
• Confirm .NET Framework v4 (Full) is listed and has Release ≥ 378389

Resolution (if .msi installation fails despite prerequisites being met):

1. Recheck prerequisites and try the Installation via command line.
2. If issue still persists, locate the apm_install.log file in the installation directory & send the log file to appmanager-support@manageengine.com for further assistance.

Outbound communication from the agent-installed machine to the Applications Manager (Host and Port) should be allowed — either directly or via a proxy.

How to verify:

1. Get the configured “Apm Endpoint Urls” from the APM Insight .NET Agent Configuration tool.

2. Open the same URL in a browser on the agent-installed machine and confirm it loads.

3. Run the below PowerShell command (as Administrator) using the same “Apm Endpoint Url”:

add-type 'using System.Net;using System.Security.Cryptography.X509Certificates;public class TrustAllCertsPolicy : ICertificatePolicy {public bool CheckValidationResult(ServicePoint a,X509Certificate b,WebRequest c,int d){return true;}}';[System.Net.ServicePointManager]::CertificatePolicy=New-Object TrustAllCertsPolicy;(Invoke-WebRequest -Uri '<Apm_EndPoint_Urls>'/index.do).Content -split "`n" | Where-Object {$_ -match 'Applications Manager'}

Verify the output contains the text “Applications Manager”:

4. If the output does NOT contain “Applications Manager”, the configured endpoint is incorrect or network/firewall is blocking communication.

Resolution:

1. Ensure the correct endpoint is configured.
2. Ensure the network and firewall configuration allows communication from the APM Insight .NET agent installed machine to the Applications Manager.
3. If a proxy is used, specify the “Proxy Authentication” → Behind Proxy in the “Edit APM Insight .NET Agent Configuration” tool.
4. After updating the settings, restart the application and the APM Insight .NET Agent service for the changes to take effect.

How to verify:

1. Open Task Manager → Details tab.
2. Locate your target application process: w3wp.exe for IIS app, <service_name>.exe for services, or the main executable for desktop apps.

3. Note the “User name” and go to the above folder (C:\ProgramData\DotNetAgent & C:\ProgramData\DotNetCoreAgent) → Properties → Security.
4. Confirm the user/group (e.g., IIS_IUSRS, SYSTEM, or service account) has Read & Write permissions.

Resolution:

1. If missing permissions, click Edit → Add → [User Name] → Allow Read & Write permissions.
2. Restart the application and check.

Running multiple profiler-based agents simultaneously can cause application instability and conflicts.

Follow these steps to identify and resolve conflicts between other APM products and the APM Insight .NET agent.

SharePoint and Multi-Domain environments require specific configuration changes due to security concerns.

Follow these steps to identify the SharePoint/Multi-Domain environment and configure the “Support Multi-Domain Applications” checkbox.

Cause: “APM Endpoint Urls” configured with invalid Applications Manager host/port. Sometimes the port is configured with the OpManager port instead of the Applications Manager port.

Resolution:

1. From the Applications Manager server, navigate to Settings → Tools → Support → Installation Information to get the Web Server Port & SSL Port.

2. Ensure the same is configured in the “Apm Endpoint Urls” from the APM Insight .NET Agent Configuration tool.

3. Open the same URL in a browser on the agent-installed machine and confirm it loads.

4. Run the below PowerShell command (as Administrator) using the same “Apm Endpoint Url”:

add-type 'using System.Net;using System.Security.Cryptography.X509Certificates;public class TrustAllCertsPolicy : ICertificatePolicy {public bool CheckValidationResult(ServicePoint a,X509Certificate b,WebRequest c,int d){return true;}}';[System.Net.ServicePointManager]::CertificatePolicy=New-Object TrustAllCertsPolicy;(Invoke-WebRequest -Uri '<Apm_EndPoint_Urls>'/index.do).Content -split "`n" | Where-Object {$_ -match 'Applications Manager'}

Verify the output contains the text “Applications Manager”:

5. If the output does NOT contain “Applications Manager”, the configured endpoint is incorrect or network/firewall is blocking communication.

• Ensure the correct endpoint is configured.
• Ensure the network and firewall configuration allows communication from the APM Insight .NET agent installed machine to the Applications Manager.
• If a proxy is used, specify the “Proxy Authentication” → Behind Proxy in the “Edit APM Insight .NET Agent Configuration” tool.

6. After updating the settings, restart the application and the APM Insight .NET Agent service for the changes to take effect.

Cause: The configured “License Key” in the “Edit APM Insight .NET Agent Configuration” tool might not match the Applications Manager configured in “Apm Endpoint Urls”. Sometimes users configure a different Applications Manager’s license key instead of the one matching the configured endpoint.

Resolution:

1. Login to the Applications Manager configured in “Apm Endpoint Urls”. Navigate to APM → Add Monitor → .NET – Configure Now → APM Insight License Key. Copy the license key and replace it in the “License Key” value on the “Edit APM Insight .NET Agent Configuration” tool.

2. Restart the agent service and application to reflect the changes.

Cause: In APM Insight .NET Agent v7.0.2 or later, application onboarding may fail if the “Use Data Exporter” option is disabled in the Edit APM Insight .NET Agent Configuration tool. When disabled, the agent reverts to service mode and does not export data to Applications Manager.

Resolution:

1. Open Edit APM Insight .NET Agent Configuration on the agent-installed machine.
2. Enable “Use Data Exporter” under General → Exporter Configuration. Click Save.
3. Run IISRESET from an administrator command prompt OR restart the relevant application service.
4. Generate application traffic, then check for monitoring.