Migrating Companyweb from WSS 3.0 on Server 2003 to SharePoint 2010 on Server 2012
Our customers existing infrastructure:-
SBS 2003 domain. Companyweb on the DC was side-migrated to WSS 3.0 a long time ago.
Customer is now in the process of migrating to a new Server 2012 infrastructure.
I have various Hyper-V guests for testing purposes, and I need to move Companyweb away from WSS 3.0 and into SharePoint Foundation 2010.
The existing Companyweb database is slightly over 6GB In size, so here's what I have done so far:-
New Server 2012, joined to domain. Installed SharePoint Foundation 2010 in standalone mode (this installed SQL Express 2008 with a 4GB limit). Upgraded to SQL Express 2008 R2 to overcome 4GB limit. SharePoint still works at this point. (Created a checkpoint of the VHD at this point).
On SBS 2003, changed STS_tucsrv_1 database to read only, then took a backup.
On Server 2012, restored STS_tucsrv_1 into WSS_Content database.
From there on in, SharePoint no longer works. When I browse to http://share (share being the name of the test server) I get an error in IE which reads:-
SBS 2003 domain. Companyweb on the DC was side-migrated to WSS 3.0 a long time ago.
Customer is now in the process of migrating to a new Server 2012 infrastructure.
I have various Hyper-V guests for testing purposes, and I need to move Companyweb away from WSS 3.0 and into SharePoint Foundation 2010.
The existing Companyweb database is slightly over 6GB In size, so here's what I have done so far:-
New Server 2012, joined to domain. Installed SharePoint Foundation 2010 in standalone mode (this installed SQL Express 2008 with a 4GB limit). Upgraded to SQL Express 2008 R2 to overcome 4GB limit. SharePoint still works at this point. (Created a checkpoint of the VHD at this point).
On SBS 2003, changed STS_tucsrv_1 database to read only, then took a backup.
On Server 2012, restored STS_tucsrv_1 into WSS_Content database.
From there on in, SharePoint no longer works. When I browse to http://share (share being the name of the test server) I get an error in IE which reads:-
Server error: http://go.microsoft.com/fwlink?LinkID=177673
ASKER
Jamie, I forgot to mention that. Indeed I have run the checker, and there are some issues. The first 3 are because of the existing server not being 64 bit or Server 2008 SP2 or higher or because of the DB size.
However, there is one set of issues that I am not sure how best to resolve (if indeed they are even the cause of the migration failure):-
However, there is one set of issues that I am not sure how best to resolve (if indeed they are even the cause of the migration failure):-
Missing server file or server configuration issues:
Id = 7fbf9a80-8ae1-fa7e-9a51-30a786d33155 , Type = Unknown, Reference = 14, Status = Missing
Id = 2d70b18f-5f9b-fe07-da7e-946c6c2b3b96 , Type = Unknown, Reference = 1, Status = Missing
Id = 1a8eda1f-6a8c-d5b9-0a7a-062455488c90 , Type = Unknown, Reference = 1098, Status = Missing
I'm not immediately sure what those are either. Was any custom development done for your WSS installation?
Any commercial web parts or solutions purchased?
Any commercial web parts or solutions purchased?
ASKER
All three of the webparts are listed amongst others on this page:-
http://blogs.msdn.com/b/josrod/archive/2013/08/21/wss-2003-assembly-types-and-corresponding-type-ids.aspx
which says that they may show as unknown type when doing the pre-upgrade check.
This would make me think that these in fact are not going to cause a problem. So now I'm back to the start of not knowing why my migrated Companyweb doesn't work.
http://blogs.msdn.com/b/josrod/archive/2013/08/21/wss-2003-assembly-types-and-corresponding-type-ids.aspx
which says that they may show as unknown type when doing the pre-upgrade check.
This would make me think that these in fact are not going to cause a problem. So now I'm back to the start of not knowing why my migrated Companyweb doesn't work.
ASKER
OK, a bit more digging showed that the WSS_Content database is too old and needs an upgrade. I ran:-
PSCONFIG.EXE -cmd upgrade -inplace b2b -wait -force
I then got an error. I am attaching the logs just in case someone can spot the problem?
Upgrade-20140923-131558-242.log
Upgrade-20140923-131558-242-error.log
PSCDiagnostics-9-23-2014-13-15-56-914-52
PSCONFIG.EXE -cmd upgrade -inplace b2b -wait -force
I then got an error. I am attaching the logs just in case someone can spot the problem?
Upgrade-20140923-131558-242.log
Upgrade-20140923-131558-242-error.log
PSCDiagnostics-9-23-2014-13-15-56-914-52
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks - the Learning Center link worked a treat - had to re-run the PSConfig command after, but it's all working now!
Great news! Well done! :)
http://technet.microsoft.com/en-us/library/cc287628(v=office.14).aspx