Submit a ticketCall us

WebinarFREE IT Monitoring Webcast

Don’t miss out on our webcast, Essential IT Monitoring with SolarWinds ipMonitor, where we will show you how to keep an eye on your IT environment from one centralized, affordable, and lightweight monitoring tool: SolarWinds® ipMonitor®.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 503 Error after running Configuration Wizard

503 Error after running Configuration Wizard

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,335 Votes: 0 Revisions: 11

Issue:

When installing or upgrading a SolarWinds product on a server that is also hosting Microsoft Exchange (or potentially any other non-SolarWinds 64-bit application), a failure to update IIS website configuration settings triggers a 503 error as the Configuration Wizard attempts to finish its website-related configuration work. The same failed configuration also leads to a dying SolarWinds Application Pool.

Solution:

This issue arises when a non-SolarWinds 64-bit application installed on a SolarWinds host fails to specify that it is a 64-bit application. More specifically, the configuration error occurs if a 64-bit application includes a call to a .dll in the <globalmodules> section of applicationhost.config without specifying precondition="bitness64".</globalmodules>

<globalmodules>The fix is to add the bit-ness precondition to Exchange any other 64-bit application and then restart IIS.</globalmodules>

For more information, see "How to Run a 32bit Web Application on SBS 2008/2011 Standard" at technet.com.

Expected Result

Assuming all 64-bit applications on a SolarWinds host correctly declare their bitness, the Configuration Wizard should complete successfully

Last modified

Tags

Classifications

Public