Installing and Configuring ASP.NET

In Microsoft Windows SharePoint Services Service Pack 2 (SP2), Microsoft ASP.NET 2.0 is supported. This topic describes how to install and configure ASP.NET 2.0 and ASP.NET 1.1 for Windows SharePoint Services.

Windows SharePoint Services SP2 does not use the extended capabilities of ASP.NET 2.0. However, because ASP.NET 2.0 is fully backward compatible with ASP.NET 1.1, the same features and functionality are supported without the need to update or recompile any applications.

 Note   ASP.NET 2.0 is part of Microsoft .NET Framework 2.0.

The following table describes the versions of ASP.NET that are included and available for Microsoft Windows Server 2003 operating systems and Microsoft Windows Server 2003 R2 operating systems.

Included * Available as download
Windows Server 2003 ASP.NET 1.1 ASP.NET 2.0
Windows Server 2003 R2 32-bit versions ASP.NET 1.1
ASP.NET 2.0
N/A
Windows Server 2003 R2 x64-based versions ASP.NET 2.0 ASP.NET 1.1

* You must manually enable ASP.NET on Windows Server 2003 and Windows Server 2003 R2.

Windows SharePoint Services Service Pack 2 allows running ASP.NET 1.1 and 2.0 on different virtual servers on the same Web server simultaneously. You can accomplish this by configuring each virtual server extended with Windows SharePoint Services to use the version of ASP.NET that you want for a particular virtual server. Note that virtual servers running different versions of ASP.NET must be running under different application pools.

 Notes 

  • When you enable IIS, you have the option to also enable ASP.NET 1.1, which also configures ASP.NET 1.1 as the default Web service extension for all virtual servers. However, installing, enabling, and configuring ASP.NET 2.0 requires additional steps, which are detailed later in this topic.
  • It is not necessary to enable ASP.NET 1.1 to use only ASP.NET 2.0 with Windows SharePoint Services Service Pack 2.
  • You must be logged on to the server either as a local administrator or a member of the Domain Administrators Group to perform the procedures described in this topic.
  • To perform the procedures in this topic Internet Information Server (IIS) must already be enabled. For more information about enabling IIS, see Preparing Front-End Web Servers for Windows SharePoint Services.

Verifying the currently enabled and allowed versions of ASP.NET

Before you decide to install a particular version of ASP.NET, it is a good idea to first verify which version or versions are currently enabled and allowed in the Web service extensions, in IIS.

ASP.NET is not enabled on Windows Server 2003 or Windows Server 2003 R2 by default. However, if you selected the ASP.NET check-box when enabling IIS, ASP.NET 1.1 should appear in the web service extensions list in IIS. If you installed Microsoft SQL Server 2005 on the same computer as IIS, then ASP.NET 2.0 may also appear in the web service extensions list.

After IIS is installed, you can use the following procedure to verify which version or versions of ASP.NET are currently enabled and allowed as a web service extension in IIS.

Verify the currently enabled and allowed versions of ASP.NET
  1. On each front-end Web server, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. In the left-hand pane, click the plus sign (+) next to the local computer and then click the Web Service Extensions node.

All versions of ASP.NET that are currently enabled appear in the Web Service Extension column.

  1. The Status column displays whether the version or versions of ASP.NET (that are currently enabled) are allowed or disallowed as a web service extension in IIS. You can change this status by right-clicking the version of ASP.NET you want to change and then click either Prohibit or Allow.

If the version of ASP.NET that you want to use does not appear in the Web Service Extensions list, you can install and enable it by using the following procedures. Note that the process for enabling ASP.NET 2.0 differs between Windows Server 2003 and Windows Server 2003 R2.

Installing ASP.NET 2.0 on Windows Server 2003

As described earlier, Windows Server 2003, prior to R2 includes ASP.NET 1.1. If you selected the ASP.NET check-box when enabling IIS, ASP.NET 1.1 is enabled as the default web service extension. Note, however, that ASP.NET 2.0 is not included with Windows Server 2003. Use the following procedures to install ASP.NET 2.0 and verify that it is allowed in the web service extensions.

