Documentation forOrion Platform

Deploy SolarWinds Orion Platform products to Microsoft Azure

This topic applies to all Orion Platform products.

This guide is intended for new installations of Orion Platform products in Microsoft© Azure VM, using an Azure Virtual Network (VNet). It does not cover migrating products to the cloud. The information outlined in this guide is applicable for all Orion Platform products that support cloud deployments.

To reduce the number of places you have to configure your ports, SolarWinds recommends all cloud instances be in the same availability zone and in the same VNet. SolarWinds recommends using availability zones closest to your monitored devices.

The only exception to this rule are High Availability backups. When deployed in Microsoft Azure, HA backups must be deployed in a different subnet.

How do I deploy Orion Platform in Azure?

Before you begin

  1. Review Orion Platform deployment options for Azure.
  2. Review the requirements.
  3. Prepare for the installation.
  4. Prepare the environment.

Installation and configuration time

  1. Install Orion Platform in the Azure cloud.
  2. Deploy Azure Active Directory app.
  3. Configure Azure IAM Permissions.

Optional tasks

  1. Deploy Orion agents in the cloud (optional).
  2. Install an Additional Polling Engine or additional web server (optional).
  3. Enable High Availability (optional).
  4. Troubleshooting

Task 1: Review Azure Deployment types

Your main Orion server and your Orion database server should be hosted at the same location, either both servers are on-premise or both are in the cloud. Hosting the main Orion server and database servers separately is not recommended due to connectivity concerns.

SolarWinds recommends that all components (Orion server, Orion database) are deployed in the same region. If you run High Availability, deploy all components on one availability group.

Regardless of deployment location, it is important the main Orion server and Orion database are hosted on different servers.

SolarWinds is not responsible for fees incurred when deploying SolarWinds products to the cloud.

Cloud (main Orion server and database in the cloud)

SolarWinds recommends this deployment when your monitored environment resides mostly in the cloud, and you have a good understanding of how much computer capacity you require to monitor your environment.

You have the following options to deploy the database:

  • Use the Azure SQL Database managed instance service (starting with Orion Platform 2019.4).
  • Use the Azure SQL DB service (Orion Platform 2019.2 and later).
  • Use the Microsoft SQL database deployed on an Azure VM.

For details on additional databases used by Orion Platform products, such as NTA or Log Analyzer, see Databases used by SolarWinds modules.

Hybrid (Additional Polling Engines in the cloud; main Orion server and database on-premise)

Use this deployment type when the majority of your monitored networks are on-premise or if your hybrid environment is geographically diverse and use different availability zones.

You can also deploy agents to your nodes in the cloud to reduce the amount of data transferred within the Virtual Machine instance - and from the Virtual Machine instance - to your main Orion server.

You will need to create a virtual private network (VPN) tunnel between the Additional Polling Engine (APE) in the Azure VM instance and your main Orion and Orion database servers.

For details on additional databases used by Orion Platform products, such as NTA or Log Analyzer, see Databases used by SolarWinds modules.

Hybrid (Main server and database in the cloud; APE on-premise)

This deployment is recommended when your monitored environment includes a significant number of on-premise devices, or if you are migrating your infrastructure to the cloud.

For details on additional databases used by Orion Platform products, such as NTA or Log Analyzer, see Databases used by SolarWinds modules.

Task 2: Review requirements

To deploy a single Orion Platform product on Microsoft Azure, consider using the following instance types, based on your deployment size.



SL100, SL250, SL500





XL (up to 1,000,000 elements)

Orion server





SolarWinds Orion database using Azure SQL DB

All installed products must run on Orion Platform 2019.2 or later.

Time zone setting of the Orion Server must be in the same time zone as Azure SQL DB time zone (UTC).

When deploying Azure SQL and creating a new user in the Configuration wizard, SA account credentials are required in the Configuration wizard.

DTU Standard Tier S3 or better

vCore General Purpose Tier 2 or better

DTU Standard Tier S3 or better

vCore General Purpose Tier 2 or better

DTU Standard Tier S4 or better

vCore General Purpose Tier 2 or better


vCore Hyper-Scale 40 vCPU

SolarWinds Orion database using Azure SQL Database managed instance

4 vCores

8 vCores

16 vCores

40 vCores

