Hi,
I have two Flames on the same network at the same location. We keep having dumb licensing problems. We cannot seem to both be working at the same time – even though I’m paying for 2 boxes and we are signed in as different emails.
I get this error when trying to open Flame, and I can’t work. We’ve tried various things…
It just hangs with this empty window, and I cannot open Flame.
Is there still a remnant of ADSK support? And how would one contact it? My last attempts came to nothing…
I think the same happened to me a few weeks ago. I’ll look what the fix was.
re: support, yes still there and responsive. The new assistant actually makes it a bit easier to open a case. It’s not as dumb as the previous one.
however license support goes to a different team which has less of a positive record.
@GPM I had the same symptoms. You have to reset the licensing status on the system and then it will work again. It happened a few times in a row, and then went away. Mine was on MacOS, but could easily be on Linux as well. I think some status or certificate gets horked.
Here are the details: More licensing shenanigans - #6 by allklier
Aaand this one might also help
Thank you, Jan and Sinan. We’ll try this in the morning
I’d rather not spend as much time sorting out licenses as actually working on this job with a deadline.
this a worldwide issue that is affecting Flame Linux ver 2024.x and 2025.x in multiple houses … not affecting Macs - One that autodesk need address with a QFE or patch release asap
No response from ADSK support, and I still cannot run my Flame, from any registered user. We sign out of ADSK management browser, Reset license through Setup – but the login doesn’t pop up like normal when doing so. It’s not initializing the connection to the web browser to do the log in authorization.
Any ideas? I’m pretty dead in the water and we’ve tried pretty much everything.
When you contact support do not select “licensing” as your problem. This is straight from the Flame support team.
I didn’t flag it as licensing. Just technical support. Then I submitted it again, flagged as installation and registration, or whatever the option is called. Still nothing from ADSK…
I would say that advice holds true if it is a 100% product issue. Anything licensing adjacent should still go to that team,
Based on your screen grab you sent to support, this does not look to be your issue.
Chrome broke the setup along with a few other issues that needed to be resolved. Have a great weekend.
Who’da thunk it was Google Chrome??
Big thanks to Beau at ADSK, and Gagik at MetVid, and Culley Bunker for helping me out.
It takes a village to raise an idiot.
Was good to chat with you and my boy Gagik again. Teamwork makes the dreamwork.
Interesting. For future incidents, let’s add changing default browser to things to test.
Chrome is a problematic product. I get security advisories in a feed. Almost every other day there’s a Chrome vulnerability, more than any other software I use or any browser.
I’ve stopped using Chrome as my main browser 10 years ago. I keep it for as needed access to Google products.
Chrome is basically malware. I just can’t understand why people use such shit.
Totally agree. As many things Google, it started with a great premise (fast, nimble, works well), and then it slowly turned it corporate crap over time. Worse yet, it’s a total surveillance tool as well.
And it’s not just Chrome. There was a good story the other day that most CTOs don’t trust Google Cloud and said so at a conference. Despite some good innovation, It will be forever 2nd tier after AWS and Azure because of the infamous Google Graveyard. It’s not a tool that can trusted long-term.
For some time during the pandemic I had some inside views, and many of people working on it, do mean well, but the product road map and the bigger picture is very cloudy.
