HSMWorks R3 Installer uses incorrect Product Key

[scottmoyse]

The installer for the Jan 29th/30th build of HSMWorks pre-populates the Autodesk HSM product key in the product key field during activation. Which results in an incorrect serial number error. I had to overwrite the product key with the one from my account, which resulted in a product called Autodesk HSMWorks Ultimate 2017 being activated successfully...

Also it's worth noting that although the installation went ok, after using the Activate HSMWorks tool from the start menu, and it telling me to launch HSMWorks to finish the activation. The HSMWorks addin would start to initialize, but then no CAM tab would load. The Addins dialog showed it loaded, and the About dropdown had no mention of HSMWorks. 

This was an upgrade from HSMWorks 2017 R1 using the old licensing system.

After restarting my PC, and launching HSMWorks again, still nothign. But worse, each time I closed Solidworks it would crash. The second time of launching HSMworks after the PC restart, a Solidworks message box asked if I wanted to block the HSMWorks add-in because it was causing Solidworks to crash. I felt that was progress, so clicked yes to continue loading HSMWorks, at which point I was finally presented with the Autodesk Activation dialog. So far from a clean experience, but it's activated and running now.

[jeff.pek]

Hi Scott -

Not sure what would cause all that. Maybe Rene has an idea.

As for the product key, this is expected. HSMWorks supports being activated with either product key -- but we expected this would typically be done with the Autodesk HSM key, so that's set as the default. As you've seen, you just need to modify it to use the HSMWorks product key.

I hope this gets reconciled for 2018, so that everyone would be consuming an Autodesk HSM license.

Jeff

[scottmoyse]

So if it was a subscription serial number then they would have been using the default HSM product key? But because this was a maintenance one it's the HSMWorks Product key?

It's actually an NFR. Should that have also been migrated to the HSM bundle? So far it's only had the upgrade to 2017.

[jeff.pek]

Yes, that's right.

I'm honestly not sure how the NFRs are being treated -- this should be part of what's shown in the account portal.

I'm pretty sure that if you're seeing the HSMWorks product key, it's considered a maintenance scenario.

Jeff