![]() Will try to find a way around that though. Thanks a lot for the proposed fix, Stiltzkinz! Attempted this last night, but Win8 gave me some issues with "l" being object protected. Since VEP is the only program that seems to cause this issue, I would not be so quick to blame Steinberg, Paul. In my current build with Cubase, Cubase simply won't load and shows the error message as reported in above posts.Īll in all, over the last year, I have spent more time updating eLicenser, rebooting the computer (according to the error message), changing USB ports for the key, than what I have spent in VEP Pro and Vienna Instruments Pro! ![]() In my previous build, Ableton would fail to open any plugins requiring eLicenser. Only when I recently moved over from Ableton to Cubase and the latter did not start up (since it needs eLicenser) did I realize that VEP Pro is the culpit. I've had this exact issue on two separate builds using Win7 圆4 and Win8.1 Pro 圆4. It works fine when running cubase and then opening VE Pro though - but this sort of isn't ideal considering the workflow improvements is what I'm mainly using VE Pro for :P I've checked to make sure VE Pro, eLicenser and Cubase 7 are all up to date, along with all windows updates etc - I've also made sure that all the programs are being run with full admin settings - I'm unsure what else to try really. Please visit to download and install the latest version of the Elicenser Control software in case the problem persists. Please restart your computer to fix this problem. When having VE Pro open (even without a metaframe loaded, just the VE Pro 64bit Server) I get the following error:Īpplication 'Cubase / Cubase Artist' has caused the following error:Īn important service has become unresponsive. I also saw a post in the forum thread mentioning the SofteLicenser possibly causing these issues (VSL products don’t use the soft-eLicenser).I've started using VE Pro, and while it does all work correctly, I am unable to have VE Pro open PRIOR to opening cubase or any other program that uses my eLicenser. Start your sequencer/hosts, then go to the Task Manager and end the “protected Object” task" - if there is one. Run the eLCC software as admin and click “Maintenance” Uninstall the eLCC software & reinstall it as admin (!) But here are a few things you can try - and I would test in between every time to see if that step has fixed it: So this issue seems to affect all kinds of 3rd party products like HALion Sonic, Cubase, …as well - not just VSL products. There are also other non-related cases in the Steinberg Forum. We did some logging and provided detailed information for the Steinberg developers (eLicenser), but this was never really fixed, to my knowledge. Unfortunately, we did see a few “ID NOT found” error messages starting to pop up in support a few months ago. Received this in response to my email to Vienna Instruments and it was the solution for me. I have no idea if running Maintenace will sync my other Steinberg key or Software licenser number or not but that was mostly for troubleshooting anyway. It is working for now so I will leave it alone. I don’t have the balls to run Maintenace again. I suspect more people will have this problem and find this page. Too bad that the Cubase 11 install automatically updates eLicenser Control to the latest version. So if you get this error, I would recommend downgrading to the old version until they fix this. Given that this is a professional studio and anyone could open eLicenser Control Setup by accident or curiosity which would cause Cubase to stop opening even after restart unless the workaround steps above are done, it seems way too dangerous to keep the new version installed. Like I said before, I highly suspect there is a large bug in the latest versions of eLicenser Control Setup. and it still recognizes the Cubase 11 license. After a few hours of troubleshooting, I worked out, that if you completely uninstall eLicenser Control Center and then install this older version from 18 months ago, you can open Cubase Pro again without having to kill “Protected Object Server”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |