Jason Chan

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 create a 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



Re: SharePoint - Setup, Upgrade, Administration and Operation Upgrade to WSS3 by migrating content database failed

Erik Bo

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






Re: SharePoint - Setup, Upgrade, Administration and Operation Upgrade to WSS3 by migrating content database failed

Jason Chan

Sorry I am not very clear about the document.

The doc said I have to create a Web appl for each virtual server before doing the database migrate.

Is your command for create empty web appl or run it *after* I created a web app

The problem is I dont know how to create a *empty* web appl
When I create a web appl it ask me to specify the content database server and name, so I typed the database I just restored from WSS2, after doing that I saw ithe database is upgraded (table name changed) , however it throw 404 error when I browse the site root.

In the second shoot, I removed all the thing (web appl, database) and try again.

This time I create a web appl and use the default name as the content database. It create a site collection in root / for me.
Then I use your command to add the database I just restored from WSS2, again I saw the database is upgrade but now I have 2 content db. I removed the previous one however it still have 404 error.

Have anyone success with the upgrade Help appreciate

Jason





Re: SharePoint - Setup, Upgrade, Administration and Operation Upgrade to WSS3 by migrating content database failed

Erik Bo

Your second shot should have worked all right - though you should not have deleted the content.db

try again without deleting and check the upgrade.log file for errors






Re: SharePoint - Setup, Upgrade, Administration and Operation Upgrade to WSS3 by migrating content database failed

Jason Chan

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.





Re: SharePoint - Setup, Upgrade, Administration and Operation Upgrade to WSS3 by migrating content database failed

Jason Chan

After fixing the upgrade definition file, I am very close to success excepted I cannot upgrade one custom list template to WSS3

Currently not more 404 error but "An unexpected error has occurred" in the homepage. I can configurate the setting from /_layouts/settings.aspx, I can browse all site contents except one custom list.

In my WSS2, I have a custom site definition and a custom list template, in every website created from the custom site def. will add a list of the custom list template automatically. And in the homepage of each site, I have a webpart that display data of the list.

I am thinking that list cause the problem.

I already map the list to the WSS3 custom list in the upgrade definition file. The list call "quicklaunch" with id 1200
<Lists>
....
<List
FromTemplateId="1200"
ToFeatureId="00BFEA71-DE22-43B2-A848-C05709900100" />
...
<Files>
...
<File
FromPath="{LocaleId}\stskgi\Lists\quicklaunch\AllItems.aspx"
ToPath= "pages\viewpage.aspx"
/>
<File
FromPath="{LocaleId}\stskgi\Lists\quicklaunch\DispForm.aspx"
ToPath= "pages\form.aspx"
/>
<File
FromPath="{LocaleId}\stskgi\Lists\quicklaunch\EditForm.aspx"
ToPath= "pages\form.aspx"
/>
<File
FromPath="{LocaleId}\stskgi\Lists\quicklaunch\NewForm.aspx"
ToPath= "pages\form.aspx"
/>
...
</Files>