Install ASP.NET 2.0 on Windows Server 2003
  • Download and install the .NET Framework Version 2.0 Redistributable Package from the Microsoft Download Center on each front-end Web server.

After successfully installing ASP.NET 2.0 on Windows Server 2003, the next step is to verify that ASP.NET 2.0 is allowed in the web service extensions in IIS.

Verify ASP.NET 2.0 is allowed in the web service extensions
  1. On each front-end Web server, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. In the left-hand pane, click the plus sign (+) next to the local computer and then click the Web Service Extensions node.

All versions of ASP.NET that are currently enabled appear in the Web Server Extension column.

  1. Verify that ASP.NET v2.0.nnnnn appears in the Web Service Extension column and that the status is Allowed.

nnnnn is the minor version number.

 Note   The Status column displays whether the version or versions of ASP.NET (that are currently enabled) are allowed or disallowed as a web service extension in IIS. You can change this status by right-clicking the version of ASP.NET you want to change and then click either Prohibit or Allow.

  1. If ASP.NET v2.0.nnnnn is listed and allowed in the web service extensions, proceed to Specifying which virtual servers use ASP.NET 2.0. Otherwise, you must first perform the following procedure to enable ASP.NET 2.0 in the web service extensions.
Enable ASP.NET 2.0 in the web service extensions

This procedure enables ASP.NET 2.0 in the Web service extensions without changing the configuration of the virtual servers. You will specify which virtual servers you want to use ASP.NET 2.0 with in a later procedure.

 Note   These steps are only necessary if ASP.NET 2.0.nnnnn does not already appear in the web service extensions.

  1. Click Start, and then click Run.
  2. In the Open box, type cmd and then click OK.
  3. Open the following directory:

%drive%\WINNT\Microsoft.NET\Framework\v2.0.nnnnn

where %drive% is the drive letter on which you installed Windows Server 2003 and nnnnn is the least significant version number of ASP.NET 2.0.

 Note   If you are running a 64-bit edition of Windows Server 2003 do not open the 64-bit directory. Windows SharePoint Services requires that IIS be run in 32-bit mode.

  1. Run the following command at the command prompt:

aspnet_regiis.exe -iru -enable

  1. Close the command prompt.
  2. In Internet Information Services (IIS) Manager click Refresh from the Action menu.
  3. Verify that ASP.NET v2.0.nnnnn is listed in the Web Service Extension column and that the status is Allowed. If the status is Prohibited, you can change the status by right-clicking ASP.NET v2.0.nnnnn and then clicking Allow.
  4. After verifying that ASP.NET is allowed, the next step is to specify which virtual server or virtual servers you want to use ASP.NET 2.0. Proceed to Specifying which virtual servers use ASP.NET 2.0.

Installing ASP.NET 2.0 for Windows Server 2003 R2

Windows Server 2003 R2 includes ASP.NET 2.0 on the CD, but it is not installed by default. To install ASP.NET 2.0 and configure it for Windows SharePoint Services, you must perform the following procedures in the order listed.

Install ASP.NET 2.0 on Windows Server 2003 R2

 Note   To perform this procedure, you will need disk 2 of Windows Server 2003 R2, which is part of the CD set you created after downloading Windows Server 2003 R2.

  1. Click Start, point to Control Panel, and then click Add or Remove Programs.
  2. On the Add or Remove Programs page, click Add/Remove Windows Components in the left-hand pane.
  3. On the Windows Components page, select the check the box next to Microsoft .NET Framework 2.0, and then click Next.

 Note   If you are installing on an international version of Windows Server 2003 R2, you will be prompted a second time to insert Windows Server 2003 Disk 2.

  1. In the Files Needed dialog box, insert Windows Server 2003 Disk 2 into the CD-Rom drive, and then click Next.
  2. When the installation is complete, click Finish.
  3. Close the Add or Remove Programs page.

