I still encountered this bug with Prime Infrastructure 3.6.0 Update 01!
In the bug report it is marked as "fixed", but the count for "known fixed releases" is 0!
So is there anywhere a fix available?
So, the bug tracker says this is fixed in 3.7.(0.0), but I've just hit in 3.8(0)
The workaround worked for me
Hi, I am curious as I have the same error, which workaround was helping ?
Running Prime 3.8.0
After an upgrade to prime 3.9 we didn't have this problem anymore.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: