Documentation forServer & Application Monitor

Troubleshoot AppOptics integrations with SAM

Following are issues you may encounter when integrating AppOptics with a node monitored by AppInsight for IIS. For more troubleshooting tips, search in the Success Center or THWACK.

The AppOptics integration is not compatible with FIPS mode. If FIPS is enabled on the Orion server, you cannot add a new integration for an IIS node in SAM. For existing integrations, SAM stops retrieving metrics from the AppOptics API.

AppOptics cannot be integrated on nodes monitored via Orion Remote Collectors.

Error Description Solution
No nodes appear in wizard IIS nodes do not appear on the Select Nodes page of the Add an Integration wizard. Check the AppInsight for IIS configuration on the target server. See Configure AppInsight for IIS on nodes and Troubleshoot AppInsight for IIS.
Agent failure Error deploying the AppOptics agent. Check the AppOptics agent logs stored in C:\ProgramData\SolarWinds\Logs\Remoting.
Internal error Error accessing the Orion database, which may occur if agent deployment fails. Redeploy the AppOptics agent on the Manage Agents page.
Package does not exist The AppOptics agent package was not found. Run the Orion Configuration Wizard and make sure the package is in the default location, \Orion\Remoting\RemoteExecutionPackage\SAM.AppOptics.
Timeout Installation took too long.

Examine logs in C:\ProgramData\SolarWinds\Logs\SAM.AppOptics, and C:\ProgramData\SolarWinds\Logs\Remoting.

Install error Error during remote installation of the AppOptics agent. Examine logs in
  • C:\ProgramData\SolarWinds\Logs\Remoting
  • Failed to copy files Error copying files from Orion server to the target server. Examine logs in
  • C:\ProgramData\SolarWinds\Logs\Remoting
  • Missing admin share Admin share on target server is disabled.

    Enable an Admin share on the target server.

    1. Ensure that the Orion server and the target server belong to the same Workgroup.
    2. Specify which user(s) can access Administrator Shares (Disk Volumes).
    3. Enable File and Print Sharing through the Windows firewall.
    4. Check to see if you can access the Admin share from another computer.
    5. Add AppInsight for IIS to the node via the Node Details view, or run the Discovery Wizard.

    Access denied Unauthorized access to the target server. Examine logs in
  • C:\ProgramData\SolarWinds\Logs\Remoting
  • Unknown error Possible invalid API token or another unrecognized error.

    Verify the API token. Reenter if necessary.

    Examine logs in C:\ProgramData\SolarWinds\Logs\SAM.AppOptics, and C:\ProgramData\SolarWinds\Logs\Remoting.

    No WMI support WMI on the target server is disabled, or the target server is turned off. Enable WMI polling on the target server.
    App Pool Error No application pools exist on the IIS server. Check that AppInsight for IIS is configured correctly on the target server. See Configure AppInsight for IIS on nodes and Troubleshoot AppInsight for IIS.
    IIS website error A Could not load file or assembly 'AppOptics.Agent, Version=3.3.3.0, Culture=neutral, PublicKeyToken=9195cde59f6d12e5' or one of its dependencies. The system cannot find the file specified message appears if the Orion Platform could not remove AppOptics from the IIS server.

    Follow steps in Uninstall the Agent. If that does not work, try this workaround:

    1. Start IIS Manager:
    2. Click the computer name of your IIS server.

    3. Click the Modules icon in the IIS category.

    4. Select the AppOpticsInstrumentation module, and then click Remove.
    5. Restart IIS services.

    If exception errors continue after removing the AppOpticsInstrumentation module from the IIS server, remove the module from the website also.

    AppOptics data does not appear in the Orion Web Console

    When you integrate AppOptics with an IIS node, SAM generates a service name (for example, jr-orbit-01-01-microsoft-iis-2-solarwinds-orion-application-pool).

    If you change the service name (also called a "service key") in AppOptics later, the connection breaks.

    Make sure the service name for the AppOptics integration in SAM matches the service name used in AppOptics. To learn more about service names, see the AppOptics documentation.

    If FIPS mode is enabled on the Orion server, SAM stops displaying AppOptics metrics.