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:
[SPManager] [DEBUG] [3/24/2008 2:51:45 PM]: [SPSite Url=http://portalurl/sites/ermg] Running 5 of 6 steps
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 2:51:45 PM]: Begin Initialize()
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 2:51:45 PM]: End Initialize()
[UpgradeReghostAction] [3.0.6.0] [INFO] [3/24/2008 2:51:45 PM]: Revert all document content streams.
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 2:51:45 PM]: Begin Upgrade()
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 2:51:45 PM]: Revert all document content streams of web: http://portalurl/sites/ermg.
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 2:51:45 PM]: Revert all document content streams of web: http://portalurl/sites/ermg/a
.….
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 2:44:38 PM]: End Upgrade()
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 2:44:38 PM]: Begin Commit()
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 2:44:38 PM]: End Commit()
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 2:44:38 PM]: Begin Dispose()
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 2:44:38 PM]: End Dispose()
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:
[SPManager] [DEBUG] [3/24/2008 11:19:27 AM]: [SPSite Url=http://otherportal/sites/projects] Running 5 of 6 steps
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 11:19:27 AM]: Begin Initialize()
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 11:19:27 AM]: End Initialize()
[UpgradeReghostAction] [3.0.6.0] [INFO] [3/24/2008 11:19:27 AM]: Revert all document content streams.
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 11:19:27 AM]: Begin Upgrade()
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 11:19:27 AM]: End Upgrade()
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 11:19:27 AM]: Begin Commit()
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 11:19:27 AM]: End Commit()
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 11:19:27 AM]: Begin Dispose()
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 11:19:27 AM]: End Dispose()
[UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 11:19:27 AM]: Elapsed time: 00:00:00.0468771.No mention of [UpgradeReghostAction] [3.0.6.0] [DEBUG] [3/24/2008 2:51:45 PM]: Revert all document content streams of web:…
What am I missing on this?
[Updated 3/28/2008]
On a hunch I ran the Configuration Wizard and Event ID 104 showed up in the event log. Here is an excerpt:Additional exception information: The initialize command is invalid or a failure has been encountered.
Unable to upgrade SharePoint Products and Technologies because an upgrade is already in progress. Upgrade progress can be monitored using the Central Administration Web Application or by monitoring the upgrade log on server There was no upgrade job listed in Job Status or Job Definition. I ran psconfig -cmd upgrade -inplace b2b -force. It chugged through the web applications and reported everything was already upgraded.
I restored the content database and reran stsadm –o addcontentdb for the content database and no more pages/sites getting reset.