After successfully installing ASP.NET 2.0 on Windows Server 2003 R2, the next step is to verify that ASP.NET 2.0 is allowed in the web service extensions in IIS.

Verify that ASP.NET 2.0 is allowed
  1. On each front-end Web server, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. In the left-hand pane, click the plus sign (+) next to the local computer and then click the Web Service Extensions node.

All versions of ASP.NET that are currently enabled appear in the Web Server Extension column.

  1. Verify that ASP.NET v2.0.nnnnn appears in the Web Service Extension column and that the status is Allowed.

Where nnnnn is the minor version number.

The Status column displays whether the version or versions of ASP.NET (that are currently enabled) are allowed or disallowed as a web service extension in IIS. You can change this status by right-clicking the version of ASP.NET you want to change and then click either Prohibit or Allow.

  1. If ASP.NET v2.0.nnnnn is listed and allowed in the web service extensions, proceed to Specifying which virtual servers use ASP.NET 2.0. Otherwise, you must first perform the following procedure to enable ASP.NET 2.0 in the web service extensions.
Enable ASP.NET 2.0 in the web service extensions

This procedure enables ASP.NET 2.0 in the Web service extensions without changing the configuration of the virtual servers. You will specify which virtual servers you want to use ASP.NET 2.0 in a later procedure.

  1. Click Start, and then click Run.
  2. In the Open box, type cmd and then click OK.
  3. Open the following directory:

%drive%\WINNT\Microsoft.NET\Framework\v2.0.nnnnn

where %drive% is the drive letter on which you installed Windows Server 2003 and nnnnn is the least significant version number of ASP.NET 2.0.

 Note   If you are running a 64-bit edition of Windows Server 2003 do not open the 64-bit directory, because Windows SharePoint Services requires that IIS be run in 32-bit mode.

  1. Run the following command at the command prompt:

aspnet_regiis.exe -iru -enable

  1. Close the command prompt.
  2. In Internet Information Services (IIS) Manager click Refresh from the Action menu.
  3. Verify that ASP.NET v2.0.nnnnn is listed in the Web Service Extension column and that the status is Allowed. If the status is Prohibited, you can change the status by right-clicking ASP.NET v2.0.nnnnn and then clicking Allow.
  4. After verifying that ASP.NET is allowed, the next step is to specify which virtual servers you want to use ASP.NET 2.0. Proceed to Specifying which virtual servers use ASP.NET 2.0.

Specifying which virtual servers use ASP.NET 2.0

On 32-bit versions of Windows Server 2003 or Windows Server 2003 R2, you can specify which virtual servers will use ASP.NET 2.0 by using either Internet Information Services (IIS) Manager or the command line option. On x64-based editions of Windows Server 2003 or Windows Server 2003 R2, however, you can only use the command line option. This is because the ASP.NET tab does not appear on the Web Site Properties pages on x64-based editions.

Additionally, you can either specify that all virtual servers use ASP.NET 2.0 or only the virtual servers you specify. For example, you may want to use ASP.NET 2.0 for virtual servers that are extended with Windows SharePoint Services, and ASP.NET 1.1 for virtual servers that are hosting other applications.

 Important   Virtual servers that are hosting SharePoint Portal Server sites or other applications that may have dependencies on ASP.NET 1.1 must not be upgraded to ASP.NET 2.0. In this case, it is recommended that you specify ASP.NET 2.0 only for the specific virtual servers on which you want to run ASP.NET 2.0.

This section contains:

Specifying ASP.NET 2.0 for all virtual servers

