Hi everyone,
I mentioned that I tried to upgrade a MOSS instance that wasn’t connected to AD. I have now changed this. I re-created my VM, connected that to AD, install MOSS 2007 then upgraded it to Sharepoint 2010 BETA.
The result is THE SAME.
The existing MOSS 2007 site wouldn’t load. It totally broke. It still said HTTP 403 FORBIDDEN (as per my previous article).
New site works no problem at all.
The detailed error was still the same ie. the old MOSS 2007 database somehow couldn’t be upgraded.
==
Server Error in ‘/’ Application.
——————————————————————————–
There is a compatibility range mismatch between the Web server and database “WSS_CSNET_Content”, and connections to the data have been blocked to due to this incompatibility. This can happen when a content database has not been upgraded to be within the compatibility range of the Web server, or if the database has been upgraded to a higher level than the web server. The Web server and the database must be upgraded to the same version and build level to return to compatibility range.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.SharePoint.Upgrade.SPUpgradeCompatibilityException: There is a compatibility range mismatch between the Web server and database “WSS_CSNET_Content”, and connections to the data have been blocked to due to this incompatibility. This can happen when a content database has not been upgraded to be within the compatibility range of the Web server, or if the database has been upgraded to a higher level than the web server. The Web server and the database must be upgraded to the same version and build level to return to compatibility range.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[SPUpgradeCompatibilityException: There is a compatibility range mismatch between the Web server and database “WSS_CSNET_Content”, and connections to the data have been blocked to due to this incompatibility. This can happen when a content database has not been upgraded to be within the compatibility range of the Web server, or if the database has been upgraded to a higher level than the web server. The Web server and the database must be upgraded to the same version and build level to return to compatibility range.]
Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.ValidateBackwardsCompatibility() +542
Microsoft.SharePoint.SPSite.PreinitializeServer(SPRequest request) +49
Microsoft.SharePoint.SPWeb.InitializeSPRequest() +258
Microsoft.SharePoint.WebControls.SPControl.EnsureSPWebRequest(SPWeb web) +365
Microsoft.SharePoint.WebControls.SPControl.SPWebEnsureSPControl(HttpContext context) +520
Microsoft.SharePoint.WebControls.UnsecuredLayoutsPageBase.OnPreInit(EventArgs e) +115
Microsoft.SharePoint.WebControls.LayoutsPageBase.OnPreInit(EventArgs e) +49
Microsoft.SharePoint.ApplicationPages.SettingsPage.OnPreInit(EventArgs e) +59
System.Web.UI.Page.PerformPreInit() +42
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1256
——————————————————————————–
Version Information: Microsoft .NET Framework Version:2.0.50727.4200; ASP.NET Version:2.0.50727.4016
==
On the next trial I will try to go down the content database attachment approach. I will install Sharepoint 2010 on a completely new VM, installing all features, create a brand new site collection, etc then attach the content database from MOSS 2007.
I’ll let you know how I go,
Tommy
