HTTP/1.1 404 Connection: close Date

Initial Error: “HTTP/1.1 404 Connection: close Date: Fri, 22 Oct 2010 05:36:09 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 12”

Initial Error:

“HTTP/1.1 404 Connection: close Date: Fri, 22 Oct 2010 05:36:09 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 12”

Quick Fix:

It generally means that there is no site collection created for the newly created web application. So just go to Central Administration -> Application Management -> Create Site Collection. Create a site collection under the web application and there will be no errors.

If you still see errors, check the Event log entries

Event log may have following entries like:

1. 1.    The database WSS_Content on ComputerName\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.
2. Access to the table dbo.sites is blocked because the signature is not valid.
3.  Access to module dbo.proc_GetCurrent is blocked because the signature is not valid.
4. SQL Database 'SharePoint_Config_' on SQL Server instance 'ComputeName\Microsoft##SSEE' not found. Additional error information from SQL Server is included below. Cannot open database "SharePoint_Config_" requested by the login. The login failed.

Cause:

This problem occurs when the initial provisioning of the Web service instance has not completed successfully. This behavior causes the upgrade process to skip the Web service instance.

Resolution:

1. Click Start, click Run, type cmd in the Open box, and then click OK.
2. Change to the following directory:

system drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin

3. At the command prompt, type the following command, and then press ENTER to stop the SPWebService service:

stsadm -o provisionservice -action stop -servicetype spwebservice -servicename ""

4. After the SPWebService service has stopped, type the following command, and then press ENTER to start the SPWebService service:

stsadm -o provisionservice -action start -servicetype spwebservice -servicename ""

5. After the SPWebService service is started, type the following command to complete the hotfix process or the update process:
   
   stsadm -o upgrade -forceupgrade -inplace
   psconfig -cmd upgrade -inplace b2b -wait –force
   
6. If the upgrade does not complete successfully, type the following commands at the command prompt, and press ENTER after each command:
   
   net stop MSSQL$MICROSOFT##SSEE
   net start MSSQL$MICROSOFT##SSEE
   psconfig -cmd upgrade -inplace b2b -wait -force

 

Resources:

http://support.microsoft.com/kb/944154
http://support.microsoft.com/kb/944267