Sharepoint Services 3.0 - Project Server Installation crashed...need help recovering please

Posted on 2014-02-11
Last Modified: 2014-03-27
We have been running a sharepoint services 3.0 installation with MS Project Server 2003 (yeah I know old stuff but it was what was here when I started not long ago)

Recently out of the blue the PWA site where we do timesheets and OLAP cubes for costing information on our projects went down. It all occured after I ran an update on our Windows 2003 server and now I cannot open the Sharepoint 3.0 Central Administration or anything else related to the site that existed.

Can someone please help me find the database information so I can retrieve it and possible try to restore the data somehow? We started up a new Sharepoint site with Sharepoint 2013, SQL Server 2012, and Project Server 2013 but it is really important to be able to at least get back our data from the other installation as it contained a lot of "costing" information.

Any guidance would be very appreciated.
Question by:jb61264
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
  • 4
  • 3

Expert Comment

ID: 39851021
All of the database information would be stored in your SQL instance.  Do you know if it was local SQL or if it was on a dedicated SQL server?  

Also, you can't go from 2003 directly to 2013.  You have to do a progressive upgrade since there were substantial changes to the application as well as the DB schema's.
LVL 38

Expert Comment

by:Justin Smith
ID: 39854448
Have you tried just uninstalling the update?

Author Comment

ID: 39854515
My database was a local SQL instance on the server (not remote). Ideally, I would like to find the database and perhaps import it into a different instance so I can get the data out of it...if this is even possible. The strange thing is that when I try to view it in SQL Enterprise Manager, I get a message that says "MMC could not create the snap-in"...also, the SQL Server Service Manager shows the server but shows it as stopped and when I click on start/ does nothing.

Strangely however, when I go into "Analysis Manager" it shows my server with a green triangle icon (indicating it is running) and I see our varous OLAP cubes..its like the information is there but there is no SQL Server Service running?...i don't get it.
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Accepted Solution

skipper68 earned 500 total points
ID: 39854569
The default location for WSS 3.0 databases is "C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\"  You can try to look there for the MDF and log files.  

The main databases you’ll want to move will be the content database, default named WSS_Content.mdf and maybe the config db, named Sharepoint_Config_%randomnumbers%.mdf.

You might also be able to search the drive for *.mdf files

Author Comment

ID: 39856750
I copied all of the .mdf files to folders on a separate machine. Can I reinstall Sharepoint Services 3, SQL Server, and Project Server on this machine now and then reload the mdb files I copied back into the new installation? or is there an easier way to extract the data in the .mdb files?

Assisted Solution

skipper68 earned 500 total points
ID: 39856951
Extracting the data isn't easy but it is possible.  Here is a link to a how-to.

The other approach would be to stand up a new wss 3.0 instance on a new or the existing server and attach the databases.

Author Comment

ID: 39950812
Anybody know of "instructions" somewhere that will help me reload the databases back into my re-installation of everything? I saved all the database files to another machine and am now going to try to reinstall/rebuild the server with the exact same installation I had before the update occured

Assisted Solution

skipper68 earned 500 total points
ID: 39950867
Here's a link:

But here are the steps:

1. Restore the databases back to SQL
2. Attach them using the following SharePoint STSADM command
stsadm.exe -o addcontentdb -url <URL name> -databasename <database name>

Here's a MS TechNet article explaining the AddContentDB command.

If you run into an error running the command, manually type the command into the command window and\or make sure you're running the command prompt as an administrator.

Featured Post

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

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

Why is this different from all of the other step by step guides?  Because I make a living as a DBA and not as a writer and I lived through this experience. Defining the name: When I talk to people they say different names on this subject stuff l…
A recent project that involved parsing Tableau Desktop and Server log files to extract reusable user queries for use in other systems. I chose to use PowerShell to gather the data, and SharePoint to present it...
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.

623 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