SharePointSupport

Error : I have a Sharepoint 2013 running on a Windows Server 2012. Following issue appeared: I made a new Site-Collection as wiki. Everything (links,...) works fine on the server but when I want to access the wiki from outside (not localhost) the server runs in a 404 Not found error. http://localhost/sites/wiki/Pages/Home.aspx - works fine(localhost) http://10.38.0.15/sites/wiki/Pages/Home.aspx - doesn't work. I checked the IIS settings, all servers are up and running. The log file has no errors in it. Resolution : The most common cause for this is that you don't have the IIS host header configured correctly . The 404 will appear because you are hitting a different IIS web site and not the one you intended to. If you go into IIS Manager and click on " Sites " in the right hand pane there will be a column called bindings and a column called ID . IIS will check in the order of ID for the first site that matches. Make sure the default site is stopped

When you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or a later version, you may receive an error message that resembles the following: HTTP 401.1 - Unauthorized: Logon Failed This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address. Note You only receive this error message if you try to browse the Web site directly on the server. If you browse the Web site from a client computer, the Web site works as expected. Additionally, an event message that resembles the following event message is logged in the Security Event log. This event message includes some strange characters in the value for the Logon Process entry: Event Type: Failure Audit Event Source: Security Event Category: Logon/Logoff Event ID: 537 Date:

By default, IIS 7.0, IIS 7.5, and IIS 8.0 put log files in the following folder: inetpub\logs\Logfiles This folder contains separate directories for each World Wide Web website. By default, the log files are created in the directories daily, and the log files are named by using the date. For example, a log file may be named as follows: ex YYMMDD .log The HTTP status codes This section describes the HTTP status codes that IIS 7.0, IIS 7.5, and IIS 8.0 use. Note  This article does not list every possible HTTP status code as dictated in the HTTP specification. This article includes only the HTTP status codes that IIS 7.0, IIS 7.5, and IIS 8.0 can send. For example, a custom Internet Server API (ISAPI) filter or a custom HTTP module can set its own HTTP status code. 1 xx - Informational These HTTP status codes indicate a provisional response. The client computer receives one or more 1 xx responses before the client computer receives a regular response. IIS 7.0, I

HTTP errors are sent to your web browser from a website if a problem is encountered when trying to view a webpage. If the webpage can't be displayed, Internet Explorer will display either the actual error page sent by the website or a friendly error message built into Internet Explorer. Here are some of the most common errors and ideas for how to solve the problem that's causing them. The following table lists the most common HTTP errors that Internet Explorer displays. For information about HTTP protocols, error codes, and causes, go to the World Wide Web Consortium (W3C) website. HTTP error message What it means The webpage cannot be found (HTTP 400) Internet Explorer is able to connect to the web server, but the webpage can't be found because of a problem with the web address (URL). This error message often happens because the website address is typed incorrectly. Make sure the address is correct and try again. The