• Article

ASP.NET 2.0 is not enabled

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at https://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2010-04-01

For computers that are running Microsoft Exchange Server 2007, the Microsoft Exchange Best Practices Analyzer examines the components that are installed on the following Internet Information Services (IIS) virtual directories:

  • Autodiscover

  • EWS

  • Microsoft-Server-ActiveSync

  • owa

  • UnifiedMessaging

The Best Practices Analyzer examines the IIS metabase for these virtual directories to determine whether ASP.NET 2.0 is enabled. The tool reads the metabase property that is named ScriptMaps to determine whether Aspnet_isapi DLL version 2.0.50727 is enabled on the particular virtual directory. If the Best Practices Analyzer detects that ASP.NET 2.0 is not enabled on one or more of the virtual directories, the tool generates the following error message:

ASP.NET 2.0 is not enabled for virtual directory '<VirtualDirectoryName>' on server '<ServerName>'. The virtual directory will not function properly without ASP.NET 2.0. Please enable ASP.NET 2.0 for this virtual directory.

Exchange uses the Web applications in the Exchange-related virtual directories to provide services to Web-based clients. For example, Exchange 2007 uses the /owa virtual directory to give Web-based users access to Exchange mailboxes.

If ASP.NET 2.0 is not enabled on a particular virtual directory, the Web application does not function correctly. Therefore, Web-based users cannot access Exchange.

To address this issue, enable ASP.NET 2.0 for the appropriate virtual directories.

To enable ASP.NET 2.0 on a virtual directory

  1. On the Exchange server, start a command prompt.

  2. At the command prompt, move to one of the following ASP.NET 2.0 installation directories, as appropriate for the operating system:

    For a 32-bit version of Windows

    %WINDIR%\Microsoft.NET\Framework\v2.0.50727

    For a 64-bit version of Windows

    %WINDIR%\Microsoft.NET\Framework64\v2.0.50727

  3. To obtain a list of ASP.NET 2.0 registration options, run the following command:

    aspnet_regiis.exe -?

  4. To register ASP.NET 2.0 on a particular virtual directory, run the following command:

    aspnet_regiis.exe -s W3SVC/1/ROOT/<virtualdirectoryname>

  5. If ASP.NET is not enabled on a number of virtual directories or if you experience other issues with ASP.NET, you may want to remove, and then re-register it. To do this, follow these steps:

    1. At the command prompt, run the following command:

      aspnet_regiis.exe -ua

    2. At the command prompt, run the following command:

      aspnet_regiis.exe -i -enable

For More Information

For more information about how to switch between the 32-bit versions of ASP.NET and the 64-bit version of ASP.NET, see Microsoft Knowledge Base article 894435, How to switch between the 32-bit versions of ASP.NET 1.1 and the 64-bit version of ASP.NET 2.0 on a 64-bit version of Windows.