Scalable hosting mode sites are inaccessible after you detach and reattach an upgraded Windows SharePoint Services 3.0 content database

Consider the following scenario. You configure a Microsoft Windows SharePoint Services 2.0 farm environment in scalable hosting mode. To do this, you run the following command at the command prompt: You create new site collections, and you associate the new site collections with host headers (-hh). Then, you upgrade the Windows SharePoint Services 2.0 farm environment to Microsoft Windows SharePoint Services 3.0.

In this scenario, you cannot access any of the scalable hosting sites if you detach and then reattach the content database that was upgraded to Windows SharePoint Services 3.0.

This issue occurs if the upgraded content database contained scalable hosting mode sites. In this case, the HostHeader column in the content database sites table may contain a NULL value instead of the URL of the host header.

When the content database is attached to the Web application, the scalable hosted sites that contain NULL values in the HostHeader column are inaccessible.

To resolve this problem, obtain the latest service pack for Windows SharePoint Service 3.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

This problem was first corrected in Microsoft Windows SharePoint Services 3.0 Service Pack 1.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.