3.9.x Documentation

AppDynamics Application Intelligence Platform

3.9.x Documentation

PDFs

Learn by Watching

Doc Maps

Skip to end of metadata
Go to start of metadata

This topic describes how to upgrade to the .NET Agent version 3.9. The instructions vary based upon your current version of the .NET Agent.

Upgrade the .NET Agent from Version 3.8.2 or Newer

When upgrading from the .NET Agent version 3.8.2 or newer, you do not need to uninstall the old agent first.

  1. Stop w3wp processes for instrumented IIS applications. Stop instrumented Windows services or standalone applications. 
  2. Install the new agent. See To install the .NET Agent.
  3. Restart the AppDynamics Agent Coordinator service:
    net stopAppDynamics.Agent.Coordinator
    net start AppDynamics.Agent.Coordinator
  4. Restart IIS one of the following ways:
    • Launch the configuration AppDynamics Agent Configuration utility and click Restart IIS on the Configuration Summary window.
    • Restart IIS by running iisreset from the command line.
    Restart Windows services and standalone applications.

Upgrade the .NET Agent from Version 3.7.8 to 3.8.1

The MSI installer package for the new version of the .NET Agent (the agent) installs the updated agent files and maintains all legacy configurations. After you complete the installation, start the AppDynamics.Agent.Coordinator service and instrumented applications to finish the upgrade.

To uninstall the old version of the agent

  1. Stop IIS, instrumented Windows services, and instrumented standalone applications.

    (tick) If you shut down IIS but continue to see active IIS Worker Processes, check the Application Pools pane in the IIS Manager and stop any started application pools.

    (warning) Failing to stop instrumented applications before uninstalling the .NET Agent may require you to reboot the machine.

  2. Stop the AppDynamics.Agent.Coordinator service.
  3. In the Control Panel, select Add/Remove Programs. Remove the AppDynamics .NET Agent.

(tick) In some cases another process interferes with the .NET Agent uninstallation process by locking the profiler.dll. If uninstallation fails, use a utility such as Process Explorer to see if a process is using profiler.dll. If so, terminate the process. Otherwise try rebooting the machine. Then retry the uninstallation.  

To install the new version of the agent

See To install the .NET Agent.

(tick) Don't launch AppDynamics Agent Configuration when the installer completes unless you want to make changes to the existing configuration. The installer maintains existing agent configurations.


To resume monitoring

  1. Start the AppDynamics.Agent.Coordinator service.
    net start AppDynamics.Agent.Coordinator
  2. Start IIS, instrumented Windows services, and instrumented standalone applications.

Upgrade the .NET Agent from Version 3.7.7 or Earlier

Identify the right upgrade path based upon the method of tier naming and assignment (manual or automatic) and the type of application you instrument:

  • If you use manual tier naming and assignment, the installer package upgrades configurations for IIS applications and Windows services.
  • If you used automatic tier naming and assignment, run the configuration utility to update configurations.
  • If you used standalone applications with 3.7.7 or earlier, follow the steps to Enable the .NET Agent for Windows Services and Standalone Applications.

The MSI installer package for the new version installs the updated agent files. After installing, you may need to run the configuration utility to update your configuration and optionally remove legacy configurations. Finally, restart the AppDynamics.Agent.Coordinator service and instrumented applications.

To uninstall the old version of the .NET Agent

  1. Stop IIS and instrumented Windows services.

    (tick) If you shut down IIS but continue to see active IIS Worker Processes, check the Application Pools pane in the IIS Manager and stop any started application pools.

    (warning) Failing to stop instrumented applications before uninstalling the App Agent for .NET may require you to reboot the machine.

  2. Stop the AppDynamics.Agent.Coordinator service.
  3. In the Control Panel, select Add/Remove Programs. Remove the AppDynamics .NET Agent.

(tick) In some cases another process interferes with the .NET Agent uninstallation process by locking the profiler.dll. If uninstallation fails, use a utility such as Process Explorer to see if a process is using profiler.dll. If so, terminate the process. Otherwise try rebooting the machine. Then retry the uninstallation.  

To install the new version of the .NET Agent

See To install the App Agent for .NET.

If you used the following environment variables with the earlier version, the MSI installer migrates the configurations to the new configuration file:

  • AppDynamicsAgent_CallGraphOptions
  • AppDynamicsAgent_DisableAppPools
  • AppDynamicsAgent_EnableInProcesses
  • AppDynamicsAgent_IgnoreCLREnv
  • AppDynamicsAgent_Profiler_Classes

Configure the .NET Agent

Configure the agent based on your method of tier generation and assignment: automatic or manual.

(info) The .NET Agent configuration utility only supports configuration of one Controller per server. To configure multiple business applications, see Configure Multiple Business Application Support for .NET.

To configure the agent using automatic tier generation and assignment

If you used automatic configuration with the earlier version of the .NET Agent, run the configuration utility to configure the agent:

  1. Use the .NET Agent Configuration utility to reconfigure instrumentation for IIS applications. Choose Automatic for the method of tier generation and assignment. See Configure the .NET Agent.
  2. Configure instrumentation for Windows services manually. See Enable the .NET Agent for Windows Services.

To configure the agent using manual tier generation and assignment

For manual systems using manual tier generation and assignment, the installer package migrates the configurations for IIS applications and for Windows services to the config.xml. At this stage, the configuration for IIS applications and Windows services is complete.

(info) If you choose not to launch the configuration utility and clean up legacy configurations, restart the AppDynamics.Agent.Coordinator service.

net stop AppDynamics.Agent.Coordinator
net start AppDynamics.Agent.Coordinator

To clean up legacy configurations

You can clean up legacy configurations by launching the AppDynamics Agent Configuration utility. When the utility detects agent settings from a previous version, it offers you the option to clean up.

(warning) The clean up procedures modifies the web.config files causing an IIS restart.

  1. Launch the AppDynamics Agent Configuration utility.
  2. Answer Yes to clean up old AppDynamics configurations.

    The utility removes the following configurations:

    • AppDynamics configSections from web.config files for IIS applications and from application.config files for Windows services.
    • Environment variables:
      • AppDynamicsAgent_IgnoreCLREnv
      • AppDynamicsAgent_CallGraphOptions
      • AppDynamicsAgent_EnableInProcesses
      • AppDynamicsAgent_DisableAppPools
      • AppDynamicsAgent_Profiler_Classes
  3. Proceed through the wizard normally.
    • Verify or update the log directory and grant write permissions to it.
    • Verify the controller connection information.
    • Verify or update manual tier assignment.

To resume monitoring

Start IIS and instrumented Windows services. 

Updated .NET Agent Directory Structure

To learn more about the updated App Agent for .NET Directory Structure, See .NET Agent Directory Structure.

Learn More


Have a question about the topic on this page? Ask the AppDynamics Community.