References > Troubleshooting > Troubleshooting AppInsight for Exchange > Troubleshooting Error Codes in AppInsight for Exchange

Troubleshoot error codes in AppInsight for Exchange

The following error messages are associated with AppInsight for Exchange. Included are possible causes and solutions.

The following log file contains all the information and errors related to the WinRM configuration process: C:\ProgramData\Solarwinds\Logs\APM\RunWinRMConfigurator.log

For information about Microsoft error codes, see: http://msdn.microsoft.com/en-us/library/cc231199.aspx

Deployment service executable not found

Error message: Remote configuration was unsuccessful due to the following: "The deployment service executable was not found on the Orion server." For details, see the log on the Orion server [ALLUSERSPROFILE]\ProgramData\Solarwinds\Logs\APM\RemoteExecutableStarter.log.

Description: Internal error. The Remote Installation Service.exe file was not found. The default file location is C:\Program Files (x86)\SolarWinds\Orion\APM. This can be caused by an incorrect SAM installation or Remote Installation Service.exe was deleted or modified.

Resolution:  Add the Remote Installation Service.exe file to the following folder: C:\Program Files (x86)\SolarWinds\Orion\APM.

Failed to start Windows Remote Management

Error message: Remote configuration was unsuccessful due to the following: "Failed to start Windows Remote Management" For details, see the log on the Orion server [ALLUSERSPROFILE]\ProgramData\Solarwinds\Logs\APM\RemoteExecutableStarter.log.

Resolution:  Start the Windows Remote Management service:

  1. On the target Exchange server, navigate to the Windows Services console and find the Windows Remote Management (WS-Management) service.
  2. Set the Startup type to Automatic.
  3. Start the Windows Remote Management (WS-Management) service.

Unable to access remote admin

Error: Unable to access remote administrator share.

Cause: The remote administrator share cannot be accessed.

Resolution: You can enable this feature manually through the following steps:

  1. Ensure that both computers belong to the same Workgroup.
  2. Specify which user(s) can access the Administrator Shares (Disk Volumes).
  3. Enable File and print sharing through the Windows firewall.
  4. Check to see if you can access the Administrator share from another computer.
  5. When complete, rerun the AppInsight for Exchange Automatic Configuration Wizard.

Configurator exe not found on the Orion server

Error message: Remote configuration was unsuccessful due to the following: "The configurator executable was not found on the Orion server." For details, see the log on the Orion server [ALLUSERSPROFILE]\ProgramData\Solarwinds\Logs\APM\RemoteExecutableStarter.log.

Description: Internal error. SolarWinds.APM.RemoteWinRmConfiguratorFull.exe file was not found. The default file location is C:\Program Files (x86)\SolarWinds\Orion\APM. This can be caused by an incorrect SAM installation or SolarWinds.APM.RemoteWinRmConfiguratorFull.exe was deleted or modified.

Resolution: Add SolarWinds.APM.RemoteWinRmConfiguratorFull.exe to the following folder: C:\Program Files (x86)\SolarWinds\Orion\APM.

Access denied

Error message: Remote configuration was unsuccessful due to the following: "Access denied." For details, see the log on the Orion server [ALLUSERSPROFILE]\ProgramData\Solarwinds\Logs\APM\RemoteExecutableStarter.log)

Description: The provided user account does not have access to the Administrator share on the remote Exchange server.

Resolution: Connect to the Administrator share with \\ExchangeComputerName\<drive letter>$\ from the Orion server.

Configurator exe has an invalid signature

Error message: Remote configuration was unsuccessful due to the following: "The configurator executable has an invalid signature." For details, see the log on the Orion server: [ALLUSERSPROFILE]\ProgramData\Solarwinds\Logs\APM\RemoteExecutableStarter.log.

Description: The configuration executable cannot be started on the remote Exchange server due to any of the following:

  • The high level of User Account Control settings
  • The provided user account does not have privileges high enough to run *.exe files
  • SolarWinds.APM.RemoteWinRmConfiguratorFull.exe is not signed with a Solarwinds certificate.

Resolution:

  • Reduce User Account Control settings on the remote Exchange server;
  • Ensure the user's account has privileges to run *.exe files

Network path not found

Error message: Remote configuration was unsuccessful due to the following: "The network path was not found." For details, see the log on the Orion server: [ALLUSERSPROFILE]\ProgramData\Solarwinds\Logs\APM\RemoteExecutableStarter.log.

Description: This is a Windows error indicating that a networking component is malfunctioning.

Resolution:

  • Ensure you have access to the Shared Storage drive. In Windows Explorer, navigate to My Network Places > Entire Network > Microsoft Windows Network > (workgroup name) > (Shared Storage drive name).
  • Firewalls can block traffic to the network which could generate this message. Try temporarily disabling any software or hardware firewalls to isolate the problem.
  • Anti-spyware tools can block network traffic. Try temporarily disabling any anti-spyware programs and restart the computer to isolate the problem.

PowerShell 2.0 not detected on the Exchange server

Error message: Remote configuration was unsuccessful due to the following: "PowerShell 2.0 was not detected on the Exchange server." Learn how to correct this. For details, see the log on the remote computer. ([ALLUSERSPROFILE]\ProgramData\Solarwinds\Logs\APM\RunWinRMConfigurator.log).

Description: PowerShell 2.0 is not installed on the remote Exchange server.

Resolution: PowerShell 2.0 should be installed on Exchange server.

To install PowerShell 2.0 on Server 2008, download the installation file for PowerShell 2.0 at http://support.microsoft.com/kb/968929/en-us and install it on the server.

PowerShell 2.0 is automatically installed on Server 2008 R2 and therefore no additional installation is required.

To install PowerShell 2.0 on Server 2012, complete the following:

  1. Open Server Manager.
  2. Click on the Manage menu, and the select Add Roles and Features.
  3. After the wizard opens, click Next until you get to the Installation Type page.
  4. Select Role-based or feature-based installation.
  5. Click Next until you reach the Features page.
  6. Scroll down to Windows PowerShell. It likely shows itself as partially installed (square inside box).
  7. Check the box next to Windows PowerShell 2.0 Engine.
  8. Click Next and then Install.
  9. When the installation finishes, click Close.

Account must be an Active Directory account with local admin privileges

Error message: Remote configuration was unsuccessful due to the following: "This account must be an Active Directory account with local administrative privileges." Learn how to correct this. For details, see the log on the remote computer: [ALLUSERSPROFILE]\ProgramData\Solarwinds\Logs\APM\RunWinRMConfigurator.log.

Description: The provided user account does not have Local Administrative privileges.

Resolution: All local administrator privileges to the Active Directory account:

  1. On the server where you wish to grant local administrative privileges, open a Computer Management console.

    On Windows 2012, add this privilege using the Active Directory console.

  2. Navigate to System Tools > Local Users and Groups > Groups and double click the Administrators group.
  3. Click Add and type in the Active Directory user name of the account you want to grant administrative privileges, and then press Enter. Ensure the location is set to either the domain where the account is located or Entire Directory.
  4. Click Apply and then click OK.

    Alternatively, you can add an Active Directory group to the local administrators group and add the Active Directory user accounts to that group.

Account must be an Active Directory account with organization wide Exchange access

Error message: Remote configuration was unsuccessful due to the following: "This account must be an Active Directory account with organization wide Exchange access (View-Only-Organization Management and Mailbox Search Management Role)." Learn how to correct this. For details, see the log on the remote computer: [ALLUSERSPROFILE]\ProgramData\Solarwinds\Logs\APM\RunWinRMConfigurator.log.

Description: The provided user account does not have View-Only-Organization Management or Mailbox Search Management privileges.

Resolution: You need to grant view-only-organization management privileges and mailbox search access to resolve.

Granting Least Privilege access to the Exchange Organization using Active Directory Users and Computers (ADUC):

  1. From the Start Menu, open ADUC and navigate to the Microsoft Exchange Security Groups OU.
  2. Double click on the View-Only Organization Management group.
  3. After the window opens, click the Members tab and then click Add.
  4. Type the user name of the account you want to grant access to the Exchange organization, then click OK.
  5. Click Apply, then click OK.
  6. Close the ADUC window.

Mailbox Search access is required to determine attachment counts and sizes. Grant the access using the Exchange Management Shell (EMS):

  1. From the Start Menu, open the EMS.
  2. Type  New-ManagementRoleAssignment -Role "Mailbox Search" -User <Username of account being granted access> and press Enter.
  3. To verify the management role has been properly assigned, enter the following command:
    Get-ManagementRoleAssignment -RoleAssignee <Username of account>

Error occurred during Exchange Server Configuration

Error message: Remote configuration was unsuccessful due to the following: "An error occurred during Exchange Server Configuration. Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed."

Cause: This is a Windows Limitation when trying to map multiple drives to the same computer using different user accounts.

Resolution:

  1. Open the Computer Manager on the Exchange server
  2. Expand Shared Folders and select Sessions.
  3. Right-click on the users in the list and click Close Session.
  4. Once the session list is empty, retry the Configure Server button in AppInsight for Exchange.

    For more information, see this KB article: AppInsight for Exchange error: Remote configuration failed due to multiple connections

PowerShell web site testing failed: Connecting to remote server

Error message: Remote configuration was unsuccessful due to the following: "WinRM test was successful. PowerShell Exchange web site testing failed with the following error: Connecting to remote server..."

Description: There are no default HTTPS bindings for all unassigned ports, (i.e. “HTTPS 443 *”.)

Resolution:  Establish the missing default HTTPS binding with an Exchange certificate.