Trying to get 2022 going. I download the latest Network License Manager for Linux, stop the current NLM that has been running fine with 2021 and then do the rpm install command according to the documentation.
rpm -vhi nlm22.214.171.124_ipv4_ipv6_linux64.rpm
It immediately returns “error: Failed dependencies: adlmflexnetserverIPV6 conflicts with adskflexnetserverIPV6-11.18.0-0.x86_64”
I’ve rebooted for good measure and that didn’t help. If I install my newly-generated license file neither Flame 2022 or 2021 work, so I’m guessing the old license manager doesn’t like something in the 2022 license and I need to upgrade. But I can’t.
Do I need to completely uninstall the old license manager first? If so, what’s the best way to do that? Or can I just remove the conflicting “adlmflexnetserverIPV6” package somehow? I don’t need or use IPV6, so this seems like additional pain I don’t need.
@Gunpowder friends? Any thoughts?
Ah, try “rpm -Uvh nlm126.96.36.199_ipv4_ipv6_linux64.rpm”
The upper case U specifies that you’re updating the existing package.
-vhi is trying to over-write the old version so you’re seeing the package conflicts.
not one ive seen before and didnt have the same issue on a machine that was upped from 2021 to 2022 (albeit only yesterday!!).
to remove the package you could do;
rpm -qa | grep -i adskflexnetserverIPV6
which will probably just return “adskflexnetserverIPV6-11.18.0-0.x86_64”
and to remove that rpm it would be;
rpm -e adskflexnetserverIPV6-11.18.0-0.x86_64
and then try installing the license manager again.
!! however !! i cant guarantee that wont cause more problems as ive not had to do it myself - im just thinking out loud here! proceed with caution…
I would probably speak to autodesk support for a sanity check, especially if the machine needs to be running in production!
ahh yes, @tombox is right too
So, rpm -qa | grep -i adlmflexnetserverIPV6 returned:
I removed both of those with the rpm -e command. YOLO.
rpm -vhi nlm188.8.131.52_ipv4_ipv6_linux64.rpm then got a little further, telling me it had conflicts with a pdf file and a few other utilities that should be newer as part of this install. So then I did the rpm -Uvh command and added the --force option. Then it installed fine. Yay!
I rebooted just to make sure the new lm would run at startup as expected. All good. My 2021 and 2020 products run fine. However, the first 2022 product I installed (Flame Assist) refuses to run, giving me a license error. Good times.
I’m going to install Flame 2022 and see if it behaves differently but this is probably heading straight toward a call to support. But as long as my previous versions still work I’m OK for now.
Just filed a case with support. There is an online license parser that shows what products are included in the generated network license file. My license (which I’ve generated twice now and they are identical) does not list anything from the 2022 family. It lists 2018 through 2021, but no 2022. So, it looks like a problem at the point of license generation.
It’s always a licensing thing for me. Always. Hah.
@mattriley what version of Linux are you using out of interest?
If Centos X you can always use Yum to install files which takes care of dependencies automagically.
“yum install nlm184.108.40.206_ipv4_ipv6_linux64.rpm”
I’ve upgraded it from 7.2 in the past so maybe some cruft from that and previous NLM installs was lurking in there and caused the dependency issue.
Ah, 100% migrate all rpm installs over to yum. It’ll make your life MUCH easier.
RPM = doesn’t take dependencies into account
YUM = I’ll figure everything out that you need to get this installed
Just heard back on my issue of 2022 network licenses not being generated… They asked me to try generating a license again today and give it a shot. This time, the online license parser showed 2022 products in the license file and I’m now up and running 2022.
No explanation as to why it didn’t work last week, but I’m happy to be able to explore the new release now.
I think @Skulleyb was having this issue to.
yeah there was not a 22 lic created… Sounds like they may have fixed it.