Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

HTTP 404 Error Connecting to ADFS Server


View products that this article applies to.

Symptoms

When you access a Active Directory Federation Services (ADFS) Federation Server or Federation Proxy Server, a HTTP 404 error is returned. No additional information is logged in the event log or in the debug log for the Federation service. If you change the ADFS virtual directory to use ASP.NET version 1.1 a HTTP 500 error is returned instead of a HTTP 404 error.

↑ Back to the top


Cause

The HTTP 404 error is returned if the 2_0_50727 directory is missing under the following location:

%windir%\inetpub\wwwroot\aspnet_client\system_web

By changing the ADFS virtual directory to use ASP.NET version 1.1 the following location is used instead:

%windir%\inetpub\wwwroot\aspnet_client\system_web\1_1_4322

Because ADFS requires ASP.NET 2.0 or higher, a HTTP 500 error will be returned instead of the HTTP 404 error.

↑ Back to the top


Resolution

To resolve this problem, ASP.NET must be registered in IIS. To do this, use the ASP.NET IIS Registration tool. The following syntax will install the version of ASP.NET that is associated with Aspnet_regiis.exe and only register ASP.NET in IIS.

aspnet_regiis -ir

Make sure that you are running this command from the install directory of the version of ASP.NET that needs to be registered in IIS. For example, run aspnet_regiis -ir from %windir%\inetpub\wwwroot\aspnet_client\system_web\2_0_50727 if ASP.NET 2.0 needs to be registered in IIS.

↑ Back to the top


Keywords: KB2002470, kbnomt, kbrapidpub

↑ Back to the top

Article Info
Article ID : 2002470
Revision : 3
Created on : 9/30/2009
Published on : 9/30/2009
Exists online : False
Views : 378