Sign In

Email Address

Titanium Schedule - Support Portal

LHWC: 500.0 Error
Ticket: 13075
Created: 6/23/2015
Modified: 3/22/2019
Rating: No one has rated this article yet
Was this helpful? Yes   No

Before using this KB article verify 500 has trailing decimals

This article is specifically for 500.0 errors.


500 with no following decimals (e.g. - 500.19) is GENERIC and provides little useful information.

To get more detailed information from IIS Server on error:

From IIS Mgr, select the Ti website and from the center pane double click [Errors], right click on "500" and select 'Edit feature settings'; change to 'Detailed'. If Titanium is the only website on this IIS Server instance, reset the server process. Full details in Ticket 1141




500 errors are reported as "something wrong on the server end":



500.0 specifically points to ""Module or ISAPI error occurred".

Things to verify:
Verify ASP features are installed on the server.

Control Panel > Programs and Features > Turn Windows Features On/Off

IIS > WWWServices > AppDev Features > ASP.NET 3.5, which automatically enabled: .NET Extensibility 3.5, ISAPI Extensions, and ISAPI Filters.

IIS > WWWServices > Common HTTP Features > HTTP Errors & Static Content

Verify Authentication at the website.

For ASP pages to work, there must be some kind of authentication (website level).

On TiWeb (actual website, not server) > Authentication:

Using ‘Anonymous Authentication’ (recommended as to allow anybody to use website)

Using ‘Basic Authentication’ (requires the user to put in UserID and Password for accounts local to IIS Server) -

Using ‘Windows Authentication’ (requires the user to have a domain ID and be logged into local computer with that domain ID) - not recommended for kiosk, or any environment where the website would be used in outreach.

Verify Application Pool

On IIS Server Manager, Application Pools, right click the application pool being used for Titanium Schedule and under 'Process Model' verify that 'Identity' is set to "Application Pool Identity".  Additionally set 'Load user profile' to "True".


On SQL SSMS, Security > Logins, add “IIS AppPool\TiWebAppPool” where TiWebAppPool is the name of the Application Pool you previously set. There is a bug in MS SMSS that will not allow you to add the TiWeb role at this time. After you add it, go back in and give it TiWeb db role.


On the Windows Operating System, from the folder %system%\inetpub\wwwroot\TiWebsite, righ-click, ‘Properties’, {Security}, [Edit] and add:  “IIS AppPool\TiWebAppPool” and give “Modify” permission.


Verify Bin folder files aren't blocked

On the Windows Operating System, from the folder %system%\inetpub\wwwroot\TiWebsite\Bin right click on any of the .DLL files and select 'Properties' to verify that they DO NOT HAVE an [Unblock] button in the bottom right corner.

If you are familiar with Powershell, this unblocks them all:  Get-ChildItem -Path 'C:\inetpub\wwwroot\TitaniumWeb' -Recurse | Unblock-File

* thanks to Tom G @USM for sharing the Powershell command with us



Server registry settings:


recommendation to add this string instead:
<machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

After that, I could get WebTest.aspx to load correctly, but ConnTest.aspx still failed with the 500.0 error.

Further reading in that link suggests that a registry key is also involved, located at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\fipsalgorithmpolicy. I changed it from 1 to 0 (disabling it) and after that, ConnTest.aspx loaded correctly, and the connection test passed.



Additional Notes:

Configure antivirus/antimalware applications to exclude:

  • TiWeb folder
  • Temporary ASP.NET Files folder (C:\Windows\Microsoft.NET\Framework\v2.50727\Temporary ASP NET Files)



If after all that has been verified and you are still receiving a 500.0 error

If you are using Internet Explorer as your browser, please use anything else to help in the diagnosis process. 

If you only have Internet Explorer

At this point it would be prudent to enable IIS Server loggging for more detail.

Back to Control Panel > Programs and Features > Turn Windows Features On/Off

IIS > WWWServices > Health & Diagnostics > HTTP Logging, Logging Tools, and Tracing.

Bring up the Web Component again and have it cause the 500.0 error, making note of the time.  Then check the Windows Event Viewer log.

Some resources I've used to diagnose what's in the log:





Setting up the App Pool and connecting IIS to SQL:

Even if TiWeb is the only website on the IIS Server, still create a new application pool dedicated to TiWeb ‘TiWebAppPool’. This way if future websites are added to IIS Server, somebody making changes to the DefaultAppPool won’t affect TiWeb.

Add Application Pool > “TiWebAppPool”  … Advanced Settings:

Under (General), verify ‘.NET CLR Version’ is set to “v2.0”.

Under (General), verify ‘Enable 32-Bit Applications’ is set to “True”

Under (Process Model), verify ‘Identity’ is set to “ApplicationPoolIdentity” (Microsoft recommended)

Under (Process Model), vierfy ‘Idle time-out (minutes)’ isset to “0”.

Under (Process Model), verify ‘Maximum Worker Processes” is set to “1”.

Good info: http://blogs.msdn.com/b/cenkiscan/archive/2012/06/20/iis-best-practices.aspx

Under (Recycling), under “Generate Recycle Event Log Entry” set all options to “True”, set ‘Regular Time Interval (minutes)’ to “0”, select “Specific Time(s)’ and [add] an entry for 3AM.