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

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!
LVL 5
jkeegan123Asked:
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.

Jayaraja JayaramanSharepoint Architect ConsultantCommented:
did you run the pre-upgrade check before you actually migrated? wat are the issues you find?
0
jkeegan123Author Commented:
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

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
jkeegan123Author Commented:
There was no other solution offered and this is the solution that fixed the issue.
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.