Select the product you need help with

FIX: HTTP error 500 when an application that is published to a nonstandard HTTPS port is accessed the first time in Forefront Unified Access Gateway 2010 Service Pack 2

Article ID: 2810233 - View products that this article applies to.

Symptoms

An application that points to an intranet server is published in Microsoft Forefront Unified Access Gateway (UAG) 2010 Service Pack 2 (SP2). In this case, if a nonstandard HTTPS port is used, you receive an HTTP 500 error message when the application is accessed for the first time.

Note Access to the application is successful when the application is accessed again during the same client session.

Back to the top | Give Feedback

Cause

This problem occurs because, when you connect to Forefront UAG, it stores the original URL that you tried to access before Forefront UAG redirects you through the Forefront UAG logon process. If you access a URL that corresponds to a published web application that is listening on a nonstandard HTTPS port, Forefront UAG cannot translate the internal Protocol:Host:Port combination correctly. This situation occurs in code that is called from StartApp.asp. This code only runs during the first request that a client makes to an application. Therefore, the problem does not occur on successive requests.

Back to the top | Give Feedback