Improve company productivity with a Business Account.Sign Up

x
?
Solved

SBS 2008 WSS3 WSS_Content Migration

Posted on 2011-03-10
3
Medium Priority
?
621 Views
Last Modified: 2012-06-27
I am having a bit an issue with sharepoint. Recently, our sharepoint server got destroyed by the KB983444 update which never completes and destroys the sharepoint config database. None of the psconfig scripts or other documented fixed online fix this issue, so as i have had to do before, i wiped out shartepoint and re-installed it cleanly.

So now i have a default sharepoint system again. What i need to do is get the lists and views from the old sharepoint database. I have a copy of the old WSS_Content database, but using the database in place of the new one results in weird and wonderful errors, and doing a backup of this database and restoring over the top of the new WSS_Content database yields no results either - just more error messages.

All i need is the lists and views back out (i could even just do with the lists to be honoust and recreate the views) - but I dont know what else to do. I don't have enough knowledge of sharepoint.

Hope someone can help.
0
Comment
Question by:sparky2156
  • 2
3 Comments
 
LVL 12

Expert Comment

by:Hairbrush
ID: 35095137
Hi Sparky

Sorry to hear that your SharePoint installation got hosed by that hotfix.

The backup you have of the old database - was it taken before or after you applied the hotfix?  If it is before the hotfix, it is worth soldiering on in getting that attached in order to get the data out.  If not and the content database is unreadable by SharePoint, then it may be necessary to extract what you need directly from the database.  

There are some off-the-shelf tools that do this, starting with https://shop.quest.com/682/purl-recovery-manager-for-sharepoint?x-AdCode=cbShopBTNRecoveryManagerForSharePoint and http://www.sharepointrecoverytool.com/sharepoint-document-recovery

If you don't want to buy a tool... how comfortable are you with Transact-SQL and .NET programming?
0
 
LVL 3

Accepted Solution

by:
sparky2156 earned 0 total points
ID: 35505747
Only way we could resolve this issue was to restore the server from a backup, backup the sharepoint site with stsadm (http://technet.microsoft.com/en-us/library/cc512094(office.12).aspx)

Then restoring this with the stsadm command on the live server

Everything worked fectectly - should have done this in the first place, saved so much time
0
 
LVL 3

Author Closing Comment

by:sparky2156
ID: 35711354
Resolved myself.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

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.

Join & Write a Comment

In case you ever have to remove a faulty web part from a page , add the following to the end of the page url ?contents=1
When using a search centre, I'm going to show you how to configure Sharepoint's search to only return results from the current site collection. Very useful when using Office 365 with multiple site collections.
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.
Watch the video of Kernel Migrator for SharePoint, which demonstrate the process easily of migration from SharePoint to SharePoint, OneDrive for Business & Google Drive servers, Public Folder to SharePoint, File Server to SharePoint. The tool has va…

579 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