MSXML 4.0 and MusicMaker install failure

mudfinger wrote on 6/22/2017, 3:07 AM

Just got software during a humble bundle deal and cannot get music maker (or more specifically MSXML 4.0) to install. Doing some research MSXML 4.0 is no longer supported and will flat out not install on Windows 10. The exact error i receive is : "an error occurred during the installation of assembly component {74974f83-779e-3983-a06b-d6b9abf34537}. hresult: 0x80070002" How do i get around this to get Music Maker running?

Thanks

Comments

johnebaker wrote on 6/22/2017, 10:22 AM

Hi

The Music Maker included in the bundle has its own installer and is not dependant on MSXML.

If you cannot get it to install the same version is available direct from Magix here

I would suggest you read this topic on MSXML, it is not compatible with Windows 10, hence the installation error.

HTH

John EB

 

Last changed by johnebaker on 6/22/2017, 10:23 AM, changed a total of 1 times.

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

mudfinger wrote on 6/22/2017, 7:07 PM

The MSXML info is from the installer for Music Maker. I tried installing outside of the MM install just to see if it would get me any further. I have tried uninstalling, running CCleaner, rebooting, running CCleaner and reinstalling with the same result; regardless of where downloaded from (i have DLded it from both Humble Bundle and direct from your link). When i try to start MM, the splash screen shows briefly, shows some initialization messages down at the bottom then just disappears. Additionally, I have ensured that my antivirus is not blocking it.

I have sent the install logs up as part of the error reporting service provided through Music Maker. Tried to attach a zip to this post but it would not upload. The installer window remains up after everything completes indicating an error (presumably the MSXML error) and sits there showing 'installing' with the progress bar at 100%

Tried monitoring Windows event viewer while trying to start Music Maker and this info message appears in the application log right after it fails (verified twice), not sure if it means anything but thought i would add in case its helpful:

The description for Event ID 0 from source AdobeARMservice cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Service started

Any ideas on where to go from here?

Thanks

johnebaker wrote on 6/23/2017, 3:23 AM

Hi

. . . . The description for Event ID 0 from source AdobeARMservice cannot be found. . . . .

AdobeARMservice is the Adobe updater service, I suspect the program is looking for the Adobe Reader installation and cannot find it.

Check Adobe Reader is installed correctly or install it if you do not have it. It is required to read the installed PDF manual.

If that fails try re-installing following this tutorial.

HTH

John EB

 

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

mudfinger wrote on 6/23/2017, 6:48 AM

Reinstalled adobe reader, music maker and followed the tutorial you provided and still no luck. Once i start running sfc /scannow - almost immediately get the message: "Windows Resource Protection could not perform the requested operation." Did some looking to find what to do about this, and found that Microsoft suggests to run chkdsk /r to fix sfc (system file check) - so i am fixing a repair tool with a repair tool? -- Nice Microsoft.

In any case did run chkdsk rebooted and tried sfc again - same result.

This is starting to become more trouble than it is worth; getting frustrated. Still though, thanks for the help. Will have another look at it again tomorrow with fresh eyes.

johnebaker wrote on 6/23/2017, 4:26 PM

Hi

This sounds like either:

  1. You have a virus infection preventing the system file checking

    Or
     
  2. The hard drive is beginning to fail.

    Right click the Computer icon on the desktop and select Manage, Disk Management, in the lower half of the centre pane you should see your disk drive(s) and there status - it should read Healthy.

    If the drive is not healthy then it may be failing.

HTH

John EB

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

mudfinger wrote on 6/26/2017, 10:45 PM

Just wanted to follow up.  I broke down and reinstalled windows; tried to do a refresh and that would not even work so I figured I had bigger issues than just getting Music Maker working and decided it best to start clean.  Once I had a clean install of windows, Music Maker installed without issue.  All is good.  Thanks

johnebaker wrote on 6/27/2017, 2:14 AM

Hi

Thanks for letting us know, were there any issues with the hard drive or was the Windows installation corrupted?

Hopefully you did not have too much other software to re-install.

Happy editing

John EB

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

mudfinger wrote on 6/28/2017, 5:37 AM

I think it was Windows, once I reinstalled it also updated to the creators update which I was wondering about why it was taking so long for my system to upgrade to as well.

Not to much to reinstall, good way to clean out all the stuff that has built up.  Little bit of a pain, but nothing that I haven't gone through before.  Most likely will go through again in the future, even with backups.  No biggie.

johnebaker wrote on 6/28/2017, 5:47 AM

Hi

I use CloneZilla to make a clone image of my OS hard drives on a regular basis, ~ every 3 months, to maintain a recent restorable OS and software backup in case of hard drive failure or worse.

As you now have a relatively clean system it may be worth considering.

HTH

John EB

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

mudfinger wrote on 6/28/2017, 6:24 AM

Yeah; did a backup right after I had everything setup like I wanted, thanks.  Thought about rolling back from backups I had, but figured it was just easier to reinstall than to try and find a backup that wasn't corrupt as well.

cloeterrell wrote on 4/17/2019, 4:54 AM

Just got software during a humble bundle deal and cannot get music maker (or more specifically MSXML 4.0) to install. Doing some research MSXML 4.0 is no longer supported and will flat out not install on Windows 10. The exact error i receive is : "an error occurred during the installation of assembly component {74974f83-779e-3983-a06b-d6b9abf34537}. hresult: 0x80070002" How do i get around this to get Music Maker running?

https://validedge.com/windows-resource-protection-could-not-perform-the-requested-operation/

Thanks

Hi, If you got the solution then please share the best one so that it will help the new members to resolve the error.

emmrecs wrote on 4/17/2019, 6:00 AM

@cloeterrell

Welcome to the Magix forums.

If you read all the comments in this thread you will see the OP was able to resolve his problem only by a total reinstall of Windows! There does not seem to be any alternative method of dealing with it.

Are you experiencing this problem? If so, I suggest you start a new thread with full details of your computer (see this post for the details we need) the name, variant and version number of the Magix software you want to install/use, along with the actual wording of any error message(s) you receive.

Jeff
Forum Moderator

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, AMD Radeon R7 360 and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Photo Story Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Reaper, Adobe Audition CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

ralftaro wrote on 4/18/2019, 6:34 AM

Our experience with the MSXML 4.0 SP3 Parser sub installer in the various MAGIX product installers over the past few months was that this will now typically result in an error message during the installation process on Windows 10, but you will end up with a functional installation of the main program. Obviously, some users get confused by the error during the installation procedure, but it's no reason to worry. Your program will be functional and doesn't depend on the MSXML 4.0 components any longer. We have therefore also gone ahead and removed that sub installer from the most current MAGIX installers. So, I assume anyone still experiencing this would be using an older Music Maker version. If that is the case, you might want to grab the current one instead:

http://dl03.magix.net/musicmaker.exe

By entering your old serial number (going back to version 18 a.k.a. "MX" of Music Maker) into the "Activate Edition" dialogue of the current version, you will be able to unlock the feature set and software instruments associated with that version free of charge.

Cheers!

 

Nikmartin wrote on 5/13/2019, 12:01 AM

Thanks for sharing your views.