Fresh Content on SharePointJoel.com SharePoint Ads
Subscribe in a reader
Did you create your WSS farm with the -hh option in WSS 2.0 now trying to upgrade? (not the default configuration)
If so, this KB will help you understand a common issue with database attach upgrades in relation to host header WSS deployments. First be aware that host header WSS 2.0 deployments don't support gradual or in place upgrade.
Scalable hosting mode sites are inaccessible after you detach and reattach an upgraded Microsoft Windows SharePoint Services 3.0 content database: http://support.microsoft.com/kb/928305
The problem manifests itself when after you attach and the database appears to have upgraded, but you have 0 sites in the content database via central admin.
Thanks a lot for this.
This "First be aware that host header WSS 2.0 deployments don't support gradual or in place upgrade." was a much clearer explanation than that given in the KB article (which I have read earlier without realising it meant this simple fact).
Mike Walsh