Startup failed an unexpected error occurred

[Mvandenbrink]

Since yesterday, we have been receiving reports from an increasing number of users that Solibri can no longer be started. They are presented with the error message shown below. This occurs with users of both version 26.4.0 and 26.4.1. Deleting the .solibri folder from the user directory on the laptop does not resolve the issue either. Are there others experiencing the same problem, and if so, how did you resolve it? @Solibrians @tonigyllenberg I also submitted a ticket with you yesterday, and I hope to receive a response soon, as multiple users are currently unable to perform their work.

class java.lang.String cannot be cast to class java.lang.Integer (java.lang.String and java.lang.Integer are in module java.base of loader ‘bootstrap’)

Edit:
Probably worth noting that klist.exe is still being blocked by Microsoft Defender during installation of 26.4.0 and 26.4.1 like mentioned over here: https://society.solibri.com/post/14447

[Matti]

Thanks for the report. Try reinstalling Solibri in other location, maybe this is an update failure.
We will remove the klist.exe from the next installer.

[Mvandenbrink]

@Matti Installing into a new location instead of updating solibri doesn’t solve the issue. Hopefully our log files will help solving the issue.
output.log
runtime.log

[Matti]

Do you have a trial license?

[BIM GI]

Since yesterday, I’ve been having the same problem.

[Mvandenbrink]

@Matti Yes, there is indeed an Advanced Trial in our portal. How and/or why this was added to our portal is unknown to me. The Advanced version did work last week though, a few users used that licence a couple of times. We have now disconnected the trial licence from the groups and users are able to access Solibri again.

[Matti]

Thanks for the reports and log files. We are currently investigating an ongoing issue related to trial licenses that can prevent Solibri from starting with the error:

class java.lang.String cannot be cast to class java.lang.Integer

We are continuing to investigate the root cause and will provide an update as soon as we have more information.

The klist.exe warning from Microsoft Defender is a separate installer-related issue. We are already planning to remove klist.exe from the next installer.

[Matti]

The fix will be deployed to the licensing backend, so there is no need to reinstall Solibri. We currently plan to deploy the fix later today and will provide another update once it has been released.

[BIM GI]

Everything is back to normal. Thank you.

[Matti]

The license issue is resolved now.