error code: -59, panic panic panic

set wrote on 11/7/2017, 12:02 PM

Try contact support:

https://support2.magix.com/customer/en/vegas/form

Please include the app name, version number, build, and serial number when creating the ticket.

(a bit similar reference comment from Magix Staff: https://www.vegascreativesoftware.info/us/forum/a-ringing-endorsement-of-vp15--108974/?page=6#ca674017 )

digilyd wrote on 11/7/2017, 12:57 PM

Support ticket confirmed 13:10 CET, thank you, I will wait for a reply before adding information, some of which I can not determine due to the way it refuses to work. Both are the newest availalbe version and both have apparently been online tacitly recently and renewed their registration.

A most unpleasant apparent single point of failure to encounter. If I had been working with a shorter deadline with the three current concert videos it had been plain disaster for getting a business started because of the business credibility damage it could cause. As yet, it is only a nuisance. But for someone having to deliver news footage ...

set wrote on 11/7/2017, 5:57 PM

While waiting for the support staff, I searched my own and you can find in FAQ no 4 :

https://www.vegascreativesoftware.info/us/forum/faq-vegas-pro-won-t-start-what-can-i-do--104784/

It says it needs activation process... check your online connection permissions and allow your computer connect to Magix server. Seems you already did this...

The other info I found, What is your OS? If it is Win7, please update to Win 7 SP1.

Hope helps,

digilyd wrote on 11/7/2017, 11:51 PM

Thank you Set, it is Win7 updated as far as windows update will take it, something that may have been an error as everything worked fine for the year it was prohibited from updating anything, antivirus is avasts pay version. I have been wondering whether it might be a software firewall issue.

As supporter I loathe(d) when people tinker a lot before getting help with a problem, they can't solve anyway because it adds complexitiy and new potential issues, so as it might be a server side issue, I didn't do anything and decided to wait for information from people in the know, not adding potential errors by finagling with what actually works is often a strong strategy. Vegas - both versions, 14 and 15, on a pc boot yesterday - with no warning and having worked the day before - decided to act as if the server had prohibited them from working.

One of the reasons why I did nothing is my experience with Adobe Audition, reportedly it was - way back in time, many years ago! - adviced not to install a production version on a physical harddrive a trial version had been running on due to an issue in the activation process that might confuse a production version and a trial version AND logged the manufacturing number of the physical disk it was installed on. It is my recollection that a server version of Windows should not be reinstalled on a physical disk that a server that has had its function seized by another domain server because of hardware failure has been running on. So it was most likely that I would not be able to influence the issue anyway and thus best to do nothing beyond an os image restore.

As a side note, I am surprised that the post you linked to asks for a lot of information about versions of everything. I have a download version that is installed and has been updated once by their download manager client, so they know every single piece of code that is running on my license already, and they know it in triplicate and more because of all the closing down crash crashreprorts I have sent. It is in their logs, including all about os and hardware as that is included in the crash reports. This was in my mind when not including it, a choice made before seeing that it is a known issue, I thought it was a new glitch.

Thank you for your comments!

NickHope wrote on 11/8/2017, 4:33 AM

As a side note, I am surprised that the post you linked to asks for a lot of information about versions of everything. I have a download version that is installed and has been updated once by their download manager client, so they know every single piece of code that is running on my license already, and they know it in triplicate and more because of all the closing down crash crashreprorts I have sent. It is in their logs, including all about os and hardware as that is included in the crash reports.

As I understand it, crash reports are not received by Magix unless they are emailed by this method.

digilyd wrote on 11/8/2017, 6:20 AM

So the software asks for permission to send a crash report and whether it may include project files, but doesn't send it because an undocumented keypress combination is not used? -. I think I'll let be commenting!

digilyd wrote on 11/11/2017, 10:12 AM

This may be resolved, but I want to see it work tomorrow. Uninstall was impossible for all affected Magix applications, Magix video editor with Mercalli as well as V14 and V15 all abended with error -59, and none would uninstall for the reinstall on enabled Administrator account Magix support requested. Support advice then was to use "MicrosoftProgram_Install_and_Uninstall.meta.diagcab" (yes, that is the filename) and it uninstalled all three. I only reinstalled V14 and V15 and right now they work ok now, except that an mpeg2 render failed, but a mp4 render of the same file seems to work. I will see it work tomorrow before tagging it as solved :) - also because perhaps there is a codec enabling issue, perhaps not.

NickHope wrote on 11/11/2017, 8:04 PM

...Support advice then was to use "MicrosoftProgram_Install_and_Uninstall.meta.diagcab" (yes, that is the filename)...

Which (for future reference) comes from here.

digilyd wrote on 11/12/2017, 2:23 AM

Yes, it is resolved, everything works again also today, happy, happy, happy :)