iLok freaking out today: Authorization Exception

[cshaw]

Originally Posted by [email protected]

This pops up every few seconds:

PCM Native Reverb Bundle cannot run, because an error occurred.

Authorization Exception
The software that you are trying to run requires an update. Go to www.ilok.com and download and run the latest License Service Installer.

I have all the latest drivers and versions. (pops up even when protools is off)
Anyone?

Not to be argumentative but the error dialog specifically says that iLok requires an update. Syncing licenses is not the same thing.


Sent from my iPhone using Tapatalk

[Barry Johns]

I got it as well, I updated my version of Ilok and all back to normal....There is a brand new version that was released in the last couple of days. Even after the one with Soundtoys.....

[sw rec]

My Softube Summit Audio Grand Channel just did it too, about when I thought I'd dodged the bullet. But, as stated, update your license manager and go back to work.

[Drew Mazurek]

Wow, imagine that.... in 2017 users might need to spend 30 seconds updating software.... what is the world coming to?

[musicman691]

This iLok update actually came out last week - at least that's when I did the update.

[TOM@METRO]

Originally Posted by Drew Mazurek

Wow, imagine that.... in 2017 users might need to spend 30 seconds updating software.... what is the world coming to?

[V5V]

1. For some of us it came at a very inconvenient time. Holding up an entire production chain while we figured out what was going on was disruptive.

2. The error message did say that we should download and install new software, but we were suspicious of that message. Nothing on that machine has changed in over two years, so it seemed odd and unlikely that the problem was due to a required software update. We wasted time eliminating other, more likely causes before running the update.

3. We all know that something as seemingly innocuous as updating the driver for a video device can adversely affect Pro Tools, so the policy in our facility is that we don't update ANYTHING without testing and having a path to back out of it. That's fine when we can plan to do it during down time, NOT fine when it occurs without notice.

4. The machines in one of our groups are managed remotely. The operators are not ABLE to install updates. That meant all of their work ground to a halt until someone in Engineering could be re-assigned from whatever they were scheduled to be doing to work on that instead.

The problem was not that an update was required. It was that there was no notice or opportunity to schedule it.

[cshaw]

Originally Posted by Drew Mazurek

Wow, imagine that.... in 2017 users might need to spend 30 seconds updating software.... what is the world coming to?

Sent from my iPhone using Tapatalk

[7thheaven]

Your smart-ass reply sucks!!! I am a professional musician that doesn't always run the updates, mainly because Avid can't seem to make stable software that doesn't love to spit out -1097 errors, so most pro users don't like to update things in fear of ruining a tour or critical timing sessions to deal with the song-and-dance support Avid offers customers.

The FACT that iLok has a database of users, and doesn't inform them of a critical update is really poor execution. But then again Avid is the king of poor execution (see TDM - AAX, old tired out-dated website, backwards compatible sessions to 12, etc.. ).

I agree with the CUSTOMERS on here (ya know the ones that pay for Avid to survive ) that this push was really ****ty. We never run wifi for many reasons, and then to have to guess why all the sudden all our iLok's stopped working is kinda messed up. TERRIBLE execution.

I'll even write the post that should have been sent out:

WARNING - Our unneeded company will render your iLok useless, unless you update the software by this date.

Avid, you seriously need to find a solution for this mess.
NOT very happy at all!!!!!!

[Top Jimmy]

Originally Posted by 7thheaven

Your smart-ass reply sucks!!!

Avid, you seriously need to find a solution for this mess.

Pace isn't Avid. If you're going to be snarky, at least you can be snarky at the right entity. This isn't Avid's snafu to apologize for.



Sent from my iPad using Tapatalk