Troubleshoot AppOptics integrations with IIS nodes in SAM
Following are troubleshooting tips for issues you may encounter when integrating AppOptics with AppInsight for IIS nodes.
For example, if you're adding AppOptics to a node, but an expected node does not appear in the Integration wizard, check if:
- The node is set up for AppInsight for IIS. See Configure AppInsight for IIS on nodes and Troubleshoot AppInsight for IIS.
- The node is polled by an SolarWinds Platform Remote Collector (ORC), which is not supported by AppInsight for IIS.
- FIPS mode is enabled on the SolarWinds Platform server. The AppOptics integration is not compatible with FIPS mode. For existing integrations, SAM stops retrieving metrics from the AppOptics API.
The following table includes more tips. You can also search in the Success Center or THWACK.
Issue | Description | Solution |
---|---|---|
Agent failure | Error deploying the AppOptics agent. | Check the AppOptics agent logs stored in C:\ProgramData\SolarWinds\Logs\Remoting . |
Internal error | Error accessing the SolarWinds Platform 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 SolarWinds Platform Configuration Wizard. Verify the agent package is in the default location, \Orion\Remoting\RemoteExecutionPackage\SAM.AppOptics . |
Timeout | Installation took too long. |
Examine logs in these locations:
|
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 SolarWinds Platform 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.
|
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 these locations:
|
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=x.x, Culture=neutral, PublicKeyToken=xxx' or one of its dependencies. The system cannot find the file specified message appears if SAM could not remove AppOptics from the server. |
Follow steps in Uninstall the Agent. If that does not work, try this workaround:
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 SolarWinds Platform Web Console |
When you integrate AppOptics with an IIS node, SAM generates a service name (for example, 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. For details about service names, see AppOptics documentation. If FIPS mode is enabled on the SolarWinds Platform server, SAM stops displaying AppOptics metrics. |