Richard Marr's Blog

In my earlier blog  “ 502.3 Bad Gateway “The operation timed out” with IIS Application Request Routing(ARR) “    I referenced links for gathering Winhttp tracing for troubleshooting 502.3 issues.

I had a recent question about the ARR health check features which resulted  in this overview. Hopefully this is helpful to those of you setting up new ARR deployments.

When working with ARR deployments one of the errors you might see is  502.3  Bad Gateway. The 502.3 means while acting as a proxy ARR was unable to complete the request to the upstream server and subsequently send a response back to the client. This can happen for multiple reasons including , failure to connect to the server , no response from the server, or server took too long to respond (time out). 

I was recently working with a colleague to troubleshoot an issue using Application Request Routing (ARR) and wanted to use the trace areas provided by ARR to see the events this logged.

One of the challenges of troubleshooting SQL installations with WebPI is that sometimes the details passed back to Webpi do not provide enough information to tell you how to resolve the issue. This is not the fault of WebPi or the SQL installer, but due to the fact that not all of the errors are exposed  to the external process(WebPI) therefore all we can report is that something failed.   When this occurs you need to examine the SQL logs manually to find the details for the installation failure. In this blog we will help identify some of the common failures and provide the resolutions for each.

In the following walkthrough we will step through the installation of Acquia Drupal using the Web Platform Installer.