Vienna Symphonic Library Forum
Forum Statistics

196,625 users have contributed to 43,021 threads and 258,416 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. New VE Pro 6 Update - has it broken my DSN server.

  • New VE Pro 6 Update - has it broken my DSN server.

    mantrumM
    mantrumM

    Hi All,

    My first post here.

    Last night my VE Pro 6 updated to the latest verion on my cheesegrater mac pro running Sierra.

    This morning I have no internet access - and with some messing aroung it seems me DNS service is screwed up, as I can access websites by their ip address - though oddly it seems I can resolve ip addresses via terminal.  [Updated Below]

    Now, of course this might be a complete co-incidence and have nothing to do with the VE Pro 6 update, but it did start to happen after I restarted after the update.

    Anyone else having any issues ?

     

     

    Cheers, Mike
  • J
    J

    Yes! Same problem here...
  • P
    P
    Me too! All computers I installed the update have completely lost internet and external computers no longer appear on my network Spent hours trying to get to the bottom of this today now I know it's the vsl update thanks to this post. Please fix fellas! I'm cursing myself for updating during an important project. Already lost half a day over this.
  • J
    J

    I opened a support ticket and sent a crash report. On Mac 10.11.6 over here with all the most recent updates. VEP is crashing like crazy. Seems to always be upon a click that it crashes. 

    Same here. Big project. Kicking myself for not waiting... Ah well, I'm sure we'll be fine in while.
  • P
    P
    Vsl techs: So you have more info. I'm running latest Sierra. I installed old vep 6 and Internet still down so the latest version for sure did something to the network of the OS When clicking network diagnostics. Wifi (and Ethernet) network and ISP are green but red on both internet (failed) and served (failed) Also none of my computers are showing up as shared any longer I'm an idiot for not having time machine working so I hope u can find a fix or I'll have to reinstall my entire system from scratch after my project is done Thanks
  • mantrumM
    mantrumM

    Just in case it helps any of you guys, Google Chrome is working on my Mac.

    But nothing else. If you need to get on the net with a browser Chrome should work for you too. There is a delay when opening web pages, but I think it is trying to use the Apple DNS service, giving up and then using it's own.

    It looks like the update has broken the DNS service that resolves IP addresses. In console.app there are lots of error codes whenever you attempt a DNS operation.

    Oddly in terminal you can resolve IP adresses using 'nslookup' but not using 'ping'.

    I even installed Sierra on top of itself but to no avail. I think we will just have to wait until they fix this.

    I'm flipping glad I didn't install it on my main machine so at least I can run libraries locally until they fix it.
  • J
    J

    Passenger57's thought (Thanks, P57!) regarding Time Machine woke me up here. After a full restore to a couple of days ago, DNS, etc... is all good. 

    Brought up the project with Cubase and VEP and it all looked good. I do expect crashes to continue and will send up reports. At least I can give up running around this place with a 1 GB thumb drive...
  • P
    P
    last edited
    last edited

    @mantrum said:

    Just in case it helps any of you guys, Google Chrome is working on my Mac. But nothing else. If you need to get on the net with a browser Chrome should work for you too. There is a delay when opening web pages, but I think it is trying to use the Apple DNS service, giving up and then using it's own. It looks like the update has broken the DNS service that resolves IP addresses. In console.app there are lots of error codes whenever you attempt a DNS operation. Oddly in terminal you can resolve IP adresses using 'nslookup' but not using 'ping'. I even installed Sierra on top of itself but to no avail. I think we will just have to wait until they fix this. I'm flipping glad I didn't install it on my main machine so at least I can run libraries locally until they fix it.
    Woah your right Chrome does work. Trippy. Thanks for the tip!
  • PaulP
    VSL Team
    PaulP
    last edited
    last edited

    Hello everybody,

    Very sorry about the trouble, this is now fixed with a new update, available in your User Area.

    Alternatively, here is the direct download link for VE PRO 6.0.16012 for macOS, please restart the computer after applying the update!

    Best,
    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • mantrumM
    mantrumM

    Just one thing - you need to restart the mac after the update for things to get fixed.
  • PaulP
    VSL Team
    PaulP

    Hi mantrum, 

    I have added this information to the post above, thanks for reminding me. 

    Best, 
    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • B
    B

    I'm running DP9 and my slave VEP6 machine crashes when opening a new project.  I even installed your patch from this morning and restarted both machines, but no love. 

    Master machine MBP running 10.12.4, Slave machine MBP running 10.11.6.
  • P
    P
    last edited
    last edited

    @Paul said:

    Hello everybody, 

    Very sorry about the trouble, this is now fixed with a new update, available in your User Area. 

    Alternatively, here is the direct download link for VE PRO 6.0.16012 for macOS, please restart the computer after applying the update!

    Best,
    Paul

    Thanks Paul! I was hoping to find this when I woke up today, all my networks work again. 😊
  • B
    B
    Yes, I tried that patch and restarted both machines. Nothing improved. Still crashes as soon as instruments start to load under DP9
  • E
    E

    Thanks for the fix, but I feel like VSL didn't treat this issue seriously enough. Their update friggin broke the OS networking! That's a big deal. I lost a whole day to this, yesterday, and it never occurred to me that a minor bugfix update on some music software I did the night before would have broken networking. You guys should have emailed all your customers to hold off on the upgrade, once you knew about this issue. You should still email them, because many people won't think to check the VE Pro forums. And the update will never be picked up by the automatic update feature in VE Pro, because networking is broken.

    I understand that bugs slip through (though I'm still angry about such a serious one), but you folks need to communicate with your customers when such a catastrophic one slips through. I still have received no emails from VSL about this. There is nothing on any of your social media.
  • D
    D
    last edited
    last edited

    @Paul said:

    Hello everybody, 

    Very sorry about the trouble, this is now fixed with a new update, available in your User Area. 

    Alternatively, here is the direct download link for VE PRO 6.0.16012 for macOS, please restart the computer after applying the update!

    Best,
    Paul

     

    Still crashes for me even after reset.  I've sent a crash log.
  • J
    J
    last edited
    last edited

    @ericgoetz said:

    Thanks for the fix, but I feel like VSL didn't treat this issue seriously enough. Their update friggin broke the OS networking! That's a big deal. I lost a whole day to this, yesterday, and it never occurred to me that a minor bugfix update on some music software I did the night before would have broken networking. You guys should have emailed all your customers to hold off on the upgrade, once you knew about this issue. You should still email them, because many people won't think to check the VE Pro forums. And the update will never be picked up by the automatic update feature in VE Pro, because networking is broken.

    I understand that bugs slip through (though I'm still angry about such a serious one), but you folks need to communicate with your customers when such a catastrophic one slips through. I still have received no emails from VSL about this. There is nothing on any of your social media.

    Well said. I ended up missing the dealine for a project, and two days of reinstalling software because I needed to do a clean install of Sierra. I discovered that the VEPro 6 update was the issue because I happened to be on a forum and saw posting about it. A simple email would have saved me from all of this, as I could have downloaded the patch. VSL still hasn't communicated this info....I wonder how many composers around the globe are frustrated? Not good. On the other side of the coin, it's my own fault for jumping the gun and updating right away...should have known better.
  • N
    N

    Hi.

    A fellow composer has just told me about this. I installed the faulty update last week.

    A Mac repair man earlier today spent two hours at my studio trying to mend my computer. He had never come across a problem like it. The only way the internet could be accessed was through Chrome - Mail, Safari, iTunes, App Store, etc. wouldn't connect - and my main Mac Pro wasn't being seen as a shared computer by the other Macs on my network.

    £210 his time cost me. He left without having fixed it and, on his advice, I am now in the process of a clean install.

    I have to admit that I really am not very happy at all.

    VSL, can I please ask: why didn't you email everyone to inform them that this update was buggy? If you had have done, I would have been aware that the fault lay with your update and I wouldn't have needed to get anyone out to try to fix my computer. If you'd like to reimburse me the £210, I'll happily forward you macman.co.uk's invoice.

    Nick
  • PaulP
    VSL Team
    PaulP

    Hello, 

    We are very sorry that this bug slipped through, it resulted from an attempt to increase efficiency, along with other essential bug-fixes that we have worked on for quite some time. 

    Our developer team reacted the minute we saw the first report, on sunday morning, and the download numbers of the OS X version for this fix were about the same as with the previous version within 24 hours. 

    The bug affected OS X users exclusively, and only after a restart of the computer.

    Luckily, very few OS X users restart their computer on a daily basis, which definitely helped in this situation. 

    All in all, 6 days after release and 4 days after the quick update, we received 3 reports about this problem, and there is this very thread with 17 entries from 8 users.

    So before alarming tens of thousands of users (which would have been too late for most affected users anyway), we decided to let our automatic update service help out in this situation, which, from our perspective today, turned out to be a good decision. 

    I fully understand that this is not a comfortable situation for everybody affected by this unfortunate bug.

    Thank you so much for your input and help resolving it!

    Best, 

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • A
    A

    Everyone is entitled to a mistake, Just NEVER let it happen again :)