000036214 - Saving a new record in a leveled application returns the error "This page can't be displayed" in RSA Archer 6.3.x

Document created by RSA Customer Support Employee on May 12, 2018Last modified by RSA Customer Support Employee on Jul 17, 2019
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000036214
Applies ToRSA Product Set: Archer
RSA Product/Service Type:  User Interface, Records
RSA Product Versions: 6.x
IssueSaving a new record in a leveled application returns the error: This page can't be displayed.

This error happened with a specific application when you try to save a new record under a specific level.

When tested on the Web server, the record doesn't get added and it gives http error: This page cannot be displayed.

User-added image

When tested from outside the webserver, sometimes it gives proxy error.

User-added image

Below is an example of the W3wp error.

                <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
                    <Description>Value is not a valid number: B83 Parameter name: serialDate</Description>
                        <ExceptionType>System.ArgumentException, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
                        <Message>Value is not a valid number: B83 Parameter name: serialDate</Message>
                        <StackTrace>   at Syncfusion.Calculate.CalcEngine.ComputedValue(String formula)
   at Syncfusion.Calculate.CalcEngine.GetValueFromArg(String arg)
   at ArcherTech.Services.Providers.CalculationProviders.SyncFusion.CustomFunctions.SystemCustomFunctions.If(String parameters)</StackTrace>
  • The error is from Syncfusion calc Engine. The application crashes when trying to save because of a Fatal Exception which can't be handled.
  • The error happens when a calculated field is updated with applying a formula.
  • Engineering was able to identify that if a calculation field contains a Formula that includes more than 14 nested IF conditions it gives this error. 
  • If the nested conditions are 14 it works. It crashes the application when it exceeds this limit. 
WorkaroundFirst, to test, you should either delete the field if possible or remove the formula anywhere outside and save the field with empty formula. Inactivating the field will not make any difference and the issue will continue to occur. 

After confirming you can now save the record added successfully. Divide the formula on a number of calculated fields to max 14 nested IF conditions under each calculated field.