SolarWinds Orion database deployed in an Azure VM


DS4_v2 Standard



IOPS 30,000+

Azure instances required for additional databases

Some Orion Platform products, such as NTA or Log Analyzer, use additional databases. For more details, see Databases used by SolarWinds modules.

To use Azure SQL database, review requirements for the Orion database.

To deploy a supported version of MS SQL server on an Azure VM and use it as the database for NTA or Log Analyzer, review the requirements in the following table (the table uses NPM license levels for reference).

Instance Details

Medium (SL2000)

Large (SLX)

Instance type




30.5 GB RAM
- 8 GB for every received sustained 1000 Flows/s (NTA) or EPS (LA) with 30-days retention period

122 GB RAM
- 2.5 TB is Flow Storage, 300k FPS (NTA) or EPS (LA) with 30-days retention, Azure Storage Disk with Provisioned IOPS recommended)
DiskSystem SSD 80 GB (included in D12_v2) + Data Azure Storage Disk Volume 500 GB*System SSD 320 GB (included in D12_v2) + Data Azure Storage Disk Volume 2.5 TB*

* Azure Storage Disk volumes are not your dedicated hardware. Consider using Azure Reserved Instances of storage disk volumes for SQL servers.

Task 3: Prepare Orion Platform for installation

This checklist helps you prepare for Orion Platform product installations.

Review release notes

Review product release notes and available documentation in our Success Center.

The VMAN appliance is not supported in cloud deployments.

Review system requirements

Ensure your cloud instance has the required hardware and software specifications for your installed products. Certain products may require more or additional resources than the base cloud requirements.

If you install multiple products, a good rule of thumb is to add one CPU core per additional product.

Product requirements include:

For all port requirements, see Port Requirements for all SolarWinds products.

Determine your deployment type

Which components are you hosting in the cloud? Keep in mind the Azure pricing model and your estimated usage.

If you intend to set up SolarWinds High Availability now or in the future, review the Enable High Availability section before setting up your cloud instances. The VNet and port requirements are different and may be difficult to change in the future.

If you intend to deploy agents, review the Deploy Agents in the cloud section. Agents have additional port requirements.

Review licenses and gather keysReview your product licenses and determine if you need to make any changes. You can download license keys for your new Orion Platform products through your Customer Portal. Verify any license upgrades and requirements with your SolarWinds account manager or contact SolarWinds.
Gather credentialsMake sure you have all account credentials, such as your SQL database credentials, your SolarWinds Customer Portal account, your Azure credentials, and Windows local admin server credentials.
Schedule the installation

Set up the maintenance window, preferably during off-peak hours. Depending on the number of products, size of database(s), and size of environment, you may require multiple hours to complete your installation.

Notify your companySend a message to your company of the upgrade schedule and maintenance window. If you need additional help, contact and allocate specific staff to be available.

Task 4: Prepare the environment

Depending on your licensed Orion Platform products, you may need to prepare multiple servers and configure ports in your firewall before installation.


Prepare the cloud network (optional)SolarWinds recommends using a public DNS hostname and a public IPv4 address.
Create your VNetCreate the VNet that will contain your SolarWinds Orion environment.
Create the network security group and open ports
  1. Define the network security group for your Orion environment. All SolarWinds Orion components installed in the cloud, such as your main Orion server, Orion database, and APE, must be part of the same network security group. 
  2. Define ports in the network security group.
  3. Modify port rules for the ports used by your SolarWinds products.

For your server ports and firewall, open ports according to the port and feature requirements. Orion uses these ports to send and receive data, issue management commands, and perform additional actions depending on the features. For example, SolarWinds High Availability has additional port requirements beyond product needs.

For more information, see Window Azure's help.

If you set a public IP address, you may want to use stricter security settings, including strong passwords.

Prepare the servers

Prepare server instances as needed for your Orion Platform products and deployment:

Any server instance in the cloud must be part of the same security group.

  • Orion server: based on your product deployment size and system requirements.
  • Orion SQL server: based on your product deployment size and system requirements.
  • Primary and Secondary servers for SolarWinds High Availability: review the HA requirements.
  • Additional Polling Engine servers and additional web servers: see the SolarWinds Scalability Guidelines.
  • Additional database server: see requirements for additional databases. Some products have additional needs.