And I have this error in the log:
Failed to look up string with key "XomlUrl", keyfile core.
Localized resource for token 'XomlUrl' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\Fields\fieldswss.xml".
Failed to look up string with key "RulesUrl", keyfile core.
Localized resource for token 'RulesUrl' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\Fields\fieldswss.xml".
#20015: Cannot open "schema.xml": no such file or folder.
(#2: Cannot open "schema.xml": no such file or folder.)
Failed to retrieve the list schema for feature {00BFEA71-DE22-43B2-A848-C05709900100}, list template 1200; expected to find it at: "".
Unknown SPRequest error occurred. More information: 0x81070215
#20015: Cannot open "schema.xml": no such file or folder.
(#2: Cannot open "schema.xml": no such file or folder.)
Failed to retrieve the list schema for feature {00BFEA71-DE22-43B2-A848-C05709900100}, list template 1200; expected to find it at: "".
List does not exist The page you selected contains a list that does not exist. It may have been deleted by another user.

Actually this list are no more required in the sites since WSS3 already have it own quick launch list. So how I can delete the list from the site

Thanks.
Jason





Re: SharePoint - Setup, Upgrade, Administration and Operation Upgrade to WSS3 by migrating content database failed

Bharat G

Hi Jason,

Have you been able to resolve your issue. I have the exact same scenario whereby one of my document library has been deprecated in wssv3.0 and thus, causing the exact same error messages in the log file.

Thanks

-- Bharat





Re: SharePoint - Setup, Upgrade, Administration and Operation Upgrade to WSS3 by migrating content database failed

frankok

Hi.
Have any of you managed to get past this error
I am in the same situation, with the same error messages in my log.

Thanks for any feedback.

Frank




Re: SharePoint - Setup, Upgrade, Administration and Operation Upgrade to WSS3 by migrating content database failed

Curtis Ruppe

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.





Re: SharePoint - Setup, Upgrade, Administration and Operation Upgrade to WSS3 by migrating content database failed

techietex

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!





Re: SharePoint - Setup, Upgrade, Administration and Operation Upgrade to WSS3 by migrating content database failed

Jason Chan

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, MS suggest we have custom site template with ID > 10000, mine is 10001







Re: SharePoint - Setup, Upgrade, Administration and Operation Upgrade to WSS3 by migrating content database failed

kwm

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.





Re: SharePoint - Setup, Upgrade, Administration and Operation Upgrade to WSS3 by migrating content database failed

Rachel.lane

Jason Chan wrote:

After fixing the upgrade definition file, I am very close to success excepted I cannot upgrade one custom list template to WSS3

Currently not more 404 error but "An unexpected error has occurred" in the homepage. I can configurate the setting from /_layouts/settings.aspx, I can browse all site contents except one custom list.

In my WSS2, I have a custom site definition and a custom list template, in every website created from the custom site def. will add a list of the custom list template automatically. And in the homepage of each site, I have a webpart that display data of the list.

I am thinking that list cause the problem.

I already map the list to the WSS3 custom list in the upgrade definition file. The list call "quicklaunch" with id 1200
<Lists>
....
<List
FromTemplateId="1200"
ToFeatureId="00BFEA71-DE22-43B2-A848-C05709900100" />
...
<Files>
...
<File
FromPath="{LocaleId}\stskgi\Lists\quicklaunch\AllItems.aspx"
ToPath= "pages\viewpage.aspx"
/>
<File
FromPath="{LocaleId}\stskgi\Lists\quicklaunch\DispForm.aspx"
ToPath= "pages\form.aspx"
/>
<File
FromPath="{LocaleId}\stskgi\Lists\quicklaunch\EditForm.aspx"
ToPath= "pages\form.aspx"
/>
<File
FromPath="{LocaleId}\stskgi\Lists\quicklaunch\NewForm.aspx"
ToPath= "pages\form.aspx"
/>
...
</Files>

And I have this error in the log:
Failed to look up string with key "XomlUrl", keyfile core.
Localized resource for token 'XomlUrl' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\Fields\fieldswss.xml".
Failed to look up string with key "RulesUrl", keyfile core.
Localized resource for token 'RulesUrl' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\Fields\fieldswss.xml".
#20015: Cannot open "schema.xml": no such file or folder.
(#2: Cannot open "schema.xml": no such file or folder.)
Failed to retrieve the list schema for feature {00BFEA71-DE22-43B2-A848-C05709900100}, list template 1200; expected to find it at: "".
Unknown SPRequest error occurred. More information: 0x81070215
#20015: Cannot open "schema.xml": no such file or folder.
(#2: Cannot open "schema.xml": no such file or folder.)
Failed to retrieve the list schema for feature {00BFEA71-DE22-43B2-A848-C05709900100}, list template 1200; expected to find it at: "".
List does not exist The page you selected contains a list that does not exist. It may have been deleted by another user.

Actually this list are no more required in the sites since WSS3 already have it own quick launch list. So how I can delete the list from the site

Thanks.
Jason



Can anyone provide some explanations for the custom list template problem Jason described. I am experiencing a similar problem where I cannot browse to the custom list after the upgrade. I did exactly the steps as Jason: created the custom list template as a feature in WSS 3.0, added the mapping entries in the upgrade file; but I am getting the "Failed to retreive the list schema for feature...." errors in the log file.