guycampbell
asked on
error when following migration guide and creating OldCompanyWeb Web Application
hi,
I am working through the SBS 2003 to SBS 2008 migration process and have got to the stage of moving our internal site.
I am following the migration guide and i get an error when i try to create the new web application to hold the OldCompanyWeb site. the error reads as follows:
"The specified SPContentDatabase Name=STS_OEMSBSCN-2267_1 Parent=SPDatabaseServiceIn stance Name=Microsoft##SSEE is too old to be upgraded by this version of SharePoint. Please perform the needed intermediate upgrades before attempting this one."
i did check that i had SP3 for sharepoint 2.0 installed on the source machine and that the version of the old companyweb site was 6.0.2.8165 so i am not sure now what i need to upgrade to get this to work.
Any help would be much appreciated.
Regards,
Guy
I am working through the SBS 2003 to SBS 2008 migration process and have got to the stage of moving our internal site.
I am following the migration guide and i get an error when i try to create the new web application to hold the OldCompanyWeb site. the error reads as follows:
"The specified SPContentDatabase Name=STS_OEMSBSCN-2267_1 Parent=SPDatabaseServiceIn
i did check that i had SP3 for sharepoint 2.0 installed on the source machine and that the version of the old companyweb site was 6.0.2.8165 so i am not sure now what i need to upgrade to get this to work.
Any help would be much appreciated.
Regards,
Guy
You must first run the Prescan utility : see http://technet.microsoft.com/en-us/library/cc262231.aspx
ASKER
Hi,
I did run the prescan utility on the source machine. Everything looked fine, however the 1 difference between my set up and the migration guide has been that the database i had in SQL was not called STS_<SourceServerName>_1 (the source server name is SERVER) but the database was called STS_OEMSBSCN-2267_1. I assumed that this was not a problem and carried on with the migration, the mdf and ldf files i had and copied to the destination server were also named STS_OEMSBSCN-2267_1.
So i am now stuck at the point of creating the web application, I did try just inputting the source server name in the Database Server and Database Name fields but this has just created a blank web application. Probably because theres no data.... Am I fine to delete this new web application and any IIS sites and content databases connected to it as there is nothing to view when i try and confirm the Site Collection Administrator?
Regards,
Guy
I did run the prescan utility on the source machine. Everything looked fine, however the 1 difference between my set up and the migration guide has been that the database i had in SQL was not called STS_<SourceServerName>_1 (the source server name is SERVER) but the database was called STS_OEMSBSCN-2267_1. I assumed that this was not a problem and carried on with the migration, the mdf and ldf files i had and copied to the destination server were also named STS_OEMSBSCN-2267_1.
So i am now stuck at the point of creating the web application, I did try just inputting the source server name in the Database Server and Database Name fields but this has just created a blank web application. Probably because theres no data.... Am I fine to delete this new web application and any IIS sites and content databases connected to it as there is nothing to view when i try and confirm the Site Collection Administrator?
Regards,
Guy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have the same type of error,can any one help me out in this?