Run all Windows updates

Before installation, check for and run all Microsoft Windows Updates on all servers. If a Windows update automatically launches during installation, your system may restart if required by the update. The installation may not complete if your system is waiting to restart.

Check for antivirus software

Determine if any antivirus software is installed on the server or servers where you plan to install. To ensure the installation goes smoothly, exclude the SolarWinds directory. For example, on Windows Server 2012 R2, exclude C:\ProgramData\SolarWinds\. For a full list of antivirus exclusions, see Files and directories to exclude from antivirus scanning.

SolarWinds assumes that C:\ is the default volume.

Verify connectivity

Ensure that you can connect to your nodes from your cloud instance and vice versa. Polling Engines and Additional Web Servers must be able to connect to the database server.

Task 5: Install the Orion Platform on Azure VM instances

Use the SolarWinds Orion Installer to upgrade and install Orion Platform products.

What you should know:

  • If you have products out of maintenance, the Orion Installer will provide the latest possible upgrades for your products. Information and a link will display warning you of the issues that can occur. Having even one product out of maintenance can restrict the upgrade options for products currently under maintenance. For example, if you have IPAM out of maintenance and want the latest NPM upgrade, you may not be able to upgrade until IPAM is also upgraded due to compatibility.
    Recommendation: Renew. SolarWinds highly recommends renewing your maintenanceto receive the latest upgrades and installs for all products.
  • The Orion Installer will alert you to warning or critical level requirements issues during the System Check.
    Recommendation: Verify product requirements before you get started. View the checklist at the beginning of this guide for links to help.

Step 1: Create an Azure VM instance for your Orion Platform server

  1. Sign in to your Azure VM console and launch a virtual machine according to your recommended deployment size.
  2. Choose your instance type.
  3. Select the Resource Group that contains all of your Orion servers.

Use this instance to deploy your Orion servers in the cloud.

Step 2: Create a database server in Azure

You can either use the Azure SQL Database, Azure SQL Database managed instance, or create an Azure VM instance and deploy a supported version of the MS SQL Server there.

When you finish creating the database server, make sure that the database is able to communicate with the Orion Server.

Create Azure SQL Database server

Follow these steps if you are using Azure SQL Database as the Orion database.

  1. Sign in to your Azure VM console and create a SQL Server.
  2. Configure your SQL Server.
  3. Create an Azure SQL Database for the Orion database.

Create Azure SQL Database managed instance

Follow these steps if you are using Azure SQL Database managed instance as the Orion database.

  1. Sign in to your Azure VM console and create a managed instance.
  2. Ensure connectivity between the Azure SQL Database managed instance and your Orion server.

Create a VM instance with SQL

Follow these steps if you are hosting your Orion database server in the cloud.

  1. Sign in to your Azure VM console and launch an instance according to your recommended deployment size.
  2. Choose your instance type.
  3. Select the Security Group that contains all of your Orion servers.

The SQL server must use the same timezone as your main Orion server.

Step 3. Install the Orion server

Installation step 1. Run the Installer and select products to install

Starting with Orion Platform 2019.4, you can deploy Orion Platform products using Azure Marketplace. In Azure Marketplace, search for the product to install and complete the wizard.

  1. Save and run installer.exe on the server dedicated to your main Orion server.
  2. A welcome screen displays a list of products to install. The installer walks you through upgrading and installing in one process.
  3. Select the product(s) you want to install using the SolarWinds Orion Installer.
  4. (Optional) Select to Send usage metrics to help SolarWinds improve products. SolarWinds only receives data collected during the installation and upgrade process.
  5. Click Next.

Installation step 2. Create the additional database (optional)

Follow this step if you are deploying the NTA Flow Storage database or the Log Analyzer database in Azure.

Create another Azure SQL database or deploy another VM and deploy the NTA Flow Storage database on it.

If you are not hosting your NTA Flow Storage or Log Analyzer database in the cloud, run the appropriate installer on a physical server. Install the additional database and the Orion database on separate SQL server instances.

Installation step 3. Review the System Check

A series of system checks run per product to verify if your server meets recommended system requirements. These checks include:

  • Hardware resources, including RAM, hard drive space, and number of CPUs.
  • Software installed, including the Operating System version, .NET, and other required tools.
  • Ports for data access and tasks.
  • Specific checks for product configurations and additional requirements.

