I am not very clear about the procedure of upgrading WSS2 to WSS3 by migrating content database to the new farm.In my new web server, I fresh install the WSS3. Then I backup the WSS2 contentdb and restore to new database server. In the WSS3 central admin. page, I createa new web application and set the contentdb to new restored contentdb. Everything look fine but when I try to connect the site collection. It throw 404 error.Please help

I believe you have to create empty web application in wss3.0 use stsadm.exe -o addcontentdb to upgade but this is all described in: http://technet2.microsoft.com/windowsserver/WSS/en/library/700c3d60-f394-4ca9-a6d8-ab597fc3c31b1033.mspx?mfr=true

I found the problem may related to my custom site definition of WSS2.I found this error in the log file. Failed to find <ListTemplate> tag corresponding to ID "105", tried both onet.xml for site definition ID "10001" language "1033" and global site definition. Operation failed. Failed to determine the setup path of the list schema for list template 105. List does not exist The page you selected contains a list that does not exist. It may have been deleted by another user. Cannot get ghost document: 1033\STSKGI\default.aspx Failed to find <ListTemplate> tag corresponding to ID "103", tried both onet.xml for site definition ID "10001" language "1033" and global site definition. Operation failed. Failed to determine the setup path of the list schema for list template 103. Unknown SPRequest error occurred. More information: 0x80070002 Cannot get ghost document: 1033\STSKGI\default.aspx Failed to find <ListTemplate> tag corresponding to ID "101", tried both onet.xml for site definition ID "10001" language "1033" and global site definition. Operation failed. Failed to determine the setup path of the list schema for list template 101. Unknown SPRequest error occurred. More information: 0x80070002 Entering MRU trim routine. Initial table size: 96518 in 35 entries ...I already created a upgrade definition file for that.

Hey all, I recently migrated using the database backup / restore mechanism. Did you remember do perform the prescan.exe? I saw no explicit mention of this, so I wanted to make sure you did complete that process. Once you have the site up and running, you can consolidate the databases.Basically, I've found it easier to backup the site using stsadm -o backup, and then delete the uneccessary database from the web application (the old database), then restore the site using stsadm -o restore. If you want a clean start, you can certainly recreate the web application between the backup and restore process.

Hi, I'm doing a similar migration but in my case the upgrade process doesn't seem to find the upgrade file for my custom site definition so it is applying global template to all the sites. I created the upgrade file and its name starts with the name of the custom site definition. I placed it under 12\config\upgrade folder. I believe there is something wrong in the WebTemplate element, below is what I'm using: <WebTemplate RemoveSiteExternalSecurityProvider="true" ID="25" LocaleId="*" FromSiteDefinitionPath="{LocaleId}\CustomSTS" ToSiteDefinitionPath="SiteTemplates\CustomSTS" FromProductVersion="2" BeginFromSchemaVersion="0" EndFromSchemaVersion="0" ToSchemaVersion="2"> Can anybody please tell if there is something wrong here. Thanks in advance!

You can look at the MpsUpgrade.xml <WebTemplate ID="2" LocaleId="*" FromProductVersion="2" BeginFromSchemaVersion="0" EndFromSchemaVersion="0" ToSchemaVersion="2">The ID should be the same as the site ID in your wss2. In the day of WSS2, MSsuggest we have custom sitetemplate with ID > 10000, mine is 10001

I did an upgrade recently. I also got the "An unexpected error has occurred" in the homepage, I was also able to access settings.aspx and sitemanager.aspx. The solution for me was as simple as iisreset.