OK I am going for my once a quarter post, with yet another weird issue.

We are down to our final migrations from SharePoint 2003 to MOSS 2007 and we are running into a peculiar issue in the upgrade.log and the outcome of the upgrade. 

Due to the size of our farm and the number of SharePoint 2003 Portals we have chosen the database migration approach.  When we run stsadm –o addcontentdb …. It churns and the upgrade log reports it completed successfully.

When we browse to a site/page that had been modified via FrontPage 2003 in the old SharePoint 2003 portal, all the customizations are gone. The site/page has been reset to the site definition.  This is contrary to what had happened on previous database migration upgrades and from everything I have read regarding content database upgrades.

Looking into upgrade.log I see it littered with these messages:

This enumerates through all the webs in the site collection and each site collection in the web application.

Now on other content database that have successfully migrated this is what appears:

What am I missing on this?

[Updated 3/28/2008]

Long time no post.

We recently had the need to use the new stsadm operation of mergecontentdbs.  What I thought would be a very straight forward operation has not been.

I run:

stsadm -o enumsites -url http://url> sites.xml

I remove all but the one site that I want to move, http://url

When I run the following:

stsadm -o mergecontentdbs -url http://url/ -sourcedatabasename sourcedbname -destinationdatabasename destinationdbname -operation 3 -filename sites.xml

It outputs to the screen this message:

http://urlofsite/sites/sitename
Moving sites...

Then errors with this:

The following sites failed to be copied:
        Already exists in desintation database: SPSite Url=http://urlofsite/sites/sitename

Notice anything strange? That is not a typo that is the message.  Destination is misspelled.

Spelling errors aside has anyone run into this error while attempting to run mergecontentdbs and found a solution?

UPDATE

There are total of 18 site collections in the source content DB.  I was able to merge all but 2.  The other site that generated the error was the root one at http://urlofsite.

I have been working a lot lately with the provider model, http://msdn2.microsoft.com/en-us/library/aa479030.aspx.  Specifically I have been creating a custom MembershipUser to work with my custom MembershipProvider.  The goal is to create a single provider that we can use for SharePoint forms based authentication and use in a custom ASP.net app. 

Everything was going peachy until I started to create a class that inherited from the CreateUserWizard Control.  The CreateUserWizard calls the MembershipProvider's base CreateUser method in a method marked private called AttemptCreateUser().   Now since I created a custom MembershipUser that has additional parameters I cannot call my overloaded CreateUser method. 

The best I could come up with is to use the OnCreatedUser method of the CreateUserWizard class.   Here I cast the Membership.GetUser method to my Custom MembershipUser.  Then fill the extra properties and call Membership.UpdateUser method.  This works, but forces me to store null values or default values in the Database for those extra parameters of my custom MembershipUser.  This is particularly troublesome if it has a FK relation to another table.

Has anyone come up with a better solution using the CreateUserWizard Control?  Yes I know I could create my on control from the base Wizard class, but the CreateUserWizard control already offers everything, with the exception of overriding the AttemptCreateUser method.