Hello Dorico team,
I hope you are doing well!
I already reported this issue in the Cubase forum, but didn’t get any feedback from the team. Unfortunately they are not to much into
interaction with the customers, so I don’t expect anything from them.
I hope you could be able to do something this problem to be solved!
Here is the link to the original report:
After the eLicenser Control error appears Dorico’s “No Valid License Found” dialog:
I’m using the latest version of eLicenser Control Center app - 184.108.40.2068.
This bug also affects the Vienna Ensemble Pro 7 app:
Thank you for the reply! Yes, when I start eLicenser Control Center first I can’t start Dorico then. The same error appears. But I can start Cubase 11.
The problem with VE Pro 7 still remains…
If I don’t open the eLicenser CC first I can open Dorico, but only before Cubase 11. The only way to launch Dorico again after Cubase, or eLicenser CC is to restart the PC.
When Dorico is launched firs, and I try to start Cubase 11 secondary it appears as background process in the Task Manager, but the app doesn’t really appear on the screen. When I’m trying the same scenario with Dorico - first and Cubase 10.0.60 - secondary everything works as expected
Everything was fine before the upgrade to Cubase 11 and the latest eLicenser Control Center.
It could be something related to “Run as Administrator”?!
It can’t be something specific to my setup, since I did change nothing. The only thing I did was the upgrade from Cubase 10.0.60 - 11.0.0 via the grace period, because I bought a license for 10.5 during the summer sale.
I did eLicenser CC Maintenance during the period when the problems with licensing servers were, and it didn’t pass well, but I did it again after that and passed OK.
I hope this can be solved somehow, but I can’t do it myself!
Ulf, thank you very much! Now, with the previous eLCC, everything is alright.
Just if I start eLicenserCC first I can’t start Cubase, nor Dorico, nor VE Pro.But as soon as I close eLCC I’m able to launch and have them all simultaneously on my screens.
Obviously something is wrong with the latest eLCC.
Glad to hear, but somehow it’s just a workaround, but at least it works…
On the other hand, it’s not a general issue, because here on my machine it works, also with the latest eLC. So I really wonder what the underlying problem is.
Well, if I can help somehow… feel free to ask me for whatever you need. This is the very first time I’d experienced problems with the eLCC.
I am a Steinberg customer since March, 2014.
More about my system you could find in the signature section below.
I hope you are doing well and everything is alright there!
I would like to ask you something about the eLCC.
I did new test with the latest eLCC - 220.127.116.119. Unfortunately I’m getting the same problem as with the previous version - 18.104.22.1688.
Is it possible the problem to be related to the version of Windows 10 Pro I have on my workstation - 1909? Do I have to update to 20h2 in
order to fix the situation?
Thank you very much in advance!
thanks, everything fine here. The latest update of the eLC has only an update of the license database but no change in functionality.
And to be honest, we also don’t know if the problem you are having comes from our eLC or Windows.
By downgrading the eLC, can you get back into the wanted state?
Thank you for the reply! I’m glad that everything is fine there.
Well, if I downgrade to version 6.11… everything works fine. But when I started the Steinberg Download Assistant it automatically updated the eLCC without asking.
Probably something that requires Windows 10 Pro 2004, or later, was implemented in the latest versions of eLCC?!
It’s a delicate thing to touch already tweaked and fine working system… upgrading the Windows could cause unwanted issues.
That’s why I’m asking about such details.
If you have any information I would be very thankful if you share it with me!
unfortunately I don’t have such information. But I don’t know if you have already heard, we are actively working on a new system where the eLC will become obsolete, so please bear with us and in the not so far future these issues will simply disappear. Thanks