I had a single-user license on my laptop but not anymore. When I start the application I get this message:
Error Information: Flame (ADLSDK_UPDATE_REASON_LICENSE_UPDATE): timed-out after 30.0 sec(s) waiting for Agent to connect
ERROR: Licensing Error
So I think changing the licensing type might solve the issue. I followed the online docs to reset license type via the flame_setup app but no go. There must be a local file when deleted will let me choose my license type again?
Hi guys, we have a strange licensing issue here, 2022.2 and 2022.3. Licensing started to say it can not connect to internet on two machines. Tried to reinstall flame - no luck. Tried a quick fresh OS install on a separate ssd - works fine. But it is rather a drag to reinstall everything on two machines. Any ideas on where it could potentially stuck?
Iād try to reinstall the Autodesk Licensing Service. Sometimes after removing all of /opt/Autodesk and reinstalling Flame it complains licensing and when I reinstall using this procedure it solves it. Not sure if it will solve your problem though.
Tried removing /opt/Autodesk. /var/opt/Autodesk, /var/lib/Autodesk or any numerous āAutodeskā folders one could find but only clean system install (with /opt/Autodesk from the previous system copied to retain the project structure) got the licenses back. Interesting thing that it did happen at about the same time on two machines that were clones in terms of os (Centos 8.2) but different Flame installs and different framestores logged in as different adsk users on completely different network locations. Both has just refused to connect to adsk licensing and only clean system installs fixed it so far.
This has been reported and being investigated via channels outside this forum. But you should open a case with support. Also you state RL 9.4, but that is not a supported OS.
Not sure what you mean by āUpgrading from RL 8.7ā since there is no OS upgrade path between RL 8.x and 9.x. You need to perform a clean installation of Rocky Linux 9.3 (and not 9.4, as pointed out by Alan) using our ISO and DKU. If you do not follow these steps you run into a non qualified system and we will not be able to help. Stick with validated components to save time and effort.