@dayjob
Just trying to draw an analogy that might be applicable to a Mac based on my Windows fix ...
My hunch is that the .sbd file is "locked" to the iLok License Manager ... and that lock has to be broken (by stopping the Service) *before* the file can be removed in a manner that *allows it to be rebuilt and updated*. That's why I asked if there is a "Services" equivalent in a Mac. When I initially removed the .sbd file it simply returned with a newer date and time ... but without seeing the Update Storage License popup I wouldn't have known it was updated. Maybe that's the key ... break the lock between the .sbd file and the ILM ... remove the file ... restore the lock ... update the file (verified by the Update Storage License popup). Unfortunately I can't say how to do that on a Mac.
For Windows guys ... I can report that after several reboots the fix I used is working fine. Fingers crossed though!
KenB
SOLVED: Beware New iLok (HD?) Authorised Software Installations
-
- KVRAF
- 3398 posts since 6 Nov, 2006
yeah.. that's what is supposed to happen but it isn't doing anything. i deleted the file, uninstalled the licenser.. made sure the file was deleted.. emptied the trash.. rebooted. reinstalled the licenser app... rebooted... relaunched the licenser app.. and nothing has changed.TexLoco5 wrote:@dayjob
Just trying to draw an analogy that might be applicable to a Mac based on my Windows fix ...
My hunch is that the .sbd file is "locked" to the iLok License Manager ... and that lock has to be broken (by stopping the Service) *before* the file can be removed in a manner that *allows it to be rebuilt and updated*. That's why I asked if there is a "Services" equivalent in a Mac. When I initially removed the .sbd file it simply returned with a newer date and time ... but without seeing the Update Storage License popup I wouldn't have known it was updated. Maybe that's the key ... break the lock between the .sbd file and the ILM ... remove the file ... restore the lock ... update the file (verified by the Update Storage License popup). Unfortunately I can't say how to do that on a Mac.
For Windows guys ... I can report that after several reboots the fix I used is working fine. Fingers crossed though!
KenB
oh and i did this 4 times now. per iLok
Please close iLok License Manager and try following these instructions again:
1) Go to the following location:
/Library/Preferences/
On Mac OS X 10.7 & greater, the users Library directory may be hidden by default. To temporarily view this location, hit Command+Shift+G from the desktop (or Finder > Go > Go to Folder) and type in the following
~/Library
This will give temporarily access the Library directory in the Finder. When done, close this window and it will no longer be visible.
2) Delete the "com.paceap.eden.clientdb.v1.01.sdb" file found there
The client database on Macintosh will be reset after completing this step.
-
- KVRAF
- 5622 posts since 23 Aug, 2014 from Boston/Cambridge
Thanks, guys.
One thing is certain, although Compyfox will have a hard time admitting it: the only party to blame is iLok/PACE, since I didn't add or activate any new plugin.
One thing is certain, although Compyfox will have a hard time admitting it: the only party to blame is iLok/PACE, since I didn't add or activate any new plugin.
-
- KVRAF
- 8446 posts since 29 Sep, 2010 from Maui
I have not had any problems, although I did happen to ignore the last Ilok
update and have not as yet tried the adaptiverb demo.
I did get a notice of a critical upgrade for Ozone 7. Wonder if maybe its related
to this. *shrugs...
-Cheers
win 8.1 64, pretty much all of the plugins involved in this fiasco...
update and have not as yet tried the adaptiverb demo.
I did get a notice of a critical upgrade for Ozone 7. Wonder if maybe its related
to this. *shrugs...
-Cheers
win 8.1 64, pretty much all of the plugins involved in this fiasco...
-
- KVRist
- 39 posts since 12 Jan, 2014
@dayjob
Well ... ya deleted everything and started over from scratch. Hmm ... it sounds like even though you deleted everything that there is something that's rebuilding it.
What I don't get is ...
I'm on Windows ... iLok told me to stop the Service before removing the file.
You're on a Mac ... but iLok didn't mention a similar step. Which leads me to believe ... you have a different problem than I did, there is no Service equivalent on a Mac or iLok didn't tell you all the steps. Bloody frustrating either way.
Wish I had an answer ... I should prolly shut up because I know absolutely nothing about Mac's.
KenB
Well ... ya deleted everything and started over from scratch. Hmm ... it sounds like even though you deleted everything that there is something that's rebuilding it.
What I don't get is ...
I'm on Windows ... iLok told me to stop the Service before removing the file.
You're on a Mac ... but iLok didn't mention a similar step. Which leads me to believe ... you have a different problem than I did, there is no Service equivalent on a Mac or iLok didn't tell you all the steps. Bloody frustrating either way.
Wish I had an answer ... I should prolly shut up because I know absolutely nothing about Mac's.
KenB
Last edited by TexLoco5 on Tue Aug 16, 2016 12:43 am, edited 2 times in total.
-
- KVRAF
- 2620 posts since 16 Jan, 2013
If rebuilding the sdb doesn't fix things, try using an older copy.
As I said before, if you have a backup containing the sdb file from before the problems arose, try restoring the "good" sdb file and reinstalling the iLok software. It worked for me in the past when a malfunctioning ethernet driver changed the location ID on my system.
As I said before, if you have a backup containing the sdb file from before the problems arose, try restoring the "good" sdb file and reinstalling the iLok software. It worked for me in the past when a malfunctioning ethernet driver changed the location ID on my system.
-
- KVRAF
- 5622 posts since 23 Aug, 2014 from Boston/Cambridge
One of the developers just contacted me, writing: "iLok just hit me up and said that it should be good to go now." He's a great guy, absolutely trustworthy, but the question is whether iLok is too.
-
- KVRer
- 1 posts since 16 Aug, 2016
AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
I got all of my licenses working on Mac by doing this:go to www.ilok.com (http://www.ilok.com) and download the latest version of the "License Support"
open the dmg and run "Uninstall License Support.app"
Go to Library/Application Support and deleted the 'Pace' folder
reboot
re-install the License Support from the dmg
All my licenses are now working
Strangely enough, the 'Pace' folder I deleted hasn't come back again :/
-
- KVRAF
- 3398 posts since 6 Nov, 2006
fixed. what a relief.
so, the iLok tech support person who i have to admit handled one much too snarky moment on my part rather cooly.. finally simply booted/forced all my licenses off their locations and they showed up in my "available" licenses cue and i was able to reactivate my desktop and laptop machines w/o any problem.
now i'm ready to eat dinner, have a glass of wine and get some work done. fug.
so, i'm glad they have that ability to remotely unfug things from their end when needed. fug and fug again.
edit: she admitted that forcing activations off remotely is the nuclear option and there are several good reasons not to start with the nuclear option.
so, the iLok tech support person who i have to admit handled one much too snarky moment on my part rather cooly.. finally simply booted/forced all my licenses off their locations and they showed up in my "available" licenses cue and i was able to reactivate my desktop and laptop machines w/o any problem.
now i'm ready to eat dinner, have a glass of wine and get some work done. fug.
so, i'm glad they have that ability to remotely unfug things from their end when needed. fug and fug again.
edit: she admitted that forcing activations off remotely is the nuclear option and there are several good reasons not to start with the nuclear option.
Last edited by dayjob on Tue Aug 16, 2016 1:13 am, edited 1 time in total.
-
- KVRist
- 239 posts since 9 Feb, 2013
-
- KVRist
- 343 posts since 13 Jan, 2012 from In the studio, in front of computer.
Yep, PACE just told us that as of now, the issue has been fixed. Thanks to the people who helped us get them the information they needed to resolve this so quickly.
Basically, you should simply start ILM – a progress bar should show up. Let that complete before quitting ILM. All should be good afterwards.
OR
Simply run ADAPTIVERB (or any other software that has the "activation experience"). This also fixes the issue.
Basically, you should simply start ILM – a progress bar should show up. Let that complete before quitting ILM. All should be good afterwards.
OR
Simply run ADAPTIVERB (or any other software that has the "activation experience"). This also fixes the issue.
Last edited by zynaptiq on Tue Aug 16, 2016 2:33 am, edited 1 time in total.
Zynaptiq - Audio Software Based On Artificial Intelligence Technology, makers of PITCHMAP: Real-Time Polyphonic Pitch Correction And Mapping.
-
- KVRAF
- 14738 posts since 19 Oct, 2003 from Berlin, Germany
I think the license manager needs to log on to the online account in order to snag a hotfix
My main question would be... Who is to blame? Zynaptic, Air Music Tech or Pace?
But it clearly shows that the first contact should always be the company in question, not Pace. The devs have a higher leverage and more direct "hotline"
And despite all the negative experience, the issue was fixed fairly quick still, no?
Anyway... Good to see people getting their equipment back up and running.
My main question would be... Who is to blame? Zynaptic, Air Music Tech or Pace?
But it clearly shows that the first contact should always be the company in question, not Pace. The devs have a higher leverage and more direct "hotline"
And despite all the negative experience, the issue was fixed fairly quick still, no?
Anyway... Good to see people getting their equipment back up and running.
-
- KVRAF
- 5622 posts since 23 Aug, 2014 from Boston/Cambridge
Come on, Compyfox, give it up.
I didn't even know about Zynaptiq (written with a 'q') until this thread, so I sure did not have anything from them that could have caused this.
If you're wondering whether it's Zynaptiq or Pace, well, then it's Pace.
Pace out.
I see you just edited your post and added AIR as an alternative culprit. Well, AIR has been on my iLok since a year now without any changes. Pace out too.
And I'm happy we contacted the developers. Sure hope they'll take action.
I didn't even know about Zynaptiq (written with a 'q') until this thread, so I sure did not have anything from them that could have caused this.
If you're wondering whether it's Zynaptiq or Pace, well, then it's Pace.
Pace out.
I see you just edited your post and added AIR as an alternative culprit. Well, AIR has been on my iLok since a year now without any changes. Pace out too.
And I'm happy we contacted the developers. Sure hope they'll take action.