If your environment does not meet specifications, the installer provides:

  • Warning message: does not block the installation. Details provide recommended actions and best practices to update your environment for better performance.
  • Critical issue: blocks the installation until resolved. Details provide required updates for your environment to support the products. After addressing the issues, run the installer again.

For more information, select Click for more details. Click Save Install Report to save a list of issues to resolve. You can also click Copy the issue to clipboard to paste the details in a text file.

The following is an example of a report.

Installation step 4. Review the EULA agreement

The EULA is displayed for you to review and accept. If you agree with the license agreement, click the accept option and click Next.

Installation step 5. Monitor the installation progress

Progress messages are displayed as products are installed. The installer displays any issues, halting the installation to allow you to review and fix. The installer may run multiple product installations prior to running the Configuration wizard. Installations requiring the configuration opens the wizard and walks you through the installation steps.

You can always run the SolarWinds Orion Installer again to check for updates.

If a reboot is required as part of the installation, the installer will prompt you. You cannot continue the installation until you have restarted the computer.

Installation step 6. Complete the Configuration wizard

When the installation completes, the Configuration wizard opens. Depending on your product, the wizard may include additional options and screens.

  1. In the welcome dialog box, click Next.
  2. If prompted to stop services, click Yes.
  3. If you performed a Standard installation with an existing SQL database, select one of the following for authentication:
    • Authenticate as currently logged in user: pass through authentication to the SQL server using the account currently logged in for installing the Orion platform product.
    • Switch user: provide separate SQL, Windows, or Azure AD credentials.

    Unless you have joined your on-premise and cloud domains, you must use a dedicated SQL Server account. Windows authentication may not work as expected in the cloud.


  4. In the Database Settings dialog box, create a new database in your SQL server.

    SolarWinds recommends that your main Orion server and your SQL server are both hosted on-premise or in the cloud to prevent alerting loss or other undesirable behaviors in case of network connectivity issues.

  5. In the Database Account dialog box, create an account or use an existing account that the polling engine and Orion Web Console use to access the database. You can use a SQL user account, a Windows, Active Directory, or Azure AD account. Please note that if the account is covered by a password expiration policy and the password expires, Orion Platform stops working.
  6. In the Website Settings dialog box, complete selections for your installation:
    1. Select All Unassigned unless your environment requires a specific IP address for the Orion Web Console. The Port is 80 by default.
    2. Specify the Port and the Website Root Directory where the system installs the Web Console files.

      If you specify any port other than 80, include that port in the URL used to access the Web Console.

    3. To configure SSL, click Enable HTTPS and select your SSL certificate.

      You must install your SSL certificate on the server before running the Configuration wizard. You can install the certificate and run the Configuration wizard again.
      If a certificate is not available, select the option to Generate Self-Signed Certificate. The Configuration wizard automatically generates a self-signed certificate issued to the hostname or FQDN and adds it to the trusted certificate store.

  7. If prompted to create a directory or website, click Yes.
  8. Review the list of services to install, click Next.
  9. Click Yes if prompted to disable the SNMP Trap Service and enable the SolarWinds Trap Service.
  10. In the Completing the Orion Configuration wizard dialog box, click Next.
  11. When completed, click Finish to launch the Orion Web Console.

    Click Start > All Programs > SolarWinds > Orion Web Console


    Open a web browser on your Orion server and enter http://ipAddress or http://hostname, where ipAddress is the IP address of your server and hostname is the host name of your server.

    SolarWinds recommends using a public DNS name or IPv4 address.

  12. Log in with user name admin and leave the password field blank.

    For security purposes, SolarWinds recommends that you change the password to your admin account.

Task 6: Deploy Azure Active Directory app

The Azure Active Directory is an access point that allows an external application or service, such as the Orion Platform, to connect to the Azure Portal. The Azure AD app must be configured to allow read-access to the Orion Platform for polling of VM status and metrics. See Integrating applications with Azure Active Directory for more information.

Step 1: Register a new application

  1. Log into the Azure Portal.
  2. Click Azure Active Directory > App Registrations > New application registration.
  3. In the Create pane, enter a Name for the AD app.

    Use a recognizable name, such as Orion, SAM, or SolarWinds.

  4. Select Web app/API as the Application type.
  5. Enter a properly formatted URL, such as
  6. Click Create to display the AD app in the App registration pane.

