AutoCAD 2018 licensing crash – another reason to avoid subscription

AutoCAD 2018 licensing crash – another reason to avoid subscription

Autodesk has released an update to fix the following AutoCAD 2018 problem:

Product users of version 2018 Autodesk single-user subscriptions may experience an intermittent crash. The crash occurs when it has been more than 24 hours since the last successful authorization check and there is intermittent or no internet connection, or the licensing authorization server is unavailable. The licensing authorization check occurs in the background and is completely unrelated to activities the user is performing at the time of the crash.
A fatal error message may be shown by the product. For example:

FATAL ERROR: Unhandled e06d7363h Exception at ee563c58h

 
Links:

Note that this crash only afflicts subscription (rental) single-user (standalone) customers. People with perpetual licenses don’t have to put up with the multiple additional points of failure caused by the subscription licensing system insisting on phoning home every 30 days. Yes, even if you pay for three years’ subscription up front, you’ll still need a working Internet connection every 30 days if you want to keep using the product.

At least, Autodesk has been saying it’s only once every 30 days (as if that wasn’t bad enough). The information provided with this hotfix tells a different story. What is the license server doing phoning home 24 hours after the last successful authorization check? Enquiring minds want to know.

No criticism of Autodesk is implied for providing this hotfix. As always, I commend Autodesk for fixing up problems as they arise. The basis of my criticism is the hotfix being necessary in the first place. It’s caused by Autodesk inflicting unnecessary complication on its customers for its own internal reasons. This one fails the “how does this benefit the customer?” test big-time.

The single-user subscription licensing mechanism has been a crock from day one, especially for CAD Managers of multiple users who have to deal with its onerous requirements. It’s an astonishingly poor design, very badly implemented. Even with this particular crash fixed, it’s still a crock.

2 Comments

  1. blueginkgo

    The very existence of a time-limited license implies that the software’s default state is “not working”, the “working” state being subordinate to a set of conditions foreign to the software itself. The opposite of reliable engineering, by nature.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.