Vienna Symphonic Library Forum
Forum Statistics

196,663 users have contributed to 43,022 threads and 258,418 posts.

In the past 24 hours, we have 1 new thread(s), 2 new post(s) and 96 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Dimension Strings update problem

  • Dimension Strings update problem

    J
    J
    last edited
    last edited

    Hi,

    Posting here as my email to support@VSL.co.at is bouncing back undeliverable: (edit - don't know what all the bliue type is - doesn't appear on the post preview!

    Final-Recipient: rfc822; support@vsl.co.at
    Original-Recipient: rfc822;support@vsl.co.at
    Action: failed
    Status: 5.7.1
    Remote-MTA: dns; mail1.cyberservice.net
    Diagnostic-Code: smtp; 554 5.7.1 <support@vsl.co.at>: Relay access denied

    Anyway, looking for help with the issue below:

    I am encountering an update issue trying to run the Dimension Strings update:

    Prior to running it I made sure I was up to date with the latest eLicenser.

    System = macOS Mojave 10.14.6 MacBook Pro i9 2018, VSL library on x2 SSDs. VSL key and iLOK key connected directly to the computer.

    This is a summary of the update procedure:

    1. Initializing update please wait for 10 minutes
    2. Scanning Volumes
    3. eLicenser POS Error message – File Synsoacc.bundle does not have the expected interface
    4. Click OK Scan stops until OK is clicked
    5. Scanning Volumes – Click OK multiple times
    6. Updating Files
    7. Lib_Update_Dim-Strings-1_March_21-2019 0 files were updated
    8. Click OK
    9. Rescanning directories for 2” then finished.

    I have not encountered the eLicenser error message before. I tried uninstalling and re-installing eLicenser and running the update again – same result, tried redownloading the update package – same result. I am dragging the .zip update package to the directory manager as advised to instigate the installation process.

    Do you have any ideas how to fix this?

    Thanks, Julian
  • J
    J

    Oh and just to add. I have run the maintenance process on eLicenser which reports back OK and all VSL licences appear to be present and correct.
  • M
    M
    last edited
    last edited

    Hi,

    we just released an update addressing this issue today. Just go ahead and download the new version from MyVSL.
  • J
    J

    That appears to have fixed the issue, Thanks.