0

When trying to open my SharePoint, I receive the following:

HTTP/1.1 200 OK Server: Microsoft-IIS/8.0 Date: Wed, 04 Sep 2013 12:29:51 GMT Connection: close

  1. Site Collection does exist
  2. Application pool and website is started
  3. I have done IIS reset
  4. I have done a server reboot
  5. Other site collections work on the same Web application
  6. I have even tried running the Products and Config wizard again.

Additional Symptoms(SOOOOOOOOOO weird):

When accessing the WFE server with the Farm account used to install the SP 2013 server, the following is MISSING, please note when logging in with a different account, the below is present:

  1. SharePoint 15 hive
  2. SharePoint windows services
  3. SharePoint executable icons, such as Central admin, Products and Config, and SP Powershell

ANY ideas or advice would be great.

Thank you, JP

  • Do you have a firewall in place, such as MS Forefront? Think you might have to publish the web app URL through the firewall to allow it to load on clients. – James Love Sep 4 '13 at 12:42
  • 1
    I'm guessing your WFE server just doesn't have SharePoint installed, and is also therefore not connected to the farm. – James Love Sep 4 '13 at 12:42
  • There is only 1 WFE, and other site collections are working, thus SharePoint has to be installed and connected to the farm. – JP Roelofse Sep 4 '13 at 12:43
  • Open up IIS and check if the sites are there? The fact that you can't see the folders is a permissions issue. – Fox Sep 4 '13 at 12:54
  • Did you ensure that the site collection do exist by checking it in the "View all site collections" in the central admin? – msounthar Sep 4 '13 at 12:55
1

I found the answer to why my Default site collection was dead. I wrote it all up on my site. http://dea.nbird.com.au/2013/09/11/sharepoint-2013-http1-1-200-ok-server-microsoft-iis8-0-connection-close-error/

Hope it helps.

We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.

  • 1
    Afraid it doesn't help very much because, while this may theoretically answer the question, we prefer inclusion of the essential parts of the answer here, and to provide the link for reference. See answer for general guidelines. – SPDoctor Sep 16 '13 at 7:49
0

Try going to Control Panel> Administrative Tool>Server Manager> Web Server. it contains the log for the reason why its not running. Mostly it is some services that stopped. The log will give exactly the which services have stopped, and go to the services and start that service(usually it's the SecurityToken service. Good luck.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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