iLok Service Breaks For 24 Hours, Causes Social Media Stir
PACE launched a new desktop-based version of their industry-leading license manager late Sunday night. Unfortunately, the new release left some iLok users with a bit more than “Zero Downtime.”
Professionals know to expect some degree of hiccups and incompatibility issues with almost any type of new software launch these days, but the new iLok license manager seems to have been particularly unready for prime time.
For those who were unlucky enough to find themselves downloading the new license manager on Monday morning, a bug caused some types of licenses to temporarily fail. This was especially a problem for users who had issues with their license for Pro Tools, which relies on iLok for startup.
Fortunately, within 24 hours, PACE had already clamped down on the issue, putting fixes in place overnight late Monday evening. Tuesday morning, service on the website was sluggish as the system updated and many users worked to fix their issues, but at least a solution was in place.
I decided to take iLok at their word and risk my own personal authorizations for the sake of this write-up. After testing early Tuesday afternoon, I’m happy to report that despite the issues on Monday, the new system is now working pretty smoothly.
I did find that connecting to the server took longer than in the past. Instead of syncing within 2 or 3 minutes, it took more like 10 or 15. (I stepped away from the computer and a quick snack and by the time I was back, the sync was done.) My first attempt at starting Pro Tools was buggy, but a simple restart took care of that, and I’ve been up and running without issue ever since.
For iLok clients who updated their system within the 24 hour window when there was a major issue, PACE recommends the following fix:
Steps you need to take once you see the license type of “License” instead of “Temporary”:
- If your iLok with the license had not been seen by the server, just the updating of the database record for your license will take care of the issue.
- If your iLok had been seen by our server and your license is no longer working, please plug in the iLok and deactivate each of the affected licenses. To do this, open the Detail pane, then select the license from the license grid at the top. Choose the Deactivate link. Once the licenses are deactivated, you may then activate it to any allowed location.
If you are still experiencing difficulties please use this link to contact us and we will work with you to fix your issues. We are monitoring our support tickets closely during extra long hours to right matters.
Some users who updated that first day report that they have also had to go through a tedious process of deleting corrupt files from their machines. To those who updated on the first day, iLok offered this public apology:
“We have let you down and we know it. We could have done a better job communicating that we were hard at work to fix the issues some of you have been having and for that we are truly sorry.
We handle tens of millions of licenses for users, some stretching back over a decade with legacy code. Whilst we have worked to ensure a seamless transition, some issues occurred.”
Fire at the Water Cooler
They say good news travels faster than bad news on social media. But warnings seem to travel even faster still.
Almost immediately, the story of iLok’s rocky launch began to spread through forum postings, and even more rapidly, through shares on Facebook and Twitter.
One popular messageboard already has 12 pages of fervent posts about the issue. (Oh, wait. Make that 13.)
But despite the clamor on the web, a representative from PACE confirmed for us that only a small number of users were affected:
“All of our support tickets to PACE on this issue totaled less than 75 and some of those were duplicates,” he said. “We strive to answer all support tickets as quickly as possible.”
That number seemed surprisingly small to me, especially when compared to the pitched tenor of criticism on the web. I wondered how many total users there were in the iLok system for a sense of scale:
“Total users/accounts in the system… just shy of 1 million. Tens of millions of licenses moving around, and that number grows exponentially,” he said, adding, “Yes, 75 is a small number but any number is unacceptable to us.”
The Critique
Despite the actual service outage which may have ruined a day’s worth of work for scores of users, PACE’s biggest problem following the launch of the new license manager may have been lack of communication.
After the newly-introduced system was known to be experiencing issues, no message appeared on the company’s website advising that new users hold off from installing until the issues were resolved. The company seemed to take no initiative in making their customers aware of the issue, or of its timetable for completion.
This, coupled with the fact that the iLok website lists no contact information, is probably central to why PACE seems to attract such a significant amount of schadenfreude, despite offering a fairly reliable and reasonably-priced service that supports most of the major software developers in the industry.
Consumers, especially in the music world, just don’t feel very warmly about companies that seem like faceless monoliths. (Even if they so readily buy and rely on their wares without even thinking much about it.)
Of course, professional users know to never (as in never, ever) upgrade essential software either the first week it’s released (much less the first day) or immediately before a session.
With that in mind, many of iLok’s core users may be willing to accept a 24-hour startup SNAFU. But in the Internet age communication is expected. And it’s expected immediately.
Steven Slate, whose company relies on iLok for piracy protection, stepped up to issue a public statement of his own:
“I think PACE should have been much more up front yesterday in acknowledging the problems, and I’m glad that today they have finally taken measures to do so. That of course is not enough consolation for those who were unable to work yesterday. But at least it shows that they are taking some positive steps to communicate.
I can relate to PACE because like them, we are a small technology company that is trying to make a good product…Clearly, the system migration wasn’t tested enough before going live. This was a mistake, and now PACE, and anyone who is having problems, are paying the price for it. However, I can attest that fixes are already in place, and deactivating and reactivating licenses that say temporary seem to solve all issues.
Even before this new iLok client update error, there seemed to be an aura of hate against iLok and I truly don’t understand why. Because the iLok is the most convenient thing on the planet and I can’t live without it. And I’m talking as a USER now – not a developer. With the iLok, I never had to worry about switching systems, bringing plugins to other studios. I would be back into my session with all my plugins in minutes…
What happened yesterday is a real tragedy. But I hope more people will be forgiving, especially since in less than 24 hours there is already a solution, and realize that PACE isn’t the enemy. The enemy is SOFTWARE PIRACY. If you’re gonna be really angry at someone, be angry at the guys who are careless about the years of work and dedication from software developers and demolish their products by removing the much deserved revenue streams that they need to keep afloat.”
Personally, I like, use, and respect iLok as a product – exven if I have had to begrudgingly accept that PACE is a small, Web 1.0-era type of company that likes to systematize and streamline customer interaction, keeping the consumer at a bit of an arm’s length.
Perhaps this experience will teach PACE that customer interaction is crucial in this day and age, and particularly in this small industry. (Even if it does cost good money to fund a more accessible customer support or PR team.)
With new piracy protection systems from The Plugin Alliance and Waves becoming significant players in the field, PACE may finally have a real incentive to step up iLok’s game on that front.
Fortunately, the company already appears to be listening. This new license manager, which had such an unfortunate launch, is actually a direct answer to market demands and pressure from their competitors:
For the first time, users will be able to license iLok protected software directly to their machines – with no dongle necessary. Yes: iLok has finally gone ahead and taken the iLok out of iLok.
(Of course, not every plugin developer may choose allow this option, due to the increased security risk that goes along with any machine-based authorization system.)
They’ve also added a much-requested “TLC” option to their “Zero Downtime” coverage, which will officially insure lost and stolen iLoks for the first time.
So it’s clear that PACE does hear the market. They just have to do an even better job about responding to it in the future.
Justin Colletti is a Brooklyn-based audio engineer, college professor, and journalist. He records and mixes all over NYC, masters at JLM, teaches at CUNY, is a regular contributor to SonicScoop, and edits the music blog Trust Me, I’m A Scientist.
Please note: When you buy products through links on this page, we may earn an affiliate commission.
Nihilist
June 11, 2013 at 7:57 pm (11 years ago)ilok suck. 20 year old drm, on a dongle. meh. and avid makes it worse with protools 11…. you have been warned…..
Ehren Ebbage
June 14, 2013 at 6:26 am (11 years ago)Hi Justin,
While I would agree that the changes to the license manager seem like steps in the right direction, the rollout of their new system has been a mess and their handling of the situation has been horrid.
You were lucky to have had minor issues. For some people, including myself, the issues were major and remain unresolved.
I write music for TV for a living. I use Pro Tools and depend on it to get my work done. I upgraded my studio computer last week and needed to install software over the weekend. There was absolutely no indication on Pace’s website that there may be issues with the new manager and, as there was no option to use the old system, I installed the new ilok software.
It didn’t work. Not even remotely. I tried uninstalling the manager and I couldn’t even do that. I spent hours and hours troubleshooting. I found the ilok support email address hidden on their website and started a support ticket. Their response was a form letter with no information or suggestions. I wrote back and their response was a longer form letter with no information or suggestions. I wrote a third time asking for help and have received no response.
This situation is in no way resolved. Gearslutz forum members still report being stuck and Pace is not responding to their emails. Some users seem to have found solutions and some, like you, report having only minor issues, but there are people still left in the dark. You are reporting that the issue was resolved within 24 hours but that has absolutely not been my experience.
I understand that you walk a fine line in your position as an industry web writer. Still, perhaps due in part to your personal experience, your story leaves the impression that the issue wasn’t that big a deal to begin with and that it has been fixed. Pace made a MAJOR error and has done a horrible job of supporting its customers, and it is not over yet.
When you say “Of course, professional users know to never (as in never, ever) upgrade essential software either the first week it’s released (much less the first day) or immediately before a session” you disregard the fact that Pace offered no alternative. Anyone making a minor upgrade (like me), anyone buying a new plug in, anyone selling old plugs on ebay, etc. was REQUIRED to download the new ilok license manager. There was no alternative. Are you really suggesting that all sales, upgrades and installations of plugs should have come to a complete standstill while Pace tested out their new system?
I, as a professional user, rarely upgrade to an unproven product, whether it’s a plug in, an interface, an OS, etc. In this situation, however, there was absolutely no alternative. Had I known Pace was overhauling their system to this degree I may have waited a week to install my new computer. But there was no warning, no indication, and once I started down that road there was no turning back.
You are reporting based on your own experience, which is fair enough. I, as a professional user, want to offer another perspective and give a clear warning to your readers: The issue is unresolved and if you are affected Pace will not help you sort it out.
Thanks,
Ehren
MapleGuitar
June 14, 2013 at 11:00 am (11 years ago)My experience this week is exactly like Ehren Ebbage’s description in his comment: the problem is NOT resolved. My studio has been down the whole week as a result of the new iLok License Manager trashing all the licenses on my iLok. Like Ehren says, it’s a major problem, it’s unresolved, and it’s a whole lot more than a “social media stir.” Pace has been completely unresponsive to me, and apparently many others. The notion that only 75 people were affected is total deception.
June
June 14, 2013 at 12:20 pm (11 years ago)Woah! You wrote, “For the first time, users will be able to license iLok protected
software directly to their machines – with no dongle necessary.” I can’t find confirmation of this on iLok’s site but it would be amazing! Where did you read that?
Ehren Ebbage
June 14, 2013 at 5:07 pm (11 years ago)Hey Justin,
Not to belabor the point, but your article is misleading. As of right now ilok is still not functioning properly. They promised a working update to the license manager but have not delivered. They’re not responding to support requests and the list of affected users seems to be growing. You may want to consider writing a follow up, or at least revising this article so that it doesn’t suggest that the issue has been sorted out. It most definitely has not.
TrustMeI'mAScientist
June 15, 2013 at 8:23 am (11 years ago)Hi Maple,
So we know, were you first affected on the day of the launch, before the system fixes were implemented, or afterwards.
I’ve heard of several users who were affected that first day, and are still having trouble resolving the issue. If you were affected sometime after Monday and are having major problems, we’d like to know about it!
I also agree that it’s entirely possible that more than 75 users may have had an issue but just didn’t contact tech support.
To those users, I’ve got to say: Contact tech support! 30-page threads in web forums are likely to just get your blood pressure up further without solving the problem.
For a their major faults in this, iLok do seem to respond to tickets fairly quickly. Again, if you have experienced that this has not been the case, please let us know!
Thanks, and I’m sorry to hear about the trouble. It must be really aggravating.
TrustMeI'mAScientist
June 15, 2013 at 8:30 am (11 years ago)Thanks for writing in Ehren. I understand where you’re coming from, and hope the issue is resolved quickly for you. It must be frustrating.
I understand that many people who updated Monday are still having problems.
After updating on Tuesday, I did have a slight bug the first time I opened, but a quick restart fixed that for good. And I have hundreds of authorizations that could have gone wrong.
My concern with threads like the one on GS is that the gross effect is that they encourage people to get madder, instead of trying things that may help.
Am I the only one who updated on Tuesday for whom a simple restart would have solved the problem? Maybe, but it’s doubtful.
For those who updated Monday and are still having issues, my heart goes out. It must suck. I’ve heard that many users have since fixed the problem, but I’m sure that “many” does not mean “all.”
I think users like you should get ZDT free for a year, at least.
TrustMeI'mAScientist
June 15, 2013 at 8:34 am (11 years ago)It’s an option that’s built right into the new license manager. I’m looking at it right now. It will be up to individual developers whether or not they choose to use the option.
iLok expects that devs may only use it on their lower-end products, as machine-based authorizations — from any company — are not nearly as secure as iLok2.
TrustMeI'mAScientist
June 15, 2013 at 8:57 am (11 years ago)Hi again Ehren,
I understand that you’re still having issues and I think that sucks. iLok owes you — bigtime.
With that said, if you know of any users who updated *after* Monday and are having huge issues that can be traced directly to iLok, then please have them let us know!
I do understand that users who updated on Monday may have been unable to resolve the issue and could still be affected. I wish the article had made that even more clear.
But here’s the remaining question: If *new* installs are having major issues that aren’t fixed by a simple restart, then that is definitely worth knowing.
I have just not yet had clear confirmation that users who updated *after* Monday are having widespread iLok-related issues — Even from the Devs whose products were most affected by the issue.
I’m not saying it hasn’t happened. I’m just saying we’d just need clear confirmation in order to print something like that. And I don’t.
For all the much-warranted griping, and for all the people who’ve been sending me emails directly on the issue, I just do not yet have confirmation of widespread persistent issues for users who installed after Monday.
Obviously you’re in a different boat. And that boat must really suck. I think you have every right to complain. I’m sorry that in your case the first-day install needed to happen, and I hope you recover soon.
For the record, I still think that anyone reading this should hold off
on an install, despite the fact that mine and many others are now working perfectly. It’s
just too early and too essential of a program to take the risk.
Ehren Ebbage
June 15, 2013 at 9:21 am (11 years ago)Thanks for your response, Justin.
As of now my rig seems to be working but I dare not fool with the manager for fear of losing my licenses again.
There is certainly a lot of needless ilok bashing on GS. The thing is, the thread you are referring to was the ONLY source of info and suggestions I could find for the first few days. Some forum members found solutions, posted their suggestions, and offered to help others. Pace offered nothing.
I used the manager on the first day it was available out of necessity. I contacted their tech support twice and got no support whatsoever. They responded with unhelpful form letters both times which directed me to their website, where I found the same exact text they sent in the form letter. I followed up a third time and, two days later, they still haven’t responded.
I honestly don’t want or need them to give me anything other than a guarantee that they will make whatever adjustments are necessary to prevent this sort of thing in the future. There will always be buggy software and mishaps. But there is no real excuse for the lack of support and communication in this situation. These sorts of problems will inevitably arise, but if Pace is unable to handle them, perhaps developers should look elsewhere for license protection.
Either way, Pace did not resolve the issue in 24 hours, they have barely been responsive let alone helpful, and their mistake resulted in thousands and thousands of dollars in lost income for their clients and users like me.
So, respectfully, your article is misleading.
Thanks again,
Ehren
Palace of Sorrow
June 15, 2013 at 10:13 am (11 years ago)I install on monday so i could use new plug ins i purchased over the weekend. Have been down ever since. Have sent in several support requests to ilok and received only a form letter. Have un/reinstalled ilok software about 15 times this week. Have restarted my machine everytime. Tried diff usb ports and a diff machine. Nothing works. Have lost a few hundred $ this week. And have several upset clients. Even had some new potential clients inquire but had to put them off. But for how long. Never had issues with ilok before. Cant get pro tools to open. So i can’t check the other plug ins
Windows 7
Rain solstice
Pt 10 hd native
June
June 15, 2013 at 10:43 am (11 years ago)OH. 🙁 Thanks for the info. That is a different impression than the article gives – Justin, I’d recommend a correction in the article.
elicho
June 15, 2013 at 10:50 am (11 years ago)I made the update 3 days ago (not on monday !!!). after that the chaos started. all my 155 licenses are useless. I cannot open projects that are in work. Even Pro Tools doesn´t start. I had to terminate scheduled projects of my clients and lost a bunch of money. no response from Pace instead of autoresponder messages. No contact hotline. The so called Zero Down Time, for which I´ve paid is completely useless and turns to a Full Down time. Today I got a message that they fixed it. tried – but same as before. Absolutely inacceptable.
All the best JF
TrustMeI'mAScientist
June 15, 2013 at 2:45 pm (11 years ago)Excellent to hear Ehren! Glad that it seems to be back up and running on your machine.
What ended up working for you? Was there a new patch, or was it a matter of deleting corrupt files from the Monday install?
I totally agree that PACE’s communication efforts have been extremely lacking.
With that said, I ‘d love to see the form letter you were sent to in order to get a better feel for just how bad. Did
it offer no solutions at all?
I’m only surprised because the few bits of useful information on that GS thread actually came
from PACE tech support. (The forum members didn’t make up all those fixes for themselves!)
We’ll have to agree to disagree about whether the article was misleading. What I thought was misleading was that GS thread — particularly the bits that came from non-users and bad actors with an anti-copy protection agenda.
(It’s actually not uncommon in situations like these for a few bad actors
to spread misinformation, flooding forums and tech support emails with
bogus claims in order to dramatically distort the scale of the issue. I’d imagine that’s part of the reason iLok has such a restricted support-ticket system, with no regular email allowed.)
From the perspective of an iLok user like me, who had no issue, the forum posts just didn’t provide needed context. They instead seemed to gleefully frustrate users further. And that just makes matters worse: Angry users are notoriously bad at working through errors on their machines — Even when they do have the full help of
tech support. I should know. I’ve been that angry user! (Haven’t we all?)
Again, I understand that you and a good number of other users had a real problem and genuine concerns. And I know that users who updated on Monday would have to go through extra steps (in some cases many tedious steps) in order to get back up and running.
I thought the article made that clear, but I can understand how that may seem different from the perspective of a person who was caught in the middle of a real problem.
But I wasn’t writing to people in your situation. That’s iLok tech support’s job. (And I’m sorry they screwed it up!) Instead, I was writing to the other 999,000 unaffected iLok users to give them a fuller understanding of the bigger picture of what was going on and what they should do next.
In any case, I’m glad to hear it’s working for you now, and hope you don’t have to go through something like this again anytime soon, with PACE or with anyone else. It really sucks that you had to go through this, and I wish you the best from here on out!
If it were up to me, your ZDT would be refunded for the year, and offered as a free courtesy next year as well. Unfortunately, that’s not my call to make. For the both of you, I hope PACE makes the right decision.
Best wishes,
Justin
TrustMeI'mAScientist
June 15, 2013 at 2:53 pm (11 years ago)I’m sorry to hear that, Palace. Did you go through the steps to remove corrupt files from your machine that accompanied the Monday install? And did iLok not send these steps to you directly?
Here is one solution for Monday installs that has been making the rounds — Try a full client-side (Mac) reset:
1. Open the LicenseSupportInstallerMac_v2.0.0 disk image:
http://installers.ilok.com/iloklicen…LicenseSupport InstallerMac.zip
2. Run the “Uninstall License Support” application
3. Drag the following items to the Trash:
• Macintosh HD > Library > Preferences > com.paceap.eden.clientdb.v1.01.sdb
• Macintosh HD > Users > your_user_name > Library > Caches > com.paceap.iLokLicenseManager
• Macintosh HD > Users > your_user_name > Library > Preferences > com.paceap.iLokLicenseManager.plist
4. Restart your Mac
5. Open the LicenseSupportInstallerMac_v2.0.0 disk image
6. Install the iLok License Manager software
7. Restart your Mac (yes, another restart is required)
8. Open the iLok License Manager application
9. Click “Sign In” and login with your iLok credentials
10. Click on the affected iLok icon in the left sidebar
11. Select ALL of your licenses
12. Select “Deactivate” from the “Licenses” menu (this moves the licenses back to your user account)
13. Click “OK” to confirm deactivation
14. Click “OK” on the successful deactivation prompt
15. Click on your User icon in the top left of the iLok License Manager
16. Select ALL of your licenses
17. Click and drag the licenses to the iLok icon in the left sidebar
18. Click “OK” to confirm activation
19. Click “OK” on the successful activation prompt
20. Test the affected software/plug-ins
I have not tested this myself, but other users I know have, and have confirmed it was a fix for them.
I hope this works for you. I’m amazed that iLok has not responded since Monday. That seems to be out of the norm based on my experience and the users I’ve been talking to.
Good luck and let us know if this works!
TrustMeI'mAScientist
June 15, 2013 at 2:58 pm (11 years ago)I’m sorry to hear that elicho. If you ask me, your ZDT should be refunded, and you should get an additional full year of the service as a courtesy.
Pace definitely does not have a contact hotline. If they did, it would probably be inundated with prank phone calls from pro-piracy trolls.
I’ve heard from a few users who installed after Monday and have had issued, but in each case a simple Sync/Repair and restart has been successful. The major issue for them was been getting sync happening in the first place, due to high traffic issues.
(Part of me wonders if there has been a coordinated DoS attack, but it could easily just be unusually high traffic volume, or server migration issues.)
If a restart and re-sync doesn’t help, please see the steps above, sent to “Palace of Sorrow”, and let me know if they work for you too.
Palace of Sorrow
June 15, 2013 at 3:07 pm (11 years ago)On a pc windows 7 rain solstice.. I have gone through folder looking for pace/ilok files and deleting all of it and reinstall. Same results. Thanks
Ehren Ebbage
June 15, 2013 at 3:59 pm (11 years ago)Hey Justin,
Thanks for your response. I appreciate the time you’re taking to address your readers’ concerns.
I sent my whole email conversation with ilok to info@sonicscoop.
I suppose it hadn’t occurred to me that anti-anti-piracy folks would fan the flames but I see now that it is a possibility. Still, there are many long-term forum members with legitimate claims and concerns. Also, if your guess is correct, I think it’s bad policy to limit customer support because there is some potential for illegitimate claims. There are lots of Reaper fans on the forums but I doubt they would go out of their way to flood the Avid support line just because they dislike Pro Tools.
I can’t say for sure what brought my rig back to life. I wasn’t able to follow the steps posted because I got error messages every time I tried to uninstall. I did lots of rebooting, tried the ilok in different ports, etc. That’s about it.
Thanks again for taking the time, and for doing so in such a reasonable and polite way.
Ehren
TrustMeI'mAScientist
June 15, 2013 at 7:18 pm (11 years ago)Thanks Ehren,
You have a lot of good things to say here. So thanks again for weighing in.
I’ll definitely check out that correspondence — I’m very curious as to how they’re handling this stuff with different people.
From what I’ve seen so far, they could obviously be doing a lot LOT better. They definitely need to hire on some new people who really get the customer support and interaction side of the business, and can overhaul their whole approach on that end.
If we get enough more good info for another story, we’ll definitely do a follow-up.
Thanks again, and here’s to a less stressful summer for you from here on out!
Best wishes,
Justin
John
June 18, 2013 at 11:09 am (11 years ago)iLok site is down or offline still. From several posts I read the problem is very much there. I have been trying for over 2 hours to get the license manager up but was complete failure.
TrustMeI'mAScientist
June 23, 2013 at 6:52 am (11 years ago)I’m not sure if you mean “correction”, because there’s nothing inaccurate in that statement. If the impression you got was “now iLok supports machine authorizations” then that impression is definitely correct!
You’re right to say that we add more context. In some cases, machine-based authorization may not be in developers’ best interests because of the inherent security risks with those kinds of systems.
But that’s a developer decision, not iLok’s. The same exact security risks exist with the Waves and Plugin Alliance machine-based authorizations.
Since this was an story about issues with the product launch — rather than about the new product itself — we decided not to go into as much detail on the software as we might in an actual review.
But we may do one of those soon. The new license manager actually offers a bunch of cool features. Once all this blows offer it could definitely be worth a second look.
PACE has even added a new feature to Zero Down Time called “TLC” — a cloud-based license option that allows the service to officially cover lost and stolen iLoks for the first time.
(Although to be fair, when I lost my iLok years ago, it was a cinch to get my licenses restored within a day, even without ZDT.)
Yeah — we didn’t really discuss the actual benefits of the update in this piece. (There are more than a few). It just didn’t seem like the right time. I’m sure you can understand why!
Thanks and be well,
Justin
TrustMeI'mAScientist
June 23, 2013 at 7:07 am (11 years ago)So far I’ve been in correspondence with close to a dozen users who were having connectivity issues. I’ve told each of them to do what I did:
“Start connecting, go away and have a bite, come back in 20 minutes or so.”
In every case so far, that has worked.
Connecting on the current system us taking significantly longer than with the old system. Instead of 2 or 3 minutes, it takes more like 10 or 15. (And the progress bar doesn’t seem to move at all in that time.)
I can certainly understand why that freaks people out and causes them to abort before the connection actually occurs. It’s slower than it should be and iLok has done a crappy job of explaining that you should simply leave it alone and step away from your computer for a hot minute. But it actually does work.
Trust me, you’re not the only one who has wasted hours syncing and aborting and re-syncing again and again, when simply connecting once and stepping away for a while would have fixed your problem completely. If iLok was doing their job right, you’d know that already. So shame on them for that.
If by “several posts” you mean random posts on internet messageboards, I’d be careful. It’s like the blind leading the blind, plus an army of undercover pro-piracy strolls adding smoke to the fire. The diamonds are buried deep down in that haystack.
Alejo
July 18, 2013 at 8:49 pm (11 years ago)if this only affected 70 users then why did Allen Cronce himself have to go on Gearslutz to apologize about the incident?
Mad
July 19, 2013 at 9:33 am (11 years ago)Justine: almost everything you wrote in this article is total b#%^^#%t. You sound like a paid pr person trying to puta spin on this. The new Ilok manager was never pulled down and please we’re still losing license week and 1/2 AFTER pace knew there were issues. It has been over a month and I still don’t have all of my licenses back. Furthermore I have heard developers are still having issues with the new system. There were people who lost gigs and one person who was laid off as a result of this.
Other than saying “i am sorry” what has pace done to date to compensate those people who lost income as a result of this…. Nothing.
You are brown nosing and spreading unthruths. Considering what me and way more than 75 people have been thru I would at least expect you to do proper investigative research before printing this.
To ad insult to injury, I have had at least 2 producers come to my studio and offer to “hook me up”. It angers me that their systems are working and mine is not. I’ve spent a lot of money to have a legit system and this is how I a thanked? Lastly to Steven slate…I think you are a cool dude and I like you but I question your defense of pace.
TrustMeI'mAScientist
July 19, 2013 at 10:32 am (11 years ago)There’s no way to say for certain that only 70 users were affected.
What we can — and did — say is that during the first two days, when the problem was at its peak, PACE reported that 70-some users had submitted requests for technical support.
It’s possible that some users had trouble and didn’t request tech support. (Which would be a bad idea!) It’s also possible that some new users had trouble after days 1 & 2 and that new tickets might have been issued.
Personally, I think Cronce and the people at Pace should have apologized for their handling of the transition whether 7 users were effected or 700. On that front, the number is irrelevant in my personal opinion. But it does help give a sense of scale.
On Gearslutz, the scale of the problem was overblown. No question about that. In PACE’s own statement’s they’re likely to downplay the severity of the issue. No surprise there either. The reality of the situation is likely to be somewhere in between.
I applaud your skepticism in regard to the company’s official remarks. But I’d also invite you to take that very same skepticism and apply it to the comments of a few dozen completely anonymous forum posters — many of whom have their own agendas to advance, and not even a pretense to accountability. Otherwise you’re just taking sides. I’m more interested in finding out what’s true.
TrustMeI'mAScientist
July 19, 2013 at 10:59 am (11 years ago)I’m sorry to hear your system still isn’t working. That must really suck.
All I can tell you is that I’ve never been paid a single cent by PACE for anything, ever. I’m just a user, and a person who’s skeptical of anonymous hearsay on internet forums.
As a user, I’ve had a good experience with PACE for a decade, even when I’ve broken or lost iLoks and even when I updated the day after the License Manager went live. As a reader of internet forums, I’ve become accustomed to every success and misstep being overhyped beyond belief or reason.
That’s not to say that no one has ever had a problem with iLok or any other piece of software or hardware. If you’ve had a real problem, my heart goes out. Seriously. Not being able to work sucks. I think PACE owes you, and any user who had a serious issue, *at least* free ZDT coverage for a year or two.
If you care to share your story, I’d love to hear some more context around your problem. Please email us anytime: Is there a problem with the software? Or do you have a legacy PPC system that’s not compatible with new iLok licenses? Is there are firewall issue that’s been impossible to circumvent?
At this time, I have not been able to verify any new or widespread issues with the License Manager program itself. I have also not been able drum up any evidence to suggest that thousands of users have been affected at any point. (Hundreds, I might believe.) ((Please Note*: repeated anonymous posts on Gearslutz are not “evidence.” But if you’ve got facts, I’m wide open — Always.))
So again: If you have any evidence or reliable reports on either of these fronts, I’d be eager to hear more! If so, please get in touch directly. This is important stuff. There’s a contact link at the bottom of every page.
Shaun
December 11, 2013 at 7:34 am (11 years ago)It is December 11th, 2013, I am a fairly new PT user and clearly the iLok crash is still an issue since I am now on this page. For the past few weeks I’ve randomly gotten error messages that state: “Pro Tools does not recognize licenses.” I then would sync/repair the licenses and it would fix temporarily. Now the iLok download manager will not even open. I receive a blue error window stating: “The wizard was interrupted before PACE License support Win64 could be completely installed. The system has not been modified.” Online instructions suggest to clear the drivers and do a clean install. I’ve done it all with reboots. So I just spent over $300 on the Ivory 2 Grand Piano VST, I spent the 3 hours it takes to install the 11 discs, yet now I can’t even put my license onto my iLok and play with my new software. I can only imagine the frustration and destruction of business this has caused for the more in-depth professional users. Does anybody have any suggestions for me? I’ve put a “ticket” in to iLok, I doubt they will get back to me after reading all these comments.
Justin Colletti
December 12, 2013 at 7:54 am (11 years ago)Shaun, this sounds like an issue not related to the switchover trouble from months ago. In my experience, Pace is usually pretty fast about responding to support tickets, especially under normal circumstances. Please let us know how it goes.
Bob Verb
August 5, 2014 at 6:38 pm (10 years ago)iLok tech support has been the absolute WORST is helping me resolve my iLok not being read. The iLok manager has NEVER worked. The tech support are completely inept and could really not care less about listening to my problems in helping me resolve my issues.