KB487103: Error loading settings in XXXX. Please check the server configuration and try again” when accessing an environment’s settings from Workstation

Symptom

 
When accessing an environment’s settings in Workstation, some pages return the following error message: "Error loading settings in XXXX. Please check the server configuration and try again.".
 

 
This impacts the following pages:

• Governing
• Security
• All settings

 
From the REST API, another error message is returned when using the same endpoint as Workstation:
GET /api/v2/iserver/settings
HTTP 500
{"code": "ERR001", "message": "Text '11:0' could not be parsed at index 3", "ticketId": "8297331c53884c30a2a87af1fe1e223a"}
 
From the Library logs, a similar yet more detailed message is retrieved:
"message":"RestError [code=ERR001, iServerErrorCode=0, message=Text '11:0' could not be parsed at index 3, httpStatusCode=500, ticketId=8297331c53884c30a2a87af1fe1e223a]","logger_name":"com.Strategy.rest.exceptions.GenericExceptionMapper","thread_name":"http-nio-8080-exec-16","level":"ERROR","level_value":40000,"stack_trace":"java.time.format.DateTimeParseException: Text '11:0' could not be parsed at index 3\r\n\tat java.base/java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2046)
 

Cause

 
The problem is related to a datetime setting on the I-Server. The pattern for a date time should be HH:mm:ss or HH:mm. As the error message implies, the string that gets parsed into the DateTimeFormatter method is '11:0' which isn't an acceptable format specified in the code: HH:m instead of HH:mm. The error message is consistent regardless of the time at which the error is reproduced. Hence, it is not the current time which is being parsed.
In the output for the /api/v2/iserver/settings, there is only one actual field that is explicitly listed as a date, which is:

 "defaultLicenseComplianceCheckTime": {"value": "23:59:00"…

Solution

1. Follow KB13544 to access the Named User compliance check from Developer.
2. If the value is set to “11:00”, increase or decrease some minutes and save the changes.
3. Restart the I-Server.