This section describes how to configure all virtual servers to use ASP.NET 2.0, using the command line option. If you prefer to use Internet Information Services (IIS) Manager, you can perform the procedure described in the Specifying ASP.NET 2.0 for specific virtual servers section, separately for each virtual server on which you want to use ASP.NET 2.0.

 Important   Virtual servers that are hosting SharePoint Portal Server sites or other applications that have dependencies on ASP.NET 1.1 must use ASP.NET 1.1, rather than ASP.NET 2.0. In this case, it is recommended that you specify ASP.NET 2.0 only for the specific virtual servers on which you want to run ASP.NET 2.0. To specify ASP.NET 2.0 for specific virtual servers, see Specifying ASP.NET 2.0 for specific virtual servers.

Specify ASP.NET 2.0 for all virtual servers from the command line

Note that after running this procedure, any new virtual servers that are created will use ASP.NET 2.0, by default.

  1. Click Start, and then click Run.
  2. In the Open box, type cmd and then click OK.
  3. Open the following directory:

%drive%\WINNT\Microsoft.NET\Framework\v2.0.nnnnn

where %drive% is the drive letter on which you installed Windows Server 2003 and nnnnn is the least significant version number of ASP.NET 2.0.

 Note   If you are running a 64-bit edition of Windows Server 2003 do not open the 64-bit directory. Windows SharePoint Services requires that IIS be run in 32-bit mode.

  1. To enable ASP.NET 2.0 in the IIS Web Service Extensions and use ASP.NET 2.0 with all virtual servers, run the following command:

Aspnet_regiis.exe –I –enable

  1. If you extended a virtual server with Windows SharePoint Services that was previously using a different version of ASP.NET, you must perform additional steps to configure the Web.config file in Windows SharePoint Services for ASP.NET 2.0. To perform these additional steps, proceed to Configuring ASP.NET 2.0 for Windows SharePoint Services. Otherwise, you have completed all the steps for installing and configuring ASP.NET 2.0.

Specifying ASP.NET 2.0 for specific virtual servers

On 32-bit versions of Windows Server 2003 or Windows Server 2003 R2, you can specify which virtual servers will use ASP.NET 2.0 by using either Internet Information Services (IIS) Manager or the command line option. On x64-based editions of Windows Server 2003 or Windows Server 2003 R2, however, you can only use the command line option. This is because the ASP.NET tab does not appear on the Web Site Properties pages on x64-based editions.

This section contains:

Specify a virtual server to use ASP.NET 2.0 using IIS Manager

 Note   This procedure cannot be performed on x64-based editions of Windows Server 2003 or Windows Server 2003 R2 because the x64-based editions do not have an ASP.NET tab of the Web Site Properties pages. To specify a specific virtual server on which to use ASP.NET 2.0 on an x64-based edition of Windows Server 2003, see Specify a virtual server to use ASP.NET 2.0 using the command line option.

  1. On each front-end Web server, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. In the left-hand pane, click the plus sign (+) next to the local computer.
  3. Click the plus sign (+) next to the Web Sites node.
  4. Right-click the virtual server you want to configure and click Properties.
  5. Click the ASP.NET tab.

The ASP.NET tab does not appear on x64-based editions of Windows Server 2003 and Windows Server 2003 R2. This tab also does not appear if only one version of ASP.NET is allowed in the web service extensions.

  1. On the ASP.NET tab, select 2.0.nnnnn from the ASP.NET version drop-down list.

where nnnnn is the minor version number.

  1. Click Apply, and then click OK.
  2. Repeat steps 4 through 7 for each virtual server you want to configure.
  3. Click Start, and then click Run. In the Open box, type cmd, and then click OK.
  4. At the command prompt, type iisreset, and then press Enter.
  5. After IIS is successfully restarted, type exit and then press Enter, to exit the Command Prompt.
  6. If you extended a virtual server with Windows SharePoint Services that was previously using a different version of ASP.NET, you must perform additional steps to configure the Web.config file in Windows SharePoint Services for ASP.NET 2.0. To perform these additional steps, proceed to Configuring ASP.NET 2.0 for Windows SharePoint Services. Otherwise, you have completed all the steps for installing and configuring ASP.NET 2.0.
Specify a virtual server to use ASP.NET 2.0 by using the command line option
  1. Click Start, and then click Run.
  2. In the Open box, type cmd and then click OK.
  3. Open the following directory:

