EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB487000: “Invalid information Please correct the marked fields and try again.” When trying to connect to an I-Server. Errors out on Port, Maximum Pool Size, Load balance factor, Server Busy Timeout, Request Timeout


Gustavo Sulbaran

Product Specialist • MicroStrategy


This article indicates the situation in which a user while configuring in the MicroStrategy Admin Section the I-server to be connected or some default properties, after clicking connect or save; the administrator encounters error “Invalid information Please correct the marked fields and try again”

Symptom

While configuring the Intelligence server from the Strategy Web Admin page section, after clicking "connect"  error “An error has occurred on this page” is encountered.

ka0PW0000003DVNYA2_0EMPW00000AlUXy.png

After editing the connection parameters from the I-server or default properties it shows the error
“Invalid information, please correct the marked fields and try again”
Image of the I-server section showcasing error at port, maximum pool size, and Load balance factor:

ka0PW0000003DVNYA2_0EMPW00000AlUXz.png

Image of the default properties section showcasing error at the port, maximum pool size and Load balance factor, server busy, and request timeout.

ka0PW0000003DVNYA2_0EMPW00000AlUY0.png

Cause

In general, this behavior should be related to the Locale setting. For example, if a customer uses French, (hose grouping separator is space) this will generate an issue when trying to communicate these parameters to the backend.
Some users will indicate this did not happen in the older versions and this is true due to the fact that In current versions of MSTR Web we upgraded from Java 8 to Java 11 (now is Java 17), and the default behavior was changed. Now the -Djava.locale.providers setting was introduced and is necessary to be included in setenv.sh or setenv.bat to prevent odd behaviors like the one described above.

Solution

The following article (impact of JDK 11 on the Strategy 2021 certification) displays documentation about the change
https://community.strategy.com/article/Impact-of-JDK-11-on-the-MicroStrategy-2021-certification?language=en_US
To apply the fix go to the area How to upgrade to AdoptOpen JDK 11 and set the JRE locale data and follow the instructions of one of these sections (the pertinent one)

  1. For Windows OS
  2. If Tomcat is run in a Windows service
  3. JBoss EAP 7.3.x on Windows
  4. For Linx OS
  5. JBoss EAP 7.3 on Linux

After the changes restart the application server.


Comment

0 comments

Details

Knowledge Article

Published:

December 26, 2024

Last Updated:

December 26, 2024