This page describes issues you may encounter when installing the .NET Agent. 

Verify Agent Controller Communication

Use the  UI to verify that the agent can connect to the Controller.

1. In a browser open:

   http://<controller-host>:<controller-port>/controller

   If you cannot connect to the Controller in Internet Explorer, see Check Internet Explorer proxy settings.

2. Log in to the Controller UI.
3. Select the application to open the Application Dashboard.
4. In the left navigation panel, select Servers > Tiers & Nodes and open the Health tab.

The Health tab lists the tiers, their nodes, and App Agent Status. When an agent successfully reports to the Controller, an up arrow symbol displays.

See Agent-to-Controller Connections.

• When deploying multiple agents for the same tier, determine if the correct number of nodes reports into the same tier.
• After sending a request to your web application, data should display on the Controller UI. The agents should display in the Application Flow Map of the Application Dashboard.

If no data displays after a few minutes:

• Verify that the Agent is writing its log files.
  Windows Server 2008 and later: %ProgramData%\AppDynamics\DotNetAgent\Logs\AgentLog.txt
• If the log file exists, open it and review for errors.
• If the log file does not exist, run the Windows Event Viewer and review the application messages.
• If there are no  event messages, look for messages from the .NET Runtime.

Check Internet Explorer Proxy Settings

Misconfigured proxy settings in Internet Explorer may cause the App Agent for .NET to fail to connect to the Controller.
If the test Controller connection fails on the Controller Configuration pane in the  Agent Configuration utility:

1. Verify the Controller host and port settings are correct.

2. In Internet Explorer, open:

   http://<controller-host>:<controller-port>/controller

3. If the connection also fails in Internet Explorer, check the proxy settings. See Change IE Proxy Settings.
4. Correct or remove any incorrect proxy settings.

Checklist for Resolving  Installation Issues

	Item	Notes
	Run the installer as Administrator.	Verify Administrative privileges
	Verify that MSDTC is enabled and that it is running under the correct account.	Verify MSDTC is enabled and running under the correct account
	Verify permissions for Agent directory.	Verify that the .NET Agent directory has the correct permissions based on the site’s application pool identity.
	Verify that the Agent is compatible with the Controller.	Agent and Controller Tenant Compatibility
	Verify the correct settings in the config.xml: Windows Server 2008 and later: %ProgramData%\AppDynamics\DotNetAgent\Config\config.xml	Update the config.xml file to include the .NET Agent Configuration Properties.

Resolve  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 associated Environment subkey 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?

Resolve Configuration Errors

• Set your IIS applications to a Full trust level. .NET Agent reporting will not work if an IIS application is set to anything other than a Full trust level.
• Ensure that you have correctly configured the config.xml file for the App Agent for .NET. See .NET Agent Configuration Properties.

• If you manually edited the config.xml file, check the AgentLog.txt file and WarnLog.txt file for errors. Invalid XML displays in the log as:

  2014-03-13 10:49:18.7199 1232 dllhost 1 1 Error ConfigurationManager Error reading the configuration file

• Resolve Log Issues

The .NET Agent writes logs to these directories: 

 %ProgramData%\AppDynamics\DotNetAgent\Logs

The agent will not generate logs if the agent directory does not have sufficient permissions.

Verify that the .NET Agent Directory has the Correct Permissions

1. Select IIS > Application pools.
   IIS displays the list of application pools for your machine.
   
2. Right-click a particular application pool.
3. Select Advanced Settings.
   
   IIS displays the Application Pool Identity for that application.
   
4. Ensure that your Agent Directory also has the same permissions as your site application pools.
   • Navigate to .NET App Server Agent directory location.
   • Right-click the logs directory for the App Server Agent and select Properties.
     
     
     
   • Select the Security tab, and verify that the same Application Pool Identity is specified for the .NET Agent directory.
     

If the Agent logs directory does not have the required permissions:

1. In the Security tab, select Edit.
2. Select Add to add new permissions to the Agent directory.
3. Select Advanced.
4. Click Find Now to find all the users, groups, or built-in security principals on your machine.
5. Select the required group from the list and click OK. Review the information that follows for Allowed groups.
6. Provide the read and write permissions for the selected user/group/security principal to the Agent directory and click OK.
7. Click Apply.

Allowed Groups for Different IIS Versions

For IIS 6.x, these settings are applicable for Application Pool Identities:

For IIS >= IIS 7.0, these settings are applicable for Application Pool Identities:

For example, if your application has the identity ApplicationPoolIdentity, you must provide the permissions for IIS_IUSRS group to your agent directory.

Another Version of  Detected

.NET Agent >= 20.3 supports .NET Core. If you used the Microservice Agent to monitor .NET Core applications you can monitor .NET Core with the full .NET Agent. You may receive an error message in the MSI Installer stating that another version of  is detected. 

The Microservice Agent uses a JSON file to store configuration information while the .NET Agent uses an XML file. The data does not migrate between these files. 

To fix this issue, you need to map the data in the JSON file to the XML file, config.xml and remove environment variables. If you have completed the instructions above and still see the error, you may need to reboot your machine. You may want to plan reboots according to your planned outage schedule. 

Known Issues

You may ignore the following error from the AppDynamics.Agent.Coordinator service in the agent.log or warn.log:

2015-12-01 10:12:03.0435 3872 AppDynamics.Coordinator 1 7 Warn MaxQueueItemAgePolicy MaxQueueItemAge is beyond the integer limit: 13093467123