Hi snafoo, 

Also, connecting the key to different ports directly on your computer will help a lot (alternatively: use a powered USB hub). 

To reset all USB ports, disconnect all USB devices, power down your computer and wait for 2 minutes before restarting. 

Best,
Paul

Good day.

Thanks for the suggestions. This morning I opened up the session I was starting yesterday. I was happily greeted with only one error message this time:

eLicenser Control - Error Application 'Vienna Instruments (M6)' has caused the following error: Failed to send Getinfo command. " 

The session opened and I had access to all the VSL libraries. Yesterday I could only play the Spec Ed Vol1 plus. This is much better. Did some elves fix things over night? Regardless I can work w/ all the VSL libraries now. But there is still the error message which I do not like. Yesterday I spent frustrating hours trying to figure out a solution. I uninstalled and reinstalled the LCC and VSL software. With the dongle, without the dongle etc. And yes I did the maintanence for the key. But now, I would love the write some music, and later today I will go back to the LCC and attempt to stabilze things. I will report back with an update. I must say I have never had to think to about the LCC software before, it has always works behind the scenes fine., but this does happen on occassion. Thx for the support.

The funniest thing happened a few minutes ago. I have 2 elicensers I use for 2 VEPs I was using for VEP5 on 2 difference Macs with each other. Anyway I downloaded VEP7 a few minutes ago and installed it, first time I've had time to download it and install it.

And whenever it started all my dongles, to include my iloks began to flash. I was like WT crap!!! Then I started the elicenser app, everything was fine. So I restarted the VEP7 app and I get some error saying only one elicenser was working or something like that. Now I open elicenser app and it shows one of the elicencer dongle is bad!!!! WT Crap VIENNA!!!

They worked fine until I started VEP7, seriously, they worked fine!! LOL wow...

I will reboot and see what happens, maybe its a burp or hiccup or a bug....never had issues with any dongle or elicenser before today...

EDIT: WHOOOOOO Rebooting my Mac fixed the issue...WOW.....

Actually, I've gotten same problem twice in past 12 hours. eLicenser application on the same machine shows the dongle and the licenses on it, but VE7 insists there's either no dongle or no license or that there's an USB problem. Rebooting didn't help. USB ports on that machine work well with, say, iLok and other USB thingies.

What's really peculiar is that the dongle in question works fine in other machines, and the license can be removed like nothing, transferred out and back. Maintenance is done, so it shouldn't be that.

Maybe you've tightened the screw a little too much?

I have the same specs and had the same problem (mentioned in another thread). At the moment it all runs smooth.

For me it helped to update all of the software, including the elicenser. 

Everything updated, and I just had the Mac inspected by an official repair center, just in case. All good. I'll continue testing whilst working.

I hope this isn't a "legit users suffer because idiots exist" issue. :-D Instead, I'd like this be a "wow not all people should be using computers because they just can't" issue.

I've been troubleshooting this. It seems all other USB dongles behave well - except eLicensers. I've tested five different license keys, and each gives me the same license nagging. Pressing "Retry" in the dialog screen a few times finally opens up the application and it seems to work normally after that.

Vienna people, is this VE7 specific or eLicenser specific? How to debug/troubleshoot?

I said I would back to the eLCC and attempt to stabilze things. But I went to work had one more error message and no more error messages. The eLCC can see the dongle and things are working so I am leaving things for now. I have no clue why it works now but refused that first day. I spent a few hours scratching my brain, updating, then uninstalling, reinstalling, etc. Unfortunately I am not sure what the solution was. Ghost in the machine. Thanks for the replies everyone.

Hi VSL,

Same error problem here with elicenser, never before with VEPro 6

VEpro 7 very crashy for me,with e licenser stuff

why it takes soooo looong to scan plugins ?

Regards

Hello everybody,

We know that our friends at eLicenser are working on improvements for upcoming versions and are also hoping that these confusing messages will disappear.

This seems to affect the 64 bit version of eLicenser only.

Here is a link to the 32 bit version of eLicenser for macOS - let me know if that helps!

Best,
Paul

"This seems to affect the 64 bit version of eLicenser only.

Here is a link to the 32 bit version of eLicenser for macOS - let me know if that helps!"

Paul - are u saying that we should un install elicenser app and install this 32 bit version?

Hi,

Sorry if I was unclear. Yes, please uninstall the current eLCC and try with the 32 bit version.

Best,
Paul

Things went strange with Vienna and eLCC again yesterday. I installed the 32 bit version as you suggested Paul and things are smooth so far.

Thx

I've solved most of my issues with eLicenser not found by using a powered USB hub.

However, I still have, more than a few times, a message saying that the eLicenser can't be found. I can simply solve this issue by clicking Retry, and everything works fine.

Not pleasant, though.

Paolo

Hi Paolo, 

Thanks for the update. Is that also the case with the 32 bit version of the eLicenser Control Center?

Best,
Paul

Paul, thank you very much for the hint of using the 32-bit version. Since 32 bits are deprecated on the Mac, I prefer to wait and see if the issue will be resolved in the 64-bit version. At the moment, I can live with the error message.

Paolo

Hi just putting my hand up here, same litany of eLicenser errors...most inconvenient. In our case clicking

the alert dialogs away made no difference, just led to more errors.

edit - uninstalling 64bit elicenser and installing eLicenserControl (6.11.3.1244) 32bit seems to fix it.

Ouch! what the hell?!

Hi, 

Glad to hear that the 32 bit version fixes these troubles. 

eLicenser/Steinberg is working on finding the culprit in the 64 bit version. 

Best, 
Paul

Fyi tried with current eLicenser (6.11.6.1251) and new VEP7, still no go..same errors.

I'm all for developers protecting their software, but the moment it inhibits the free flow of work it is a very bad look...hope you find the bugs soon!

Hi grooveq,

Yes, no fixes yet in the new eLCC software, unfortunately. Did you try the 32 bit version?

Best,
Paul