Troubleshooting bulk installation failures of the APM Insight .NET Agent: common issues and solutions

Troubleshooting bulk installation failures of the APM Insight .NET agent

You can perform a bulk installation during the .NET agent installation. If the bulk installation fails, it could be due to one of the following reasons:

 Error message/Issue
 Troubleshooting tip
 Network connectivity failure
Ensure all machines within the domain are properly connected to the network.
 Incorrect username and password
Verify that you have entered the correct credentials for your Active Directory account.
 Proxy error
Confirm that the proxy configuration is correct. The .NET agent uses the proxy details of the server where it is installed, so make sure that the proxy configuration is accurate for both servers within the domain.
 Accessibility error
Check that the URL staticdownloads.site24x7.com/apminsight/agents/apminsight-dotnetagent.msi is accessible via Internet Explorer.
 Remote issues
Verify that the target server is accessible remotely from the server where the .NET agent is installed.
 Agent installation error
Ensure the machine within the domain does not already have the agent installed.
 Error message: 
"Couldn't connect to \servername\ADMIN$. The network path was not found"
Go to Advanced Sharing Settings > Domain. Enable Network discovery and File and printer sharing. Refer to the screenshot below.





    • Related Articles

    • APM Insight .NET agent bulk installation using ManageEngine Endpoint Central

      You can install the APM Insight .NET agent on multiple machines at once by following the steps given below: Download the APM Insight .NET agent from the Site24x7 account. Log in to the ManageEngine Endpoint Central portal and click the Software ...
    • How to identify and resolve conflicts between other APM products and the APM Insight .NET agent

      Problem statement: You are experiencing either of the below issues and suspect that another APM product is interfering with the Site24x7 .NET agent. 1. The .NET monitor is not created under APM > APM Insight > Applications, even after the .NET agent ...
    • How to add APM Insight Java agent without application restart?

      In general, after installing the APM Insight Java agent, you have to restart your application for the agent to capture monitoring data. But in case of critical issues in the app, like sudden application slowness, where you haven't installed APM ...
    • DC migration steps for APM Insight agents

      For Server based installations 1. Obtain the new device key. 2. Update the license.key value in the APM Insight configuration file (or the environment variable mentioned) with the new device key. The location varies for each agent, as listed below: ...
    • APM Insight agent log paths

      Folder path to view One agent logs One agent logs can be found only in the common application folder in Windows (usually under C:\ProgramData from Vista onwards). Check the following folder path in Windows: C:\ProgramData\Site24x7APMOneAgent\Logs ...