?
Solved

Sharepoint 2007 to 2010 Upgrade - Failing because of MODULES on the 2007 database

Posted on 2014-07-31
3
Medium Priority
?
118 Views
Last Modified: 2014-09-17
We are trying to upgrade a Sharepoint 2007 installation to Sharepoint 2010...when we upgrade the database, the upgrade is failing because of modules on the 2007 Sharepoint database that do not upgrade correctly.  

We have done a Sharepoint MIGRATION to a separate 2007 server using the same database and THAT worked fine.  

The upgrade reports all of the modules that caused the update failure in the error log, has anyone ever dealt with this before?  How can I  get this upgrade to continue and skip the errors?  Or can I pull the modules out before migration using any particular method?  It seems that the database upgrade STOPS when it hits these items, because the database is not in a functional state after the migration runs.

Any help is appreciated.  We have had Microsoft PSS on the issue working with us for a few weeks and the Sharepoint team and SQL team could not resolve this...

Thanks!
0
Comment
Question by:jkeegan123
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 8

Expert Comment

by:Jayaraja Jayaraman
ID: 40239025
did you run the pre-upgrade check before you actually migrated? wat are the issues you find?
0
 
LVL 5

Accepted Solution

by:
jkeegan123 earned 0 total points
ID: 40319286
This issue was resolved by doing a full dbcc check on the associated sql database before attempting the upgrade. This was an enormous task due to the size of the database (200gb), and the check took about 20 hours to complete, however once completed we retried the database migration and were successful.

Note that the upgrade log did not indicate at any point that there was corruption in the database  but database maintenance was the only item that we had not completed. I did it more for the size of the database than anything else, thinking that in a 200gb database there is sure to be some table or logical corruption. The check resulted In a larger 250gb database, but everything was consistent and the dbcc check did not result in any data loss.
0
 
LVL 5

Author Closing Comment

by:jkeegan123
ID: 40327533
There was no other solution offered and this is the solution that fixed the issue.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There is one common problem that all we SharePoint developers share: custom solution deployment. This topic can't be covered fully in this short article, so all I want to do in this one is to review it from a development-to-operations perspectiv…
SharePoint Designer 2010 has tools and commands to do everything that can be done with web parts in the browser, and then some – except uploading a web part straight into a page that is edited in SPD. So, can it be done? Scenario For a recent pr…
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …

765 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question