Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am banging my head against the wall here. I have basically a fresh install over server 08, TFS 2010 (don't get me started on TFS 2008), and WSS 3.0 which was packaged and installed with TFS. Unfortunately TFS is boned because WSS3.0 and WSS 3.0's Administrator Panel are unreachable. The app pools are running fine in IIS and previously, it would prompt for a username and password and then 404 (it is no longer doing so).

Has anyone ever experienced this? If so, what did you do to correct it / what should I look for? Thank you so much in advance!

share|improve this question
add comment

4 Answers

Check your IIS logs. The 404 has a lot of subcategories.

It sounds like the handler may not be enabled, tho.

share|improve this answer
    
I'm sorry for this stupid question, but what handler? –  Chance Jul 14 '09 at 2:08
    
In IIS manager, click the site, and choose "Handler mappings". –  M Aguilar Jul 15 '09 at 1:49
add comment

The Windows Event log might turn some details. I would also look at Sharepoint logs (under the 12 hive).

Can you connect to your DB server from your web server?

Have you setup the correct account permsisions? link

Are you sure the right version of ASP.Net is mapped to the website?

share|improve this answer
add comment

Are you trying to access from the WFE server?

There is a security feature in WS2003 SP1 and WS2008 which blocks requests coming from the machine hosting the application. Here is a link to a good blog post on the details of the problem and best practice for overcoming it http://harbar.net/archive/2009/07/02/disableloopbackcheck-amp-sharepoint-what-every-admin-and-developer-should-know.aspx

A hard problem to diagnose as you won't see anything useful in logs etc. because nothing is actually failing!!

share|improve this answer
    
ok I didn't read the question correctly. This problem causes 401 –  Simon Fox Jul 16 '09 at 9:34
add comment

Try re-running the SharePoint Products and Technologies Configuration Wizard to re-establish Centeral Administration. Once you get that up and running you can make whatever other configuration changes are needed to get the rest of SharePoint going.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.