%drive%\WINNT\Microsoft.NET\Framework\v2.0.nnnnn

where %drive% is the drive letter on which you installed Windows Server 2003 and nnnnn is the least significant version number of ASP.NET 2.0.

 Note   If you are running a 64-bit edition of Windows Server 2003 do not open the 64-bit directory. Windows SharePoint Services requires that IIS be run in 32-bit mode.

  1. To enable ASP.NET 2.0 in the IIS Web Service Extensions and use ASP.NET 2.0 with a specific virtual server, run the following command:

aspnet_regiis.exe –s /w3svc/<identifier>/root

where <identifier> is the IIS virtual server ID. You can find the identifier for all virtual servers by opening Internet Information Server Manager (IIS) and clicking on the Web Sites node. The Identifier for each virtual server is listed in the right-hand pane.

  1. Repeat step 4 for each virtual server on which to use ASP.NET 2.0.
  2. Type iisreset, and then press ENTER.
  3. After IIS is successfully restarted, type exit and then press Enter, to exit the Command Prompt.
  4. If you extended a virtual server with Windows SharePoint Services that was previously using a different version of ASP.NET, you must perform additional steps to configure the Web.config file in Windows SharePoint Services for ASP.NET 2.0. To perform these additional steps, proceed to Configuring ASP.NET 2.0 for Windows SharePoint Services. Otherwise, you have completed all the steps for installing and configuring ASP.NET 2.0.

Configuring ASP.NET 2.0 for Windows SharePoint Services

ASP.NET 2.0 implements a new security change that locks down security for a given IIS virtual server. In previous versions of ASP.NET, code ran with the trust granted to it based on the CAS policy file specified in the Web.config file (for example, wss_minimaltrust.config). The security change in ASP.NET 2.0 restricts the permissions of pages, Web parts, and controls to the intersection of ASP.NET PermissionSet and the trust of the code. Windows SharePoint Services is configured by default to give the ASP.NET PermissionSet very minimal privileges, so when this extra security is enabled, some code runs with reduced privileges. For example, code from assemblies in the global assembly cache (GAC) which previously ran with full trust will now run with minimal privileges. This restriction is incompatible with Windows SharePoint Services and must be disabled in the Web.config file in order for Windows SharePoint Services to function properly.

Use the Windows SharePoint Services stsadm.exe command line utility to automatically update the web.config settings, as described in the following procedure.

Update the web.config settings

 Note   Windows SharePoint Services must be installed in order to perform this procedure.

  1. Click Start, and then click Run.
  2. In the Open box, type cmd and then click OK.
  3. Open the following directory:

%drive%\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN

where %drive% is the drive letter on which you installed Windows Server 2003.

  1. Run the following command:

stsadm.exe –o upgrade –forceupgrade –url http://<url of the virtual server>

 Note   The stsadm.exe upgrade operation updates the Web.config file located at the root of your SharePoint virtual server that you specified. For example, if the default web site is extended with Windows SharePoint Services and you specified the url of the default virtual server, then the Web.config file in the %drive%\inetpub\wwwroot\ folder would be updated, where %drive% is the drive on which you installed Windows Server 2003.

  1. At the command prompt, type iisreset, and then press ENTER.
  2. After the command completes successfully, type exit and then press Enter to exit the Command Prompt.

Installing and Configuring ASP.NET 1.1

This section describes how to install and configure ASP.NET 1.1 on Windows Server 2003 and Windows Server 2003 R2.

If you did not enable ASP.NET 1.1 when you enabled IIS or you uninstalled ASP.NET 1.1, you can use the following procedures to install ASP.NET 1.1, enable it in the web service extensions in IIS, specify which virtual servers on which to use ASP.NET 1.1, and then finally restart IIS to ensure that IIS is aware of your changes.

Installing ASP.NET 1.1

The first step is to download and install ASP.NET 1.1 on each front-end Web server.

