Description

When we implemented the SSL certificate in our QA environment all our solutions have stopped working. 

 

When we checked the core logs we found the error:

Error-from-processor-Value-does-not-fall-within-the-expected-range-ErrorCode-2028

We followed the article for this error but the issue still remained:

Error from processor: Value does not fall within the expected range. ErrorCode: 2028

 

 

 We also updated all solutions with the new (https) URL in the deployment profile and made the modifications required in the Database.

We run the below command to verify Database URLs

 

Please log onto your Foundation Database:
run this on your foundation database: select * from SiteIdentifierMapping

 

 

 

 

All foundation URLs can be accessed via https like workflow, composer, forms, etc.

 

But still, the forms are not working.

 

 

Applies To

Foundation 11.x and 12.x

 

Cause

Configuration

 

 

Solution/Immediate Workaround

With the help of the key form's cache was set to file system.

This can happen due to differences in setups like Network Load Balancer (NLB)
The error message we were getting was happening due to the Form cache being enabled in the library. The default value is "Library" and if set to "File System" it starts using existing caching functionality.

For now, we have enabled the form cache to the File system. It is just how caching works for different setups. FormPublicFilesStore is an internal key to store temporary Composer Form's files (i.e. views, javascript, CSS ) to either "SharePoint library" or "File system". To support NLB Non-sticky session it should be selected to "Library".
It is recommended to change that setting back to the library if the customer faces issues with current settings and reset the app pool so that changes get reflected
A few customers had a problem with legacy cache settings in NLB environment in the pat, so the library value was added for those customers.

 

 

 

 

 

 

 

Additional Information

A documentation clone has been created to get this information updated in our Documentation:

https://jira.wswork.biz/browse/WIN-40008