Alexander’s Blog

Recently, I was installing Microsoft Office SharePoint Server 2007 Beta 2 on Windows Server 2003 running on my Virtual PC. I installed .NET Framework 2.0, Internet Information Services (IIS) 6.0, Windows Workflow Foundation Beta 2 and then added the ASP.NET 2.0 service extension in IIS 6.0. When I ran the setup.exe I received the following error “This product requires ASP.Net web service extensions to be enabled in Internet Information Services (IIS). Enable this setting and re-run setup.”

I verified that the ASP.NET 2.0 extension was enabled but still received the same error. The .NET Framework 2.0 didn’t give me the option to repair in Add or Remove Programs in Control Panel (similar to the one that’s available for Workflow Foundation shown below).

I knew that the ASP.NET was not properly registered because the General tab showed that the extension was not used by the ASP.NET v2.0.50727 as expected, instead it showed “unknown”, as shown in the following screen shot.

Rather than reinstalling the .NET Framework, I decided to register ASP.NET by using the following command at the command prompt. I made sure that I was in the folder where aspnet_regiis was located.

aspnet_regiis -i

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -i
Start installing ASP.NET (2.0.50727).
……………………………..
Finished installing ASP.NET (2.0.50727).

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>

When I ran the SharePoint Server setup it failed again. I ran “aspnet_regiis -i” one more time, restarted the IIS Admin service and noticed that the ASP.NET was now being used by v2.0.50727. I ran the SharePoint Server setup again and it finally worked. If you’ve run into a similar situation, hopefully this will help solve your problem.

The following information is posted in Microsoft’s KB article 918005.

When you unplug the AC power from a Microsoft Windows XP-based portable computer, the battery may drain more quickly than you expect. Therefore, the operating system may shut down prematurely.

This problem may occur if one of the following conditions is true:

1. The portable computer cannot enter the deeper Advanced Configuration and Power Interface (ACPI) processor idle sleep states.

This occurs when the USB 2.0 driver leaves the asynchronous scheduler component running continuously. This prevents the processor from entering the deeper ACPI processor idle sleep states, or C-states. C-states save power when the processor is not busy. These states range from C0 to C3 or C4. Typically, an idle portable computer uses the C3 and C4 states to preserve battery power. If an idle portable computer cannot enter or maintain the C3 or C4 states, the battery power drains more quickly. This problem is fixed by installing the download that is available in this article.

2. The USB host controller is unable to turn off.

This typically occurs when devices are removed from a nested USB hub that is attached to the host controller. The host controller does not recognize the device removal. Therefore, the controller is never turned off. This prevents the processor from entering the ACPI processor idle sleep states. This problem is not fixed by installing the download that is available in this article.

3. The USB host controller uses the periodic scheduler for USB 2.0 devices.

This typically occurs when devices that rely on the periodic scheduler are attached to the host controller. These may be isochronous (Isoch) devices such as audio devices. Alternatively, they may be interrupt devices such as mouse or keyboard. This problem is not fixed by installing the download that is available in this article.

To solve this known problem, download an update for Windows XP (KB918005) here.