When I finally replaced my 9-10 year old PPC G4 iMac last month with a 2010 MacPro, I thought "all my problems would go away".
Well, they did, with one glaring exception: eLicenser hiccups!
Maybe going from a behind-the-times machine to an ahead-of-the-times machine put me outside the range of Steiberg's "commitment" to the Mac? :-)
Whatever the case, the latest update to Mac OS X Snow Leopard (I could never go past Tiger on the 700 MHz iMac), which is 10.6.5, MAY have corrected the problem, as I miraculously have have a week's worth of sessions now without a single eLicneser hiccup.
I tried to make things better by off-loading most of my download library licenses to a separate eLicenser key, but I still have upwards of 40+ licenses on the main key (the other one is in storage as those licenses are redundant vs. the DVD collections).
When I set up the new key, I actually moved my most important licenses to that key and left the unused ones behind on the old key. Everything went great until I got to around 20 licenses. Then I started getting the familiar "license not found" errors mid-session, only correctable by rebooting the computer.
There is a new iLok on its way right now, but I haven't read all the details yet about whether it supports 64-bit apps.
At any rate, the most obvious thing VSL could do to help, is to offer consolidated licenses to people who own big chunks of the library. Maybe an all-brass license, etc. I guess the tricky thing is that this might get complicated if more instruments in that category are added later.
I've kept my computer on for several days now, which is something I NEVER did in the past. One of the reasons (not the least of which is flakey power in my region), was that "stale" sessions were the most frequent cause of eLicenser troubles.
So I keep my fingers crossed that my sessions will go well today. VSL isn't all that I have on that key: the Eiosis plug-ins, a few soft synths, and one or two other vendors are on that key as well. All have the same problem as VSL licenses.
The Vienna Suite licenses, for some reason, have flagged the error far more frequently than Vienna Instruments. I have no idea why that woulkd be, other than that maybe it's because Vienna Suite uses several licenses, whereas each Vienna Instruments instance presumably only has to look up the license for the library that is being loaded?