Saturday 15 March 2014

SharePoint 2013 - IIS Server Errors

The following are some of the IIS Server errors that provide the general solution.
Error Message:
HTTP 500 Internal Server Error
Solution:
Start the SharePoint Web Services web application in IIS.

Error Message in SharePoint Designer 2013:
the server could not complete your request, for more specfic infomation click the details button
Solution:
Select the Anonymous Authentication in IIS. In Actions pane, click on "Enable" link. Now we can open SharePoint site in designer without any issues.

Error Message:
404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly.
Solution:
Application path share in every one on read and write Permission
or
Visual studio-> click aspx page properties --> dont copy

Error Message:
To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
Solution:
1) Go to Run screen and type services.msc
2) Look for SQL Server (MSSQLSERVER) service, right click on it and click Start

Error Message:
HTTP Error 404.3 - Not Found The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.
Solution:
-Open IIS Manager and navigate to the level you want to manage.
-In Features View, double-click MIME Types.
-In the Actions pane, click Add.
-In the Add MIME Type dialog box, type a file name extension in the File name extension text box.  Type a MIME type
-In the MIME type text box.

-Click OK.

Error Message:
HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid.
Solution:
Install the .NET Core Windows Server Hosting bundle on the hosting system.

1 comment: