HTTP 400 Bad Request in WSS 3.0

Hi, I have a site in my Windows Sharepoint 3.0 and today my server was hang, after I do a hardreset, I can´t access to our WSS site, the explorer show HTTP 400 Bad Request.
I don´t have a backup, but I can see the Content Database with the SQL Management Studio.
I already create a new site and restore the ContentDatabase with the overwrite option, but the problem persist (HTTP 400).(I restore using the SQL Management Studio 2005).
Is there a way to restore my site from the WSS_Content database?
Regards!
Esteban_GNAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

nalla_btsCommented:
Check these places for error logs:

SharePoint logs
Event viewer
0
Esteban_GNAuthor Commented:
Hi,
Where I can see the Sharepoints logs?
I don´t have any event regarding the problem on Event Viewer.
Thanks
0
Esteban_GNAuthor Commented:
Dear Nalla,
I perform the following:
1. Restore the DB "WSS_Content" using the SQL Management Studio
2. Create a new application called http://server02:4444 without any site, only the app.
3. Run "stsadm -o addcontentdb -url http://server02:4444 -databasename WSS_Content"
Now in the WSS admin page I can view the DB "WSS_Content" is already associated in the new app, and also another DB content created by the system, and both show "zero sites created" and the state is "running"
The answer now,
How I can "re-create"  my site with the information?
Regards!!
0
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

vikas413Commented:
take following steps

1. Create Web App on new Server

Central Admin->Application Management->Create or extend Web App->Create New Web App.

2. Associate restored DB with new Web App

Central Admin->Application Management->SharePoint Web Application Management->Content Databases->Remove Content Database from your new web app.

3. Now use STSADM to add restored DB to this web app

c:\program files\common files\microsoft shared\web server extentions\12\bin on new server is where you can find the STSADM.

run this command from there.

stsadm -o addcontentdb -url http://yourwebapp:port -databasename yourcontentdb -databaseserver yoursqlserver

4. Run ISSRESET from command prompt.

Note:

1. make sure your running the same service pack level on both source and destination sharepoint if possible.
2. Make sure you install all webparts, solutions, features, etc on new server before you restore the content database, so that it can find all the features it's looking for.
3. Make sure you copy any files that may be living in the file system that you need, sometimes people have css/javascript here.  (This refers to files in the hive)
4. Leave your old site and contentDB intact until you get the backup running on the new server, this way your ok if there is a problem.
5. DON'T try this with your config database! It won't work!

hope this will help you to recreate your site.
0
Esteban_GNAuthor Commented:
Hi I already perform the operation, the DB is attached, but there is not any site collection.
The admin page show "0" zero sites
:(
0
Esteban_GNAuthor Commented:
I install a clean WSS 3.0 installations in another server with a SQL 2005 SP3, but the problem is the same, I can attatch de DB, but can´t access to site collection.
Another info: the source server is a SBS2003 with WSS 3.0 and later I apply the SP2.
and the new server is WSS 3.0 with SP2 included.

Regards,
0
vikas413Commented:
does current db was linked with any other web application also? is so .. then just remove it from there and try again
0
Esteban_GNAuthor Commented:
The current DB is alone, its attached to the new webapp only.
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
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.