TimeTrust Error Message HTTP 500.19

HTTP Error 500.19 Internal Server Error when installing TimeTrust

It may happen that when installing TimeTrust you receive the following message:

HTTP Error 500.19 - Internal Server Error

The requested page cannot be accessed because the related configuration data for the page is invalid.

This message is possibly due to an installation problem with MS IIS set up

Please confirm that Application Development features have been installed on the server - see image below:



Once these features are installed you may be required to restart the server for the features to come into effect.

    • Related Articles

    • Error message schema does not contain the specified table Snapshot

      If this error message comes up: The first step is to click on CHECK FOR NEW DASHBOARDS: if this does not work, there's potentially an issue with the view not going down correctly. In this case please lodge a Support Ticket (See below) For any ...

    • Installing Server and Workstation versions of Snapshot

      Once SnapShot is installed on the Server/Primary workstation initially, a shared database is created (the default name is SnapShot).  Load the Licence using web update (if possible) See installation notes on the Snapshotbi download page on how to do ...

    • Requirements to run TimeTrust

      Microsoft Windows Server 2008 or Higher IIS Installed Microsoft SQL Server 2008 R2 or Higher SSL Certificate (if accessing TimeTrust via the internet) Note: Please double check these requirements with your Partner or Plus as version changes take ...

    • Error opening file for writing Snapshot

      If you get this message, either  someone is still logged in somewhere on the Network, or the user doing the upgrade does not have permissions to the folder. Possibly try and get your Partner or IT team to run the upgrade, as an Administrator.

    • Get Snapshot Web working on same IIS server as Exchange - Application Pool keeps stopping

      When trying to run snapshot on the same IIS instance as Exchange, you can sometimes get a error where the Snapshot application pool just stops, and you have to manually start it again. This is due to some exchange components being 64bit, but Snapshot ...