By using this web site, you agree to all terms and conditions for acceptable use.

ServiceLedger KnowledgeBase Knowledgebase Home Page > ServiceLedger > Technical | Contact Us

Search the Knowledge Base Browse by Category

ServiceLedger provides this content as-is for self help support purposes. ServiceLedger assumes no liability for any steps you take based on the directions in our knowledge base, and assumes that you have the knowledge to determine whether a given step is appropriate for your situation. Certain solutions can affect third-party software that ServiceLedger relies on or integrates with; it is your responsibility to consult with the documentation or publishers of such third-party software to understand whether any changes suggested here will have negative effects on other applications.

(T0104) Troubleshooting web server Internal Server Error 500

Would you like to...

Print this page
Email this to a friend

If you receive "Internal Server Error 500" after installing ServiceLedger web applications, please:

  • Make sure that the server mode copy of ServiceLedger is running and configured properly. For more information, see  (T0112) How do I run ServiceLedger in server mode?
  • Find the folder that ServiceLedger.dll is located in (c:\ToC if installed according to the standard instructions) and make sure that the IWAM & IUSR accounts on the local web server have execute (read & execute) permissions on this folder.  Additionally, ensure the ASPNET account (if you have .Net installed) has execute permissions as well to this folder.  Usually this is done by right clicking the folder in the explorer and selecting properties.  Next select the security tab.
  • Check that Enable Parent Paths is on for the virtual directory you installed the web application into (usually ServiceLedger, SLTechPortal, or SLCustomerPortal).  In the Internet Services Manager, locate the virtual directory, right click and select properties.  Select the configuration button.  Ensure that "Enable Parent Paths" is turned on.  Apply your changes and reboot the web server.
  • Make Sure the Web Application runs within ServiceLedger Web Application Space for Windows 2003 servers.  This is performed in the Internet Services Manager.  Windows 2003 provides application spaces.  As part of the installation of the web server, you should create a specific application space for ServiceLedger.  Please review your ServiceLedger web installation documentation and ensure you have performed this step.  It is only necessary for Windows 2003 server.  Reboot if changes are made.
  • Make sure you are running in High Isolation mode.  Necessary for all Windows web installations other than Windows 2003.  Please refer to your web installation instructions that this step was performed.  Reboot if changes are made.
  • Ensure ServiceLedger.dll was registered with RegSvr32.exe as listed in installation
  • Verify that all files that begin with default_ (not default.aspx or default.asp, however) are renamed without default_.  If the file names already exist, then this paragraph may not apply for a specific file.  Recent updaters handle this automatically, however an older version may not.  For the tech portal, there are additional files in the Utility folder.
  • If you are running IIS 7.0 or later (Vista, Windows 2008), Then ensure that for the Tech Portal Application in IIS Manager that the ASP configuration for Send Errors to Browser is turned on (Under Debugging Properties), to allow further troubleshooting.
  • If you are running a 64 bit web server, enable 32 bit applications under the Advanced Settings of the Application pool you are running the portal under.

Related Questions:


No attachments were found.

ServiceLedger KnowledgeBase Copyright © 2020
Powered by AcitveKB Knowledgebase Software