Step 2: Record Application ID

  1. Click the Display Name of the new AD app to display registration details.
  2. Record the Application ID for use as the Client / Application ID in the Orion Web Console.

Step 3: Generate an Application Secret Key

The Application Key is used when adding an Azure account to the Orion Platform.

  1. Click All settings > Keys, to open the Keys pane.
  2. Enter a Description of the key.
  3. For the Duration, select Never expires.
  4. Click Save to display data in the Value field. The value that appears is the Application Secret Key.

Task 7: Configure Azure IAM Permissions

You next need to configure Identity and Access Management (IAM) permissions to integrate the Azure Active Directory app with the Orion Platform. Your account must be assigned to the User Access Administrator role to manage account permissions and perform actions, such as stopping polling.

To configure your IAM permissions, see Configure Azure IAM permissions for cloud monitoring in the Orion Platform.

Role-based Access Control (RBAC) may be customized for your organization and can affect how the Orion Platform works with Azure.

Task 8: Deploy Orion agents in the cloud (optional)

If you are deploying Orion agents from the cloud to on-premise devices, follow the manual deployment steps. Otherwise, complete the steps below to deploy agents in the cloud.

Step 1: Review agent requirements

SolarWinds Orion agent requirements.

Step 2: Update network security groups ports

Update ports based on the agent communication type.

Agent-initiated communication

  • The monitored device must be able to reach the Orion server using the IP address.
  • Port 17778 must be open on the Orion server or APE.

Server-initiated communication

  • The Orion server must be able to reach the monitored device using the IP address.
  • Port 17790 must be open on the monitored device.
  • Open port 22 on Linux-based devices to install the agent.
  • Open ports 135 and 445 on Windows devices to install the agent.

Step 3: Deploy the agent on Azure

You have the following options:

  • Manually deploy an agent on Azure
  • Automatically deploy an agent to established instances on Azure

Manually deploy an agent on Azure

You can manually deploy agents to a virtual machine using Remote Desktop Connection in two ways.

Deploy through the command prompt

  1. Click Settings > All Settings in the menu bar.
  2. Under Product Specific Settings, click Agent Settings > Download Agent Software.
  3. Click Windows, and click Next.
  4. Click Mass Deploy to Multiple Machines, and click Next.
  5. Download the MSI and MST files.
  6. Run a command prompt as administrator from the context menu.
  7. Enter the following command:

    msiexec /i "SolarWinds-Agent.msi" TRANSFORMS="SolarWinds-Agent.mst"

Deploy the agent using the interactive wizard

  1. Click Settings > All Settings in the menu bar.
  2. Under Product Specific Settings, click Agent Settings > Download Agent Software.
  3. Click Windows, and click Next.
  4. Click Install Manually, and click Next.
  5. Click Download MSI.
  6. Copy the MSI file to the client machine, and run it.
  7. In the Installation wizard, select Agent Initiated Communication or Orion Server Initiated Communication.
  8. Enter the Orion server IP address or hostname, and the SolarWinds Orion administrator account credentials.
  9. Optional: For Server-initiated communication (passive), in the Orion Web Console:
    1. Click Settings > All Settings.
    2. Under Node & Group Management, click Manage Agents > Add Agent.
    3. Click Connect to a previously installed agent > click Next.
    4. Enter the name, IP address, and port number for the agent and click Server-initiated communication.

Automatically deploy an agent to established instances on Azure (Optional)

  1. Click Settings > All Settings in the menu bar.
  2. Under Product Specific Settings, click Agent Settings > Download Agent Software.
  3. Click Windows, and click Next.
  4. Click Mass Deploy to Multiple Machines, and click Next.
  5. Download the MSI and MST files.
  6. Log in to your Windows Azure account.
  7. Create a bucket and upload the MSI and MST files.

    Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

  8. Create a PowerShell script to run on each virtual machine when it is launched for the first time, downloading and executing the MST and MSI files on each virtual machine where you want to install the agent.
  9. Log in to your Azure account.

    You can perform the following steps through the API or Azure CLI command line interface.

  10. Create an instance, and paste your PowerShell script under Advanced Details in the User Data text box. Select the As Text option.
  11. For instances that are already created, take the following steps:
    1. Stop the instance where you want to deploy the agent.
    2. Right-click the instance and click Instance Settings > View/Change User Data.
    3. Paste your PowerShell script in the text box as Plain Text.
  12. Optional: For Server-initiated communication (passive), in the Orion Web Console:
    1. Click Settings > All Settings.
    2. Under Node & Group Management > Manage Agents > Select Add Agent.
    3. Click Connect to a previously installed agent > Click Next.
    4. Enter the name, IP address, secret, and port number for the agent and click Server-initiated communication.

Task 9: Install an Additional Polling Engine or additional web server (optional)

If you have Additional Polling Engines (APE) or an additional web servers (AWS), the final installation screen reminds you of those installations. SolarWinds recommends using the Scalability Engine Installer.

Step 1: Create an VM instance for your APE or SolarWinds AWS

  1. Sign in to your Azure VM console and launch an instance according to your recommended deployment size.
  2. Choose your instance type.
  3. Select the Security Group that will contain all of your Orion servers.

Step 2: Ensure your APE or SolarWinds AWS can communicate with your main Orion server

If the DNS does not resolve the host names in Azure's VM, update your hosts file.

  1. On your main Orion server, add your APE or SolarWinds AWS information to your hosts file.
  2. On your APE or SolarWinds AWS, add your main Orion server to your hosts file.

See Unable to resolve primary Orion server name for detailed troubleshooting instructions.

Step 3: Install APE and SolarWinds AWS

  1. Log in to the cloud instance for your Additional Polling Engine.
  2. Download this installer through the Orion Web Console.
    • For the APE installer, click Settings > All Settings > Polling Engines.
    • For the AWS installer, click Settings > All Settings > Web Console Settings.
  3. Run the installer on your APE or AWS.
  4. Repeat installing on all Additional Polling Engines and web servers in your environment.

Task 10: Enable High Availability (optional)

  1. Create an Azure Virtual Network.

    Azure does not support the use of a virtual IP address. As a result, Orion High Availability cannot be deployed in Azure if both members of the same HA pool also reside in the same subnet. Each member of an HA pool must be deployed into a different subnet. A virtual hostname (using, for example, Azure DNS) can be used to direct users to the active member of the HA pool. See Azure's help for more information.

  2. Create or update network security groups.
    1. Open port 5671 (TCP) on the primary and standby servers.

    2. Open ports 4369 and 25672 (TCP) on the main Orion server and its standby server. These ports are not required when protecting Additional Polling Engines.
  3. Create a primary server.
  4. Create a secondary server.
    SolarWinds recommends that your standby server has similar specifications as the primary server.
  5. Download and install the secondary server software.
  6. Create your HA pool using a virtual hostname.

    Do not use a Virtual IP (VIP) address when enabling High Availability in the cloud. Instead, you must use a virtual hostname.

  7. Activate your HA pool licenses.


If you receive errors, try the following:

  • A timeout and error message when attempting to add or view an Azure instance is likely the result of adding two or more virtual machines with the same name, even if they are assigned to different resource groups. The auto-monitoring polling logic expects a unique machine name for each instance in Azure. To resolve, upgrade to SAM 6.6.1 on Orion Platform 2018.2. See this article for full details.
  • If you cannot connect to the main Orion server from your APE or SolarWinds AWS, check that the hosts file includes the main Orion server.
  • If you experience issues and are not on the latest product versions, SolarWinds recommends completing a full upgrade. Use the Orion Installer to create the upgrade path. Many of these updates solve issues you may experience part way through your upgrade.
  • Check our Success Center for troubleshooting. SolarWinds recommends searching on the name of the product, the version number, any error codes or messages displayed, and the general issue you found.
  • Check your Customer Portal for any new hotfixes.
  • If you receive (500) internal server error after an upgrade, use the Orion permission checker to make sure your Group Policy is not locked. See this article for full details.
  • If your views do not load when first opening the console, run the Configuration wizard again.

If an issue occurs you need additional help with, contact Support. SolarWinds recommends gathering diagnostics, a screenshot of the issue, and any error codes you receive. Attach and add this information to your ticket. You may also want to gather additional diagnostics on your additional polling engines and web servers.