MOTUnation.com

All of a sudden I'm unable to use MX4, Aliverb and all of my iLok plugins.

At DP startup when DP scans all plugins I see an error window that the Authorizations can not be found, to insert my iLok and try again.........so I tried these steps:

1) unplug iLok and reinsert iLok into different USB port.
On peripheral USB hub AND on USB ports on the front/back of my MacPro itself.

My ilok lights up fine when plugged into any USB port.

2) reboot computer

3) go to ilok.com to verify that my iLok is working and verify that valid licenses are present.
Both are fine.

4) Follow iLok.com troubleshooting steps of un-installing and re-installing both the iLok client and the ilok driver.

5) Still I get the error message that authorizations can not be found

If anyone's been through this before, please let me know any suggestions.

Thank you!

Have you repaired permissions??

Stephen

You´ve done it but do try it again:
Reinstall the latest PACE driver or just do a reinstall of the Pace app.
http://www.paceap.com/index.html

I'm having no trouble in either 10.6.8 or 10.7.

Is something not installed in its default location?

DP authorization issues are usually cured by removing the AUTH file, generally hidden, repairing permissions, then re-authorizing. Failing to do all three steps in order won't get it fixed (found this out while installing DP 7 last Sunday).

Yes, I had this problem the other day, repeatedly.

After Repair Permissions, everything was fine.

The main problem I had was it couldn't find the authorizations on the iLok when logged into iLok.com, and also kept timing out when trying to write new license auth codes to the iLok.

This is with an iLok2, which I upgraded to recently.

I remember installing the same PACE update over again, then Repair permissions, and all was fine after that.

I suspect something else that was installed recently caused some unknown corruption or conflict with the PACE drivers. probably the latest Snow Leopard OS upgrade would be my bet.

mikehalloran wrote:
Is something not installed in its default location?

DP authorization issues are usually cured by removing the AUTH file, generally hidden

Thank you all for the replies!

What is the file path location of the 'AUTH' file?
I just enabled 'view hidden files' with Onyx after reading your post...

If AUTH is part of the file name, the following support page will tell you how to find and delete it:

http://www.motu.com/techsupport/technot ... ix-Leopard" onclick="window.open(this.href);return false;

The latest iLok and Pace software drivers were released July 26 2011.

Radiogal wrote:The latest iLok and Pace software drivers were released July 26 2011.

A Clue!

Thanks for the update, but I found the problem...

A few days after posting here, I logged in again at ilok.com and found that my ilok could not even be detected, but it was still lighting up and had no signs of damage, no loose parts.

That was new...

I did the RMA process and yesterday all licenses returned to me and put on a new ilok.
So it was another case of a hardware problem which at first did not act like a hardware problem.

Reminds me of when my bootup hard drive failed a few years ago.
One day I started getting weird error messages when trying to save a certain file type [not a music program--can't remember what program it was] but every thing else was totally normal.

Within 48 hours the disk was totally dead.

So I need to consider hardware problems more frequently when software isn't working as it should. I'm always quick to think that it's definitely a software problem...

Glad you got it resolved, but it's too bad the iLok failed and had to be replaced.

>So I need to consider hardware problems more frequently when software isn't working as it should. I'm always quick to think that it's definitely a software problem...<

I hear you on that. Bad memory is one that I run into more often than I think I should.

And for those of you with SSD's as your main drive, get in the habit of verifying your disc more often than you might of when you used a hard drive.

I have had three faults on mine since installing it in November 2010. Easy to repair, but not quick, so it pays to be pre-emptive vs. getting caught with a drive fault during a session.

In fact this WAS the cause of ONE of my license failure incidents for the iLok stuff!

mhschmieder wrote:And for those of you with SSD's as your main drive, get in the habit of verifying your disc more often than you might of when you used a hard drive.

I have had three faults on mine since installing it in November 2010. Easy to repair, but not quick, so it pays to be pre-emptive vs. getting caught with a drive fault during a session.

In fact this WAS the cause of ONE of my license failure incidents for the iLok stuff!

Apple supplied SSD or from a 3rd party?