Pro Tools not recognizing iLok

[musicman691]

Originally Posted by OctopusOnFire

Started happening to me a couple weeks ago, after using pro tools for over a year. Resetting NVRAM won't help. So far I've been trying to open the ilok license manager, other than the solutions mentioned above. It's pretty random and it kind of works whenever it pleases.

It's quite annoying, especially when you're in the middle of a recording and the musicians are waiting for you. I want to keep using PT but I don't think these things are acceptable for a DAW that is meant to be used in daily work.

I have this problem in a 2015 MBP, with 2.0 and 3.0 usb connections. The problem happens randomly in both of them.

EDIT: Pro Tools also crashes after the issue, it often needs for the whole system to restart.

Do you have the latest version of ILM? It's also possible your iLok is failing.

[alanm]

Originally Posted by Dale_G_sound

Hey ergalthema, I'm getting the exact same issue as you. I'm running an early 2013 13" Retina MBP and I've had the issue on both OS X 10.8/10.9. It's driving me nuts...

I don't think it is related to NVRAM/PRAM - the ilok can work one minute, then you can close PT and reopen it and it just won't see it. I get the same dialogue window showing. If I open the ilok licence manager I can it there with all the licences present. I'm pretty sure the issue has to lie with PT somewhere.

The only way I deal with this is by working around it by swapping ports, force quitting PT when I know it's not going to pick it up, resyncing the ilok, then finally rebooting. Even after all that it is still temperamental.

Same here, I had to reset NVRAM/PRAM preferences up to 3 times for it to work and then still it will not recognize it half of the times. I thought it could be something related to my audio interface (RME Fireface UFX) cause only since I started using it earlier this year this became a problem. I realized that if I always use the same usb port for my ilok and for my UFX (and I plug the ilok and turn on the UFX before turning on the computer) the issue happens less frequently though. Hope this helps.

[The Weed]

Make sure the iLok is on a USB 2.0 port - known issue. No USB 2.0 ports - get a USB 2.0 hub.

Cheers,

[OctopusOnFire]

Originally Posted by alanm

Same here, I had to reset NVRAM/PRAM preferences up to 3 times for it to work and then still it will not recognize it half of the times. I thought it could be something related to my audio interface (RME Fireface UFX) cause only since I started using it earlier this year this became a problem. I realized that if I always use the same usb port for my ilok and for my UFX (and I plug the ilok and turn on the UFX before turning on the computer) the issue happens less frequently though. Hope this helps.

What a coincidence, my problems started when I plugged my laptop to a RME Fireface UFX.

I still have the interface software installed, I'll remove it and see it it helps. The ilok problem just started happening today after a whole month working without issue. It only ever happens on the laptop, nowhere else, so maybe it's the RME software after all. I'll check it out.

EDIT: Ok that was weird. I uninstalled the RME software, restarted and now pro tools it's loading up correctly. I hope it was not random and we could find a cause for the problem. I followed this thread for instructions on what to delete. It's not 100% accurate but the file names are similar. https://www.forum.rme-audio.de/viewtopic.php?id=9233

[ergalthema]

OP here. Still having the problem. Sometimes unplug/plugging the iLok will work, sometimes not. Very frustrating.

[musicman691]

Originally Posted by ergalthema

OP here. Still having the problem. Sometimes unplug/plugging the iLok will work, sometimes not. Very frustrating.

Do you have USB3 or USB2 ports? It's a known issue that the iLok2 doesn't get along with USB3 ports. Get a powered USB2 hub and use that between the Ilok2 and computer.

[irishharry]

I have this exact problem. I have to reinsert my ilok a few times before protools recognises it. Once it recognises it I have no problems after that. I've started using a powered USB hub in my studio and haven't once had a problem with it since.

[broonskee]

SOLVED!
Had the same issue. Found it was a problem with the driver signature of the ilok which seemed to be caused by the licence manager software.

1. Re-boot system and tap F8 on start up
2. Select the option "Disable Driver Signature Enforcement”
3. Continue boot up as normal after that and in the ilok license manager try to activate whatever current licenses you have onto your ilok stick.
4. Once done then uninstall the ilok manager software and protools should just get the validation straight form the ilok stick without having to go through the license software.
5. Done.

*If you don't want to delete the software then you can follow steps 1 an 2 but you will have to do them on every start up which is a bit annoying. Hope it helps.

[RichrdC]

Sad (good?) to see others having this iLok that gets recognized one day and not the next. I figured I had an issue because I've got a USB hub with the iLok and other USB things are plugged into. I've heard the hub is a problem, but until this iLok issue, it's never been a problem. Then all of a sudden, my mouse wouldn't get recognized. I'm wondering if an AAE -9013 error couldn't also be prompted by this same issue?
Sorry to ramble here, richrdC

[musicman691]

Originally Posted by RichrdC

Sad (good?) to see others having this iLok that gets recognized one day and not the next. I figured I had an issue because I've got a USB hub with the iLok and other USB things are plugged into. I've heard the hub is a problem, but until this iLok issue, it's never been a problem. Then all of a sudden, my mouse wouldn't get recognized. I'm wondering if an AAE -9013 error couldn't also be prompted by this same issue?
Sorry to ramble here, richrdC

The hub shouldn't be the problem if it has an external power supply; sometimes bus-powered hubs can get starved for juice especially if they have bus powered devices plugged into them. I run a powered hub here.

I did have a problem with the iLok not being recognized one time. All it took was to unplug and replug-in the iLok and all was well. Sometimes connections go bad all on their own without anything being moved due to humidity or such.