iLok License Manager

[Shooshie]

Anybody know what's up with the new iLok License Manager application? I downloaded it -- which appears to be the only way you can do the things the website used to do -- and opened it. it opened without text. All the windows are there, but there is no text inside. It's not just the background color; if it were that, you could select the "invisible" text and see it highlighted. This has nothing in it! No text, no instructions, no labels… nothing.

I guess I should be writing this letter to Pace, but I thought maybe there was something I missed over the past month or 6 weeks, having been kind of off-grid for that time. Maybe you all already know about it.

If not, I'll just send this to Pace and see if I can figure out what's going on. And if this is the first you're hearing of any of this, then you might get on it, too, as it looks like we're up •••• creek without a paddle until we get this app working. I cannot find any place on the website that will allow me to download and activate a license. If a vendor has sent you a license, it shows up in your list, but it shows up unactivated. Apparently I have to use the app to activate it, but since the app has no text, that's going to be hard to do.

Will keep you posted if I learn anything. Likewise, please tell me what you know.

shoosh

[NazRat]

I've read about several issues with the new iLok LM, but haven't seen that one yet. I think you're a fan of Spaces/Expose - maybe something up with that. Spaces seems to cause some quirky UI issues with some apps.

[buzzsmith]

This is why I'm still "scared" to install my new Ivory update. I can't be down right now!

Buzzy

[bayswater]

I downloaded the new licence manager for the first time about a week ago, waiting as long as possible because of the reported issues. It worked perfectly. A bit of confusion at first while I figured out how to log in (it does still contact the iLok site), and get the listings of licences and what is on the key. Nothing appeared initially on launch, but there was at least a few places to click to get things started.

If there is absolutely no text anywhere when you run it, it would seem the resource files are missing. Perhaps your download was not complete or was corrupt. Did you try uninstalling and downloading again?

[twistedtom]

I used it the other day and it worked fine. Today I got some new software and it did not work, it said I needed to down load it again, so I did; it worked fine then. Try down loading it again, you will need to log in using it. Maybe the next time it will remember you.

[Shooshie]

Well, I worked on it literally all night, reinstalling, restarting, Safe-Booting, repairing permissions, and all the tricks we know to do. I read the log and noticed that it was having issues with fonts.

I went to the FontBook utility and resolved some font conflicts and had it automatically resolve all duplicate fonts. Went back to iLok License Manager and this time I had labels, but still no content text. Again, I went through the litany of procedures that we try, even if they rarely work. Still, no content text. By this point I could see that it had five slots representing the five iLoks which I've used over the years.

I went to Pace's website, where I searched in vain for a way to report this. Finally, I repurposed one of their other support tech links for some product of theirs, and used it to describe my problem. I sent it to them.

Immediately after sending my report to Pace, I went back to the iLok License Manager, and LO! We had CONTENT! It had been open in the background when I went to the Pace website. I cannot help but wonder if there was some link between my sending the support tech link and the sudden appearance of content. I'd logged in correctly a dozen times, so I know it had nothing to do with my logging in; in fact, I cannot think of anything that I could have been doing wrong, and no detail had I overlooked, no procedure had I neglected to perform, all to no avail. But the moment my support issue hit their site and i got acknowledgement that it was sent, suddenly the content appeared.

Well, I really don't have a clue as to why it started working. The above was more likely sheer coincidence, but it makes you wonder just how all this stuff is connected, and by what means they monitor your iLok and your actions on their website. I mean, the timing could not have been more perfect. I clicked the send button on their support link page, it sent, and the content started pouring in.

First, it only gave me about half the content I could see on their website. Alphabetically, it stopped in the "H's" somewhere. I clicked around in it, and pretty soon the rest of it came pouring in. It's all there, now. Er… I think. I haven't reopened it since early this morning, when I finally quit and went to bed.

So, there's the story.
Shoosh

[Shooshie]

For anyone interested in seeing the relevant parts of the crash reports I sent to Apple, here they are. You will notice a lot of FONT related activity in the crashed thread.

Shooshie

Code: Select all

Process:         iLok License Manager [430]
Path:            /Applications/iLok License Manager.app/Contents/MacOS/iLok License Manager
Identifier:      com.paceap.eden.iLokLicenseManager
Version:         2.2.1 GM [b1094, r23238] (2.2.1.1094)
Code Type:       X86-64 (Native)
Parent Process:  launchd [244]
User ID:         501

Date/Time:       2013-09-21 06:29:21.238 -0500
OS Version:      Mac OS X 10.8.4 (12E55)
Report Version:  10

