Error while upgrading to R12.8.06a, cannot get past the Java path
search cancel

Error while upgrading to R12.8.06a, cannot get past the Java path


Article ID: 240893


Updated On:




While attempting to upgrade the Policy Server to 12.8.06a on Windows, the GUI installer would not recognize the Java path entered. Some paths used would generate an on screen error, others would loop and prompt again with no failure message.



Policy Server 12.8.06a upgrade



As mentioned, the customer tried several variations of the Java path. Pointing to the bin directory or the Java root. They had also tried use AdoptOpenJDK/JRE 1.8 and 1.11 with the same results.

We were able to narrow it down to a specific hosted environment, whereas non of the on-prem Policy Servers had this issue. Working with our Engineering team, we use a debug build to get more details about the issue.

When we captured the output from the debug installer, it showed another issue actually happening.

openjdk version "" 2022-02-08
OpenJDK Runtime Environment Temurin- (build
OpenJDK 64-Bit Server VM Temurin- (build, mixed mode)
Message: Malformed \uxxxx encoding.
Cause: null
 Exception Stack : 

Here at Message you see it reporting malformed encoding due to the "\u". 

Once the Java path is given, behind the scenes it retrieves the Java and environment properties, and due to this \u error, it would error out.

But we would only see it happen when selecting the path, when in actuality it was what happens after choosing it.

The source of the "\u" was from the username performing the install. In this case it something like "u123456". So when the environment properties were printed out, it included a "\u": = u123456
user.home = C:\Users\u123456


A NIN was required to resolve this issue of upgrading to 12.8.06a when the username begins with a "u".

If you run into this issue, please open a support ticket and reference this defect, DE530862, to get the NIN.