Vienna Symphonic Library Forum
Forum Statistics

182,869 users have contributed to 42,261 threads and 254,943 posts.

In the past 24 hours, we have 0 new thread(s), 10 new post(s) and 34 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. New VEPro 6.0.15401 Crashing

  • New VEPro 6.0.15401 Crashing

    B
    B

    I am getting and instant crash when connecting to remote empty instance from any daw software. Plugin/client will see the remote server no probs but once I press the connect button, bang crash.

    • Have tried creating an instance first, able to load plugins etc
    • have tried vst2 and 3
    • have tried different buffers
    • have updated windows 10pro 64bit to latest anninversay edition on remote since issue started (to re-test) but no difference. My main workstation is on deferred updates hence on win 1511
    • VEPro 6.0.15401 on both systems
    • have deleted vst cache and rescanned
    • happens with no plugins loaded ie new empty instance or plugins populated - doesnt matter.
    • once finished VEP update and opening for 1st time VEP asked for update to 6.0.15401 even though I just did that.. Happened on all pcs. **EDIT: This first time when asked to install 15401 I cancelled the download/re-install because I had just updated to 15401

    crashes with this windows log report:

    Faulting application name: Vienna Ensemble Pro.exe, version: 6.0.0.15401, time stamp: 0x5809ef17

    Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f83ff

    Exception code: 0xc0000005

    Fault offset: 0x000000000003c963

    Faulting process ID: 0x198

    Faulting application start time: 0x01d22f3bda4b6801

    Faulting application path: C:\Program Files\Vienna Ensemble Pro\Vienna Ensemble Pro.exe

    Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll
  • B
    B

    UPDATE: I completely re-installed after searching thru all system folders for VSL and deleting, Again came up with quest on both PCs to update to 6.0.15401 even though that is what I just installed.

    **So this time: I let it download and install again the same version. (refer to ** in previous post)

    Note: This time on remote server, a firewall rule request came up on 1st load which I allowed. This was probably because I used CCleaner the clean registry after de-install. There were firewall rules that were removed here.

    Once the RE-install was done on each computer and I loaded up and connected, no problem. Problem solved.

    Is there a difference in the install file downloadeed from MyVSL compared to the one that VEPro downloads vias automatic update? Or is there a file not installed properly by the stand alone installer?

    What is the MSVCR120.dll error from?
  • PaulP
    VSL Team
    PaulP
    last edited
    last edited

    Hi,

    Thanks for the udpate, good to hear that it´s working now.

    Here is more information on the MSVCR120.dll error.

    The update bug wanting to install the same version again will be fixed in the next update, soon to come.

    Best,
    Paul

    Paul Kopf Product Manager VSL
  • B
    B

    Thanks Paul

    Note that the only way I could stop it crashing was to let it download again and install over.

    There must be something in the automatic install process or the automatically downloaded version that is different form the MyVSL version.
  • P
    P

    Hi! I am having the same issue here. Can you tell me exactly how you are installing the "automatically downloaded" version? I can't seem to install it besides through the .exe from myVSL.

    Edit: When I install an older version of VEP 6, then "Check for Updates", it downloads the update and asks me if I'd like to close the application and install. I select "Install" and VEP closes, then nothing seems to happen.