Totally agree. After a couple of months, support finally replied to me saying they could not reproduce the error. My template doesn't load with ilok and loads when i reinstall elicenser. But I gave up... I lost too much time waiting just to get a basic level 1 support answer. I am not using VE Pro anymore and i now think twice before buying any VSL stuff.
Error after upgrading VEPro7 to version 7.1.1249-Apr 2 2022 and now my server projects won't load
- Thread starter quickbrownf0x
- Start date
Totally agree. After a couple of months, support finally replied to me saying they could not reproduce the error. My template doesn't load with ilok and loads when i reinstall elicenser. But I gave up... I lost too much time waiting just to get a basic level 1 support answer. I am not using VE Pro anymore and i now think twice before buying any VSL stuff.
chrisr
Senior Member
This is really worrying.
I tried to update several months ago and had similar errors, so reverted back to the eLicenser version.
I've not been in a position to try again since, but hope to do so around end Oct / start Nov.
It would take me a weeks to rebuild my template, which is heavily dependant on VEP, and has thousands of midi automation settings to enable/disable kontakt instances and control reverb sends.
Is there anyone here who had the problem (elicencer created VEP7 template not loading into iLok VEP7) who later managed to fix it with an update or workaround?
I tried to update several months ago and had similar errors, so reverted back to the eLicenser version.
I've not been in a position to try again since, but hope to do so around end Oct / start Nov.
It would take me a weeks to rebuild my template, which is heavily dependant on VEP, and has thousands of midi automation settings to enable/disable kontakt instances and control reverb sends.
Is there anyone here who had the problem (elicencer created VEP7 template not loading into iLok VEP7) who later managed to fix it with an update or workaround?
chrisr
Senior Member
@Ben
Regarding the "The project you are trying to load is invalid" error when loading a template created in VEP (eLicenser) to VEP (iLok) ...
Have VSL been able to replicate the problem, and issue a fix in these past months? Comments above suggest that you have not been able to reproduce the error, in order to issue a fix, is that correct?
To your knowledge have there been any users who originally had the 'invalid' message, who were later able to successfully open their VEP (eLicenser) created templates in VEP (iLok) by some means?
Many thanks for any reply - I'm afraid I've not kept up with events due to work commitments.
best,
Chris
Regarding the "The project you are trying to load is invalid" error when loading a template created in VEP (eLicenser) to VEP (iLok) ...
Have VSL been able to replicate the problem, and issue a fix in these past months? Comments above suggest that you have not been able to reproduce the error, in order to issue a fix, is that correct?
To your knowledge have there been any users who originally had the 'invalid' message, who were later able to successfully open their VEP (eLicenser) created templates in VEP (iLok) by some means?
Many thanks for any reply - I'm afraid I've not kept up with events due to work commitments.
best,
Chris
Ben
VSL
Hi Chris! As far as I know all these issues related to eLiceser project conversion are fixed already.
Our converter tries to open the old eLicenser project files with your local eLicenser, and if none is present it will try to decode those with our online service. So make sure you have the eLicenser key inserted or an active internet connection when opening such project files. Once re-saved the eLicenser or an online connection is no longer necassary to open the project files.
Ben
VSL
It runs completely automatically in the background if needed. So in most cases you will not notice it at allHi @Ben
Thanks for your speedy response! I didn't even know you had created a converter, my apologies for being so out of the loop. I look forward to trying it, if needed, in a few weeks time when I hopefully make the swap to iLok
many thanks,
Chris
chrisr
Senior Member
@Ben
So I'm finally getting around to looking at this again, and it's still not working at all.
I have VEP7 64 server (EL) installed on two machines, a win8.1 pc and a win10pc.
The latest iLok version I can install on the win8.1 machine is 7.1.1406, and it's failing to open an eLicenser server project (created in 7.0.1120) at any attempt.
I'm loath to try a later/latest (7.3.3.x - win10 only) VEP build on the win10 machine because I need to have at least one of them avail for work!
However I'm going to try to revert everything (vep / synchron player / vienna instruments pro / all samples) back to the old elicenser versions and get all working again then will reluctantly back up my win10 and try the ilok version there I guess. I've seen comments online that lead me to believe that it may work better on win10.
By way of chasing the problem, I've stripped the server project right back to a single instance of kontakt with no automation info etc... etc... and still no dice.
best,
Chris
So I'm finally getting around to looking at this again, and it's still not working at all.
I have VEP7 64 server (EL) installed on two machines, a win8.1 pc and a win10pc.
The latest iLok version I can install on the win8.1 machine is 7.1.1406, and it's failing to open an eLicenser server project (created in 7.0.1120) at any attempt.
I'm loath to try a later/latest (7.3.3.x - win10 only) VEP build on the win10 machine because I need to have at least one of them avail for work!
However I'm going to try to revert everything (vep / synchron player / vienna instruments pro / all samples) back to the old elicenser versions and get all working again then will reluctantly back up my win10 and try the ilok version there I guess. I've seen comments online that lead me to believe that it may work better on win10.
By way of chasing the problem, I've stripped the server project right back to a single instance of kontakt with no automation info etc... etc... and still no dice.
best,
Chris
Ben
VSL
The VEP7 versions on all machines in the network have to match.
Please be aware that we no longer support Windows 8.1 as it reached EOL (end of live).
The only advice I can give at this point is to upgrade the Windows 8.1 to 10 if possible and run the latest version of VEP7.
chrisr
Senior Member
Thanks @Ben - yes I appreciate that re. win8.1.
I'm back with the eLincenser versions on that machine now and all running smoothly again. The win10 machine is currently on that same version (also eLicenser)
I can see that it's the weak point in my setup, as the win8 machine is effectively stopping me from upgrading the win10 machine VEP which may fare better with the Server Project Translation- but the idea of upgrading the OS fills me with dread!
Having said that I'm currently running win8 off a cloned C drive (an identical drive is on the shelf) - so I guess if there are big problems then I can swap that back in.
One last question:
If I upgraded the win10 to ilok and was able to successfully open my server project using VEP7.3, would a server project saved in that version likely open in 7.1.1 ? If so I could then run (ilok) v 7.1.1 on both the windows 10 and win 8 machines.
May feeling is that that's potentially a more shaky solution than simply trying to upgrade the OS...
Ben
VSL
You can't open 7.3 files in 7.1
