Restoral is so close yet so far

So here's the scoop: the server was lost but the config and content databases are available from backup. Server is 2003, Sql 2005, and WSS 2. When I rebuild the server and use the restored content database I can't access any of the content (tasks, lists, documentlibraries, etc.) I do not have the inetpub folders in backup, only the database.

In SQL Manager I attached to the config and content databases just fine; no errors. I reinstalled WSS 2 and pointed to the original config database. After a few errors (app pool security stuff) it seems to be OK; setup finished and took me to the central admin webpage. Here's where it gets weird.

When I setup a new site (e.g.,http://mainsite/subsite) I extend the server and point to the content database. Again, a few errors but I cleared these up and the install/setup finished. The problem is that none of the content is visible. It's just a default WSS site.

So the question is this: what am I doing wrong that I can seemingly access the content database but not actually see any of the data?

[1522 byte] By [JoeRitson] at [2008-2-17]
# 1

Mr. Ritson,

Let me be sure of the steps you have taken so far.

You restored the CONTENT db. Not the configuration db

In SharePoint you selected - Create a portal

Then you chose - Restore a portal site

Selected Servers and databases

Chose your virtual server and specified your URL

Then you extended and mapped your virtual servers

Is that correct?

Stephen-SP911 at 2007-9-4 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...

SharePoint Products and Technologies

Site Classified