Install ASP.NET 1.1

  1. Download the Microsoft ASP.NET Framework Version 1.1 Redistributable Package from the Microsoft Download Center to each front-end Web server.
  2. Using Windows Explorer, open the location of the download and double-click the dotnetfx.exe file to install ASP.NET 1.1.

Verify that ASP.NET 1.1 is allowed

After ASP.NET 1.1 is installed on each front-end Web server, the next step is to verify that it is allowed in the Web Service Extensions. Note that the following procedure, does not change the configuration of your virtual servers. You will specify which virtual servers you want to use with ASP.NET 1.1 in a later procedure.

Enable ASP.NET 1.1 in the IIS Web Service Extensions
  1. On each front-end Web server, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. In the left pane, click the plus sign (+) next to the local computer and then click the Web Service Extensions node.

All versions of ASP.NET that are currently enabled appear in the Web Server Extension column.

  1. Verify that ASP.NET v1.1.nnnnn appears in the Web Service Extension column and that the status is Allowed.

Where nnnnn is the minor version number.

The Status column displays whether the version or versions of ASP.NET (that are currently enabled) are allowed or prohibited as a web service extension in IIS. You can change this status to allow by right-clicking the version of ASP.NET you want to change and then click Allow.

  1. If the status of ASP.NET v1.1.nnnnn is set to Prohibited, then right-click ASP.NET v1.1.nnnnn and then click Allow.

Specifying ASP.NET 1.1 for virtual servers

After you have enabled ASP.NET 1.1 in the web service extensions in IIS, the next step is to specify which virtual servers will use ASP.NET 1.1.

On 32-bit versions of Windows Server 2003 or Windows Server 2003 R2, you can specify which virtual servers will use ASP.NET 1.1 by using either Internet Information Services (IIS) Manager or the command line option. On x64-based editions of Windows Server 2003 or Windows Server 2003 R2, however, you can only use the command line option. This is because the ASP.NET tab does not appear on the Web Site Properties pages on x64-based editions.

This section contains:

Specify virtual servers to use ASP.NET 1.1 using IIS Manager

 Note   This procedure cannot be performed on x64-based editions of Windows Server 2003 or Windows Server 2003 R2 because the x64-based editions do not have an ASP.NET tab of the Web Site Properties pages. To specify a specific virtual server on which to use ASP.NET 1.1 on an x64-based edition of Windows Server 2003, see Specify virtual servers to use ASP.NET 1.1 using the command line option.

  1. On each front-end Web server, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. In the left-hand pane, click the plus sign (+) next to the local computer.
  3. Click the plus sign (+) next to the Web Sites node.
  4. Right-click the virtual server you want to configure and click Properties.
  5. Click the ASP.NET tab.

The ASP.NET tab does not appear on x64-based editions of Windows Server 2003 and Windows Server 2003 R2. This tab also does not appear if only one version of ASP.NET is allowed in the web service extensions.

  1. On the ASP.NET tab, select 1.1.4322.0 from the ASP.NET version drop-down list.
  2. Click Apply, and then click OK.
  3. Repeat steps 4 through 7 for each virtual server you want to configure.
  4. Click Start, and then click Run. In the Open box, type cmd, and then click OK.
  5. At the command prompt, type iisreset, and then press Enter.
  6. After IIS is successfully restarted, type exit and then press Enter, to exit the Command Prompt.
  7. If you extended a virtual server with Windows SharePoint Services that was previously using a different version of ASP.NET, you must perform additional steps to configure the Web.config file in Windows SharePoint Services for ASP.NET 1.1. To perform these additional steps, proceed to Configuring ASP.NET 1.1 for Windows SharePoint Services. Otherwise, you have completed all the steps for installing and configuring ASP.NET 1.1.
Specify virtual servers to use ASP.NET 1.1 using the command line option
  1. Click Start, and then click Run.
  2. In the Open box, type cmd and then click OK.
  3. Open the following directory:

%drive%\WINNT\Microsoft.NET\Framework\v1.1.4322

where %drive% is the drive letter on which you installed Windows Server 2003.

 Note   If you are running a 64-bit edition of Windows Server 2003 do not open the 64-bit directory, because Windows SharePoint Services requires that IIS be run in 32-bit mode.

  1. To enable ASP.NET 1.1 in the IIS Web Service Extensions and use ASP.NET 1.1 with a specific virtual server, run the following command:

aspnet_regiis.exe –s /w3svc/<identifier>/root

where <identifier> is the IIS virtual server ID. You can find the identifier for all virtual servers by opening Internet Information Server Manager (IIS) and clicking on the Web Sites node. The Identifier for each virtual server is listed in the right-hand pane.

  1. Repeat step 4 for each virtual server on which to use ASP.NET 1.1.
  2. Type iisreset, and then press ENTER.
  3. After IIS is successfully restarted, type exit and then press Enter, to exit the Command Prompt.
  4. If you extended a virtual server with Windows SharePoint Services that was previously using a different version of ASP.NET, you must perform additional steps to configure the Web.config file in Windows SharePoint Services for ASP.NET 1.1. To perform these additional steps, proceed to Configuring ASP.NET 1.1 for Windows SharePoint Services. Otherwise, you have completed all the required steps for installing and configuring ASP.NET 1.1.

Configuring ASP.NET 1.1 for Windows SharePoint Services

After specifying a virtual server to use ASP.NET 1.1 that was previously extended with Windows SharePoint Services running ASP.NET 2.0, you must perform the following steps to update the web.config settings.

Update the web.config settings

 Note   Windows SharePoint Services must be installed in order to perform this procedure.

  1. Click Start, and then click Run.
  2. In the Open box, type cmd and then click OK.
  3. Open the following directory:

%drive%\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN

where %drive% is the drive letter on which you installed Windows Server 2003.

  1. Run the following command:

stsadm.exe –o upgrade –forceupgrade –url http://<url of the virtual server>

 Note   The stsadm.exe upgrade operation updates the Web.config file located at the root of the SharePoint virtual server that you specified. For example, if the default web site is extended with Windows SharePoint Services and you specified the url of the default virtual server, then the Web.config file in the %drive%\inetpub\wwwroot\ folder would be updated, where %drive% is the drive on which you installed Windows Server 2003.

  1. At the command prompt, type iisreset, and then press ENTER.
  2. After the command completes successfully, type exit and then press Enter to exit the Command Prompt.

You have completed all the steps for installing and configuring ASP.NET 1.1

Switching between ASP.NET 2.0 and ASP.NET 1.1

After you switch versions of ASP.NET on a particular virtual server that has already been extended with Windows SharePoint Services, you must update the settings in the Web.config file for the virtual server. Failing to do so results in error messages and the Windows SharePoint Services site will be unavailable.

This issue can be resolved by using the stsadm.exe command line utility, as described in the following procedure, after switching between versions of ASP.NET.

Update the web.config settings

 Note   Windows SharePoint Services must be installed in order to perform this procedure.

  1. Click Start, and then click Run.
  2. In the Open box, type cmd and then click OK.
  3. Open the following directory:

%drive%\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN

where %drive% is the drive letter on which you installed Windows Server 2003.

  1. Run the following command:

stsadm.exe –o upgrade –forceupgrade –url http://<url of the virtual server>

 Note   The stsadm.exe upgrade operation updates the Web.config file located at the root of your SharePoint virtual server that you specified. For example, if the default web site is extended with Windows SharePoint Services and you specified the url of the default virtual server, then the Web.config file in the %drive%\inetpub\wwwroot\ folder would be updated, where %drive% is the drive on which you installed Windows Server 2003.

  1. At the command prompt, type iisreset, and then press ENTER.
  2. After the command completes successfully, type exit and then press Enter to exit the Command Prompt.
 
 
Applies to:
Deployment Center 2003