Summary

Customers running Sage CRM on newer Microsoft Windows platforms (including Windows 11 and Windows Server 2025) may experience intermittent HTTP 500 Internal Server Errors when accessing certain Classic ASP-based pages, such as Dashboards and Self-Service screens.

This behavior is environment-related and not caused by Sage CRM application code.

Issue

When accessing Dashboards or Self-Service pages in Sage CRM, users may encounter intermittent failures, particularly during repeated page refreshes.

Symptoms

• HTTP 500 errors returned from IIS
• Dashboards or Self-Service pages fail to load intermittently
• Errors may occur on alternating refresh attempts
• No consistent or meaningful errors logged within Sage CRM

If detailed ASP errors are enabled in IIS, the following may be observed:

• Active Server Pages error ‘ASP 0240’ – Script Engine Exception C0000005

Cause

This issue is related to how newer Windows operating systems handle Classic ASP server-side JavaScript execution.

In affected environments:

• IIS may load JScript 9 (jscript9legacy.dll) instead of the legacy JScript 5.8 (jscript.dll)
• JScript 9 is not fully compatible with Classic ASP

This incompatibility can result in access violations (C0000005), particularly in scenarios where:

• VBScript and JScript are used together
• Server-side JScript creates COM objects
• JSON parsing or helper libraries rely on JScript

Additionally:

• Classic ASP reuses script engine instances across requests
• Reuse of incompatible engines can introduce instability in IIS worker processes (w3wp.exe)
• Failures may occur before ASP error handling completes, resulting in generic HTTP 500 responses

Resolution

To resolve this issue, configure the server to use the legacy JScript engine.

Steps

1. Open Registry Editor on the Sage CRM application server
2. Navigate to the following path:
3. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Main
4. Create or update the following DWORD value:
5. Name: JScriptReplacement 
6. Type: DWORD (32-bit) 
7. Value: 0
8. Restart IIS for the changes to take effect:
9. IISRESET

If the issue persists after applying the above steps, please contact Sage Support with details of your environment and error behavior.

Additional Information

• This is a known behavior documented by Microsoft in the IIS Support Blog
• The issue affects Classic ASP applications broadly and is not specific to Sage CRM
• Applying the registry setting forces IIS to use the legacy, fully compatible JScript engine