Error #- 5000 while verifying your Authorisation Unknown Error Help!!!

[Kitch]

My Waves 4 plufins are givving me hell I have had to cancel some mixing sessions ove the weekend cause I could not get any support from waves does anyone know what this is all about. I have tried repairing permissions and with the Pace Utility and the System utility but nothing I will not let me reautorise anything. I'm loosing out when I paid good money for my plugs. Help..... Anyone!!

PT6.0.1
OSx.2.6
G4 Dual 1.25
Mix system
Waves 4

[Kitch]

When I say plufins I mean plugins I should check my posts before pressing Add Reply.

Serverely Dyslexic
Kitch

[Jan Folkson]

Check the ownership of ALL your drives and partitions. I had the same problem and it was related to a non-audio partition. To check ownership single click on the drive icon and get info. The owner of all the drives should be you and you should be able to read and write.

HTH.

[Haxie]

Hi Kitch

You need to repair your iLok permissions. Insert your 6.0 installer cd and locate a folder named Interlock support. Inside this folder you will find a Disk image named PACE repair utility.dmg. Run the little app inside the disk image and everything should work as normal.
One note: Make sure that you have the latest Pace extensions.
I had this same problem with my 1.42ghz machine and the only fix for this issue was to install the latest Pace extension and then run the repair utility. I am not sure if this is a problem with the newer machines or the later versions of OS X, but this should fix your issue...

good luck.
let me know how it goes.

[DigiTechSupt]

Hello,

This is most likely a permisions issue of some kind. First make sure you are logged in as an admin. I would then try repairing disk permisions.


-Quit Pro Tools and launch Apple's "Disk Utility" application. Select your boot volume, go to First Aid and select "Repair Disk Permisions."

Mike

[Haxie]

Repairing disk permissions with Disk Utility will not fix this problem... That was the first thing I tried when the issue started happening to me. Like I said in the first post, the only fix was to run the Pace Repair utility and to make sure that the latest Pace extension was on my system.