Thanks guys.  I have never had a MIR demo license on this key as I have owned the product it since it was released years ago as original MIR.  I ran the maintenance many times as well and all steps succeed..  Some MIR PRO 5 releases are fine, then others just plague with eLicenser issues for me.  The recent updates have completely killed my ability to use the software.  i cannot open any of my old or current projects if MIR PRO server is running.  If I launch the project without MIR PRO server running it all loads just fine.  But if I then try to load the MIR PRO server it gives me eLicenser errors.  So I decided to update to the latest MIR PRO 5 and eLicenser as well as VI PRO 2 etc.  Just to be safe.  My god that was the worst mistake, now nothing works.  I can't even load the projects without the eLicenser key because my Cubase license is on there.  So If I wanted to just go in and remove all VSL instruments and move to another vendor I can't even do that because I can't get into Cubase without it.

This is the exact behavior:

Launch MIR PRO Server before opening Cubase 6.5:

Try to open any recent project and Cubase will lock up and I get blasted with eLicenser errors.  The error ranges from blaming Vienna Instruments Pro, to Blaming MIR PRO 5.  Sometimes it blames Vienna Suite and once it even blamed Vienna Imperial.  Have to force quit everything and reboot machine.  Ran Maintenance again.  Uninstalled and re-installed all software about 4 times each.  Same results.

Launch Cubase 6.5 BEFORE I launch MIR PRO Server:

1.  I can open any file I want.  Including any project that has VI PRO 2, Vienna Imperial etc.

2.  I can even open files that have MIR PRO 5 in them, because they have no server to connect with.

3.  If I try to open the server at this point, I get eLicenser errors of a service failed balh blah blah cannot start.  Now everything is screwed.  Reboot.

Now remember the server and the stand alone start just fine (before launching any other applications it works just fine).  Also, if I create a completely brand new project from scratch, insert MIR PRO into it, it works.  And interestingly, it will ALWAYS open those new projects.  So it's as if the new updates killed opening old projects (I am only talking about projects that are days old, to a few months.  Not years and all were created with MIR PRO 5).

So it refuses to access any project that was created prior to the updates and eLicenser maintenance.  But it will open brand new projects.  I tested more than 10 projects and it's the same error on all of them, fails to load with eLicenser error messages.  And this isn't a Cubase issue, it does the same behavior in Studio One V2.  So this is either a bad MIR PRO update, or an eLicenser database issue (I am leaning to the first as Cubase and my other software starts without any issues).

It's really a shame but I am starting to think it's time to leave the eLicenser world.  It's just to much hassle for the customer.  I never have any failures with my LASS or Symphobia Libraries.  When I look back at all the years I have suffered, it has always been with Logic PRO and eLicenser.  On both MAC and PC.  I was able to eliminate the issues with Logic by moving to Windows 7 and now the only issue I ever have in my studio is with VSL and eLicenser.  It's really a shame because I do love this company and the products but this eLicenser is just absolutely killing me.  They say there are lots of upsides to it but I don't see them.  I have never had any issues with my other software that don't use them, and most importantly I don't have to walk around terrified that I will drop it, break it or lose it.  All I want is to come home, and be able to login and make music.  I lost my entire weekend with this problem.  Everybody at VSL is extremely helpful but it really hurts badly to be down from eLicenser issues.

Dietz or anyone, do you have any ideas I could try.  I really just want to get this working again.  I had made my best template ever the night before, which is why I am so furious the next three days I was down from this.  I was so motivated to make music and I lost my 3 days off troubleshooting eLicenser issues with no success.  I did not do any Windows updates.  I did not install any new software.  I did not download any porn or browse nude video websites on any of the machines.  I did not check emails on them, I did not search google on them, i ...  You get the point.  They simply sit there as studio music machines.

Thanks,

Maestro2be

Absolutely.  Thanks Karel.

Maestro2be

Email sent.

Thanks,

Maestro2be

Well being down for a week sucked, but the new update fixed my problem.  Was definitely a VE PRO 5 issue.  I will need to remember to set a proper restore point before I ever do another update.  I should know that by now and have no idea why I didn't do it.  Lesson learned, again.

Thanks for the update.

Maestro2be

Dear Maestro2be,

sorry for your troubles, and good to hear that things are working again for you.

Just a sidenote: At VSL, we have to use an eLicenser for any VSL product just like VSL customers. It's highly unlikely that a copy-protection related issue remains undedected under most circumstances. It seems as you have run into a very peculiar combination of variables.

Thanks for your patience.

Thank you very much Dietz.  Sometimes things just happen when dealing with computers and doing this for a living I should know better than to update my main machine without setting a restore point.  Because even the best updates can cause issues in the most strange scenerios.  The biggest problem with it is when I lose a week on the two projects I had going, and now open them last night and cannot mentally remember where I was on them.  I take notes but even then, when you get removed from the mood and moment it's really hard to pick back up on it.  Will take a few days to do that.

Even more reason to remember to take a restore point in the future.  Thanks agian for the hard work and getting me up and running again.

Maestro2be

@cgernaey said:

Even more reason to remember to take a restore point in the future.  Thanks agian for the hard work and getting me up and running again.

Hi DG

Once I had troublle with VSL ; I started Logic without the VSL server lauch, I has able to disable VSL AU in the song and save my work 

Anoter trick I found is to remove all VSL AU and start Logic, you just get error messages that he does not find the AU and you can save your work without the VSL plug-in

Can you do that with Cubase ?