Hide this message
Welcome to the NEW Success Center. Search all resources (documentation, videos, training, knowledge base articles) or browse resources by product. If you are unable to find what you are looking for, please contact us at email@example.com
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.
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
<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.
Assuming all 64-bit applications on a SolarWinds host correctly declare their bitness, the Configuration Wizard should complete successfully