PACE iLok Error stops PT from booting

[joeshepard]

I tried to open Pro Tools toady and got the error:

"Error,missing PACE authorization for "Pro Tools". Please insert the necessary iLok or rejoin your your iCloud session and restart Pro Tools". ///my only choice at that point is to click "OK" which quits the Pro Tools start up.

My iLok 3 is plugged in and it shows up in the iLok Manager as working.

I tried moving it to a different USB slot and restarting my mac. Same result.

Nothing that I can see has changed since I ran a session yesterday.

PT 2021.7 Mac OS 10.15.7 2018 Mac Mini 3.2 GHz 6 core i7 23GB RAM

Thanks for any ideas,

Joe

Joe

[huzzam]

Originally Posted by joeshepard

I tried to open Pro Tools toady and got the error:

"Error,missing PACE authorization for "Pro Tools". Please insert the necessary iLok or rejoin your your iCloud session and restart Pro Tools". ///my only choice at that point is to click "OK" which quits the Pro Tools start up.

If you open the iLok License Manager app, do you see a Pro Tools license somewhere? Ideally it should be on your iLok, but also check in "All Licenses"

[jeffro]

Originally Posted by joeshepard

..."Error,missing PACE authorization for "Pro Tools". Please insert the necessary iLok or rejoin your your iCloud session and restart Pro Tools". ///my only choice at that point is to click "OK" which quits the Pro Tools start up...

Sorry for the trouble. iLok status is good, and your licenses look correct on your iLok. avid.secure.force.com/pkb/articles/Error_Message/missing-PACE-authorization-for-Pro-Tools has the basic steps to troubleshoot. I started a support case to try and assist. Pls check your email and reply to the case notice. Thanks!

[joeshepard]

Yep it's there Pro Tools Ultimate perpetual

I also have a current support plan

iLok account is up to date as is my ZDT

[joeshepard]

OK

Jeffro is a rock star.

Turns out I had an empty iLok iCloud session open which was confusing the system.

I would have never figured that one out.

FANTASTIC help.

Now, back to work!

Smile

Joe

[jeffro]

Glad that solved it! I'll update the KB article to include this info.

[bernstudios]

when I started up protools I suddenly got the message:

Error missing PACE authorization for "ProTools". Please insert the necessay iLok or rejoin your cloud session and restart Pro Tools"

I changed nothing from yesterday and it worked all great always in last 15 years of protools - anyone having the same problem?
I checken with ilok License Manager the license is on the ilok

I used different cables and hubs, blue light of the ilok is on.. what could this be! I need to finish some work..!!

thx for your help

Macbook Pro (15inch 2019), 2.4 Ghz Intel Core i9, 32GB Ram
Mojave 10.14.6., Protools 2021.6.0

[bernstudios]

Update: moved my license to my cloud and now it works again - but I want it on my ilok
all my other licenses work from my ilok..

[Ben Jenssen]

I had some strange behaviour from Pace last night, about 10-12 hours ago; there was an alert every few minutes saying 'Error trying to authorize your Pro Tools license with iLok cloud'. Strange thing is, PT continued to work. I've had a few episodes with my iLok Cloud license not working before, but that resulted in PT not working and quitting.

Eventually I restarted the mac, and no more errors. I suspect I could have just opened iLok License Manager and closed and reopened the so-called iLok Cloud Session. It's worked before.

I'd expect if you move the license back to the iLok key, it will be OK again.
Added: Remember to 'close the ilok Cloud session' from the file menu in ILM.

[jeffro]

Originally Posted by bernstudios

...Error missing PACE authorization for "ProTools". Please insert the necessay iLok or rejoin your cloud session and restart Pro Tools"...

Good advice from Ben (thanks). Merged your thread with a similar one from yesterday - closing an unused iLok Cloud session (all license were on their iLok USB Key) solved it. I updated avid.secure.force.com/pkb/articles/Error_Message/missing-PACE-authorization-for-Pro-Tools with this info.