Latest revision as of 04:41, 12 July 2021

Back to Contents

[edit] Overview

These are the most common causes of this error. If the name of the Layton ServiceDesk application is the default, LaytonServiceDesk, it will most likely appear in the error-page header, e.g.:

   Server Error in '/LaytonServiceDesk' Application

[edit] Incorrect Port Number

The installation may have been successful, but you see the following error on launch:

   Server Error in '/' Application
   
   The resource cannot be found.
   
   Description: HTTP 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.
   
   Requested Url: /LaytonServiceDesk/Login.aspx

Layton ServiceDesk assumes that it will have the port assignment 80. If other websites were previously installed on the same server, it's likely that one of them will have been given port 80 and Layton ServiceDesk will be given a different port number, e.g. 81. You can check the port assignment using this article.

Note that you may not be able to change the port assignment to the default 80. In this case, modify any link to Layton ServiceDesk to append the port number to the server name, e.g.

   http://server:81/LaytonServiceDesk/Login.aspx

[edit] SQL Server Service Not Running

The installation may have been successful, but you see the following error on launch:

   Server Error in '/' Application.
   
   Runtime Error
   
   Description: An application error occurred on the server.
   
   <!-- Web.Config Configuration File -->
   
   <configuration>
       <system.web>
           <customErrors mode="Off"/>
       <system.web>
   <configuration>

Check to see if the SQL Server service is running on the SQL Server.

Back to Contents