Interval Since Last Report:          1021856 sec
Crashes Since Last Report:           85
Per-App Interval Since Last Report:  3599 sec
Per-App Crashes Since Last Report:   5
Anonymous UUID:                      B3D3EB4A-685E-429C-CE00-BBF770FD27CF

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
*** CFRelease() called with NULL ***

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.CoreFoundation      	0x00007fff95166208 CFRelease + 40
1   QtGui                         	0x0000000100ccb9b6 paceQt::QCoreTextFontEngine::~QCoreTextFontEngine() + 54
2   QtGui                         	0x0000000100f03ab2 paceQt::QFontEngineMulti::~QFontEngineMulti() + 114
3   QtGui                         	0x0000000100ccdea2 paceQt::QCoreTextFontEngineMulti::~QCoreTextFontEngineMulti() + 66
4   QtGui                         	0x0000000100efbc5a paceQt::QFontCache::clear() + 202
5   QtGui                         	0x0000000100efbe21 paceQt::QFontCache::~QFontCache() + 33
6   QtCore                        	0x00000001005e0d16 paceQt::QThreadStorageData::set(void*) + 182
7   QtGui                         	0x0000000100c9a204 paceQt::qt_cleanup() + 180
8   QtGui                         	0x0000000100d13018 paceQt::QApplication::~QApplication() + 1128
9   com.paceap.eden.iLokLicenseManager	0x0000000100070082 non-virtual thunk to boost::exception_detail::error_info_injector<boost::system::system_error>::~error_info_injector() + 189214
10  com.paceap.eden.iLokLicenseManager	0x000000010001493b boost::exception_detail::error_info_injector<boost::thread_resource_error>::~error_info_injector() + 34271
11  com.paceap.eden.iLokLicenseManager	0x000000010000ea44 boost::exception_detail::error_info_injector<boost::thread_resource_error>::~error_info_injector() + 9960

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib        	0x00007fff91f48d16 kevent + 10
1   libdispatch.dylib             	0x00007fff8ffdadea _dispatch_mgr_invoke + 883
2   libdispatch.dylib             	0x00007fff8ffda9ee _dispatch_mgr_thread + 54

Thread 2:
0   libsystem_kernel.dylib        	0x00007fff91f46686 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff91f45c42 mach_msg + 70
2   com.paceap.eden.iLokLicenseManager	0x0000000100387111 boost::exception_detail::error_info_injector<std::out_of_range>::~error_info_injector() + 73775
3   libsystem_c.dylib             	0x00007fff8d0f27a2 _pthread_start + 327
4   libsystem_c.dylib             	0x00007fff8d0df1e1 thread_start + 13

Thread 3:: com.apple.CFSocket.private
0   libsystem_kernel.dylib        	0x00007fff91f48322 __select + 10
1   com.apple.CoreFoundation      	0x00007fff951d1f46 __CFSocketManager + 1302
2   libsystem_c.dylib             	0x00007fff8d0f27a2 _pthread_start + 327
3   libsystem_c.dylib             	0x00007fff8d0df1e1 thread_start + 13

[mikehalloran]

Having resolved duplicate fonts, a number of applications should work better for you. I have no idea if the new license manager is one of them. Finale users were affected a version or two ago by this.

[ignatius]

i thought pace had sorted out all the software issues??? wow. lame.

it's a sad state of affairs w/the iLok situation. sorry for your woes!

i still haven't updated the software for the 1 or 2 plug ins i have that use iLok.. i sold all the others to move away from it. i think i only have the free soundtoys plug ins left. i'll probably just dump it..

anyway.. sorry.. i haven't any advice to fix the problems other than persistence. hopefully the industry can come up w/a better solution for copy protection. i sure wish MOTU would abandon iLok. i'd buy machfive3 immediately.

[mhschmieder]

What the heck? I had no problems with the PREVIOUS updates over the past month or two, but suddenly tonight (my iLok software updated to accommodate iZotope RX3 earlier this week) I can't load SONNOX Sony Oxford plugs.

The iLok shows them as locked groups, with both G5 and UB versions. Isn't UB the one we should see on an Intel Mac running 64-bit mode? How come then DP only sees the G5 versions as available, thus re-triggering the problem (and an endless loop of OK or Cancel and then OK on MOTU encountered an error...). It says it can't find the license or the iLok isn't V2 (it IS V2).

I'm too tired to read more about the history of this problem at the moment, as I went a half year without needing those plugs so decided to just be patient and hope things were fixed by the time I needed them again. I used them right before Labour Day with no problems at all.

Oh, for crying out loud; I just tried my VBC demo since it expires tomorrow night and I haven't had a chance to evaluate it yet since I was at the conference all week. It too says no iLok found; yet the iLok app says it's there.

I tried RX3 and everyone knows it's hunky-dory. I guess this is a vendor-specific problem (Slate Digital, Sonnox Sony Oxford, maybe others...).