Thanks Tony. Definitely only Sharepoint Services 2.0. ;)
Hmmm.. fitting in another re-install isn't going to be easy. Is there no other diagnosis?
Main Topics
Browse All TopicsI have a customer with an SBS 2003 Premium R2 server. The companyweb does not want to work on this server. The rest of the services - including Sharepoint Services 2.0 & RWW - on the server work a treat. I have followed MS KB 829114 but found no change to the symptoms.
I've since (KB 829114) changed the logs location just for the companyweb & re-run ICW - I'm now able to determine precisely what accesses have been occuring specifically for companyweb.
Further diagnosis:
- ASP.NET v1.... is enabled as an Extension & the companyweb's ASP.NET tab is set to v1 (not v2).
- Sharepoint Services is enabled as an Extension.
- The companyweb is bound to the LAN IP Address of the server with the Advanced tab including both companyweb & companyweb.<domain>.local as host options on the LAN IP Address and (for testing) 127.0.0.1.
- The site is being accessed via various browsers: IE8, Firefox 3 & Safari with the same results.
The symptom involved is that the the http://companyweb returns an HTTP 400 error. When accessing http://companyweb/default.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Turns out that the SharePoint DB instance has a pair of databases which had different site IDs.
In the SharePoint instance, there STS_<servernaem>_1 database's dbo.sites has a single entry with an ID which did not match the STS_Config database's dbo.sites single entry's ID field. The former ID was copied into the latter ID & now all is working.
Resolution courtesy of MS support.
Business Accounts
Answer for Membership
by: thestarterPosted on 2009-08-05 at 04:05:19ID: 25021983
Hi,
om/kb/3202 02
Have you installed Sharepoint Services 3.0 perchance? i know this caused me a lot of problems in the past?
I had the same problem as you and after multiple attempts i had to reinstall the intranet as per the article 829114 but reboot prior to the section beginning:
"Install the Windows Sharepoint Services 2.0 companyweb Web Site for Windows Small Business Server 2003" (on page 3 of 5 if you print it)
if it fails always try again :) 2nd time lucky often works
Failing that and complete frustration you can try to reinstall IIS however bear in mind it will balls up exchange if you dont follow this: http://support.microsoft.c
Hope it helps
Tony