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:-

Server error: http://go.microsoft.com/fwlink?LinkID=177673
LVL 17
Chris MillardAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jamie McAllister MVPSharePoint ConsultantCommented:
I don't see a comment about using the Migration checker before the move?

http://technet.microsoft.com/en-us/library/cc287628(v=office.14).aspx
0
Chris MillardAuthor Commented:
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):-

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
0
Jamie McAllister MVPSharePoint ConsultantCommented:
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?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Chris MillardAuthor Commented:
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.
0
Chris MillardAuthor Commented:
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
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Chris MillardAuthor Commented:
Thanks - the Learning Center link worked a treat - had to re-run the PSConfig command after, but it's all working now!
0
Jamie McAllister MVPSharePoint ConsultantCommented:
Great news! Well done! :)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.