07-09-2019 06:26 AM
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?
10-30-2020 08:52 AM
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
10-27-2021 02:50 AM
Hi, I am curious as I have the same error, which workaround was helping ?
Running Prime 3.8.0
Regards Niko
10-27-2021 03:57 AM
After an upgrade to prime 3.9 we didn't have this problem anymore.
best regards
Karl
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide