SharePoint 3.0 IIS 6.0 issue accessing site

I would verify that in IIS Manager, that default.aspx is listed as the top default document.

Link:  https://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/dc6eb1b4-9028-4308-9935-52b64edfad36.mspx?mfr=true

Dan

Default.aspx is listed as the only document in IIS manager

Is the website returning an http error code when you don't use default.aspx in the URL?

Can you post a few lines (+/-10) from your http logs showing the hit on "/"?

If you use FireFox, can you turn on the Developer Tools - Web Console and then go to the site?  After you go to the site, click on the "Network" tab and then post a screen shot of what is showing in the console.

Dan

It's returning a HTTP 403 Forbidden error. On all the client workstations, when I connect to the SharePoint site it prompts me for a username and password but when I enter in the correct details it rejects them.

Also, if I put in the following http://*******/default.aspx it will let me view the SharePoint site but when I try to open a document it gives me a HTTP Error 404 - File or directory not found error.

See results be low from the Web Console -

Directory Listing Denied
This Virtual Directory does not allow contents to be listed.

GET
http://******/                              [HTTP/1.1 401 Unauthorized 0ms]
GET
http://******/                              [HTTP/1.1 403 Forbidden 16ms]

The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol.

Also, posting heavily redacted logs is only going to take longer to troubleshoot.  You can PM them to me if you are uncomfortable with posting them in the comments on the question.

Often the details to the issue are in the logged items before and after the actual error in the logs.

Dan

Hi,

OK - for the 401 / 403 issue: have you configured the registry key for "DisableLoopbackCheck" or set your URL in the "BackConnectionHostNames" as mentioned in the KB entry?
Have you afterwards rebooted the System? Afaik this change requires a reboot as the Local Security service does not recognize the runtime changes.

Second:
You have installed that security update. Did you run the SharePoint configuration wizard afterwards?
Even if you have run it, could you try to run the following in an elevated command prompt (explicitely started with right-click -> Run as Administrator):

C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\BIN\psconfig -cmd upgrade -inplace b2b -wait -force

Select allOpen in new window

Can you perhaps explain your SharePoint configuration?
Single server? Which OS? Which Service Pack (on OS level)? Which SharePoint version (Service Pack and Cumulative update)? What SQL Server version and edition?

Thanks and HTH
Rainer

Thanks Dan, I have looked at both the AppPool and File Permissions and they seem to be fine.

Rainer, when I originally investigated the KB983444 resolution I configured the registry key for "DisableLoopbackCheck". I have just run the SharePoint configuration wizard again with elevated permissions and rebooted. Still getting the same issue.

The setup is a single server running -

Windows Server 2003
- Service Pack 2

Windows SQL Server 2008
- Service Pack 3 for SQL Server 2008 (KB2546951)
- GDR 5538 for SQL Server 2008 (KB3045305)

Windows SharePoint Services 3.0
- Windows SharePoint Services 3.0 Service Pack 3

Have you tried the "DisableStrictNameChecking" fix as suggested in the workaround section of article KB983444?

Your http logs are littered with http error 401's... which translates to unauthorized access to a resource.

here is another article that mentions some workarounds.

link:  http://www.pentalogic.net/sharepoint-products/reminder/reminder-manual?p=troubleshooting%2F401errors%2F401errors.htm

Dan

Hi Dan, the  "DisableStrictNameChecking" fix is in place and I've followed the workarounds in the link but it's the same issue as before.

Went through everything again and then tried to change the AppPool. This time it works! Thank you for all your help!