Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

Possible .NET Framework 3.5 installation failure caused by broken MSXML registration

Possible .NET Framework 3.5 installation failure caused by broken MSXML registration

Rate This
  • Comments 65

The .NET Framework 3.5 can fail to install on a system where MSXML is not properly registered.  There is a custom action that runs during .NET Framework 3.5 setup that tries to use some APIs in MSXML to modify some information in the web_mediumtrust.config file that is a part of the .NET Framework 2.0.  In the cases that we've seen of this issue so far, one of the MSXML CLSID values was somehow unregistered on the system, and that causes this custom action to fail.

How to diagnose this issue from the .NET Framework 3.5 setup log file

This issue will cause the following information to be written to the verbose MSI log file for the .NET Framework 3.5 component (named %temp%\dd_net_framework35_MSI*.txt):

MSI (s) (58:94) [11:11:11:829]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI35C6.tmp, Entrypoint: ExecXmlConfig
MSI (s) (58:F0) [11:11:11:829]: Generating random cookie.
MSI (s) (58:F0) [11:11:11:829]: Created Custom Action Server with PID 4936 (0x1348).
MSI (s) (58:74) [11:11:11:860]: Running as a service.
MSI (s) (58:00) [11:11:11:860]: Hello, I'm your 32bit Elevated custom action server.
ExecXmlConfig:  Error 0x80040154: failed to load XML file: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_mediumtrust.config
MSI (s) (58!50) [11:11:11:954]: Product: Microsoft .NET Framework 3.5 -- Error 25541.Failed to open XML file C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_mediumtrust.config, system error: -2147221164

How to work around this issue

You can use one of the following options to work around this issue if you encounter it during .NET Framework 3.5 setup.  Note that these workarounds are only useful for this exact error and HRESULT value.  They will not help fix all possible .NET Framework 3.5 setup failures.

  1. Re-register msxml3.dll by running regsvr32 msxml3.dll
  2. Re-install MSXML3 by downloading and installing the package from http://www.microsoft.com/downloads/details.aspx?familyid=28494391-052b-42ff-9674-f752bdca9582

More details about the root cause of this issue

In the example log file above, the HRESULT value is 0x80040154, which means that a class is not registered.  On systems where we have seen this error, the root MSXML CLSID is listed in the registry at the following location:

[HKEY_CLASSES_ROOT\Msxml2.DOMDocument\CLSID]
@="{F6D90F11-9C73-11D3-B32E-00C04F990BB4}"

However, the following sub-key for this CLSID was not present on this system:

[HKEY_CLASSES_ROOT\CLSID\{F6D90F11-9C73-11D3-B32E-00C04F990BB4}]

The suggested workarounds listed above will re-register this CLSID, which has fixed this issue in the cases we have seen of this error so far.

  • PingBack from http://msdnrss.thecoderblogs.com/2007/11/02/possible-net-framework-35-installation-failure-caused-by-broken-msxml-registration/

  • .NET Framework 3.5 e MSXML

  • Thanks a lot!

    Been looking for the problem for a while. Unregistering and registering msxml3.dll fixed it.

    Regards, Jose

  • Great!!!!!

    It works!!!! Thanks!!!!

  • こんにちは! フォーラム オペレーターの服部 清次です 皆さん、連休モードはもう抜けましたか? 僕は今日からさっそく、 3 連休でスリープ モードに入っていた頭の中の OS を復帰させて、翻訳に励んでいます。

  • Hi I am installinf vs2008 on windows 7 RTM and havinf the error 25541. I have tried the work arrounds but it remins the same error. Can you give any suggestion.

  • Hi Jossy81 - I'm not sure if your error has the same root cause as this .NET Framework error.  Can you please use the tool described at http://blogs.msdn.com/astebner/archive/2007/11/21/6458047.aspx to gather your VS 2008 setup log files, post the logs to a file server (such as http://skydrive.live.com) and then reply here with a link I can use to download the log files so I can take a look and see if I can figure anything out about the cause of this error?

  • Hello Aaron,

    I am having the same problem as astebner.  I have completed all the steps highlighted above, and still no success.

    I have loaded my logs to: http://cid-f412b5a647c8e0de.skydrive.live.com/browse.aspx/.Public?uc=1

    Any assistance you could provide would be appreciated.

    Thanks!

    Michael

  • Hi Maas1701 – This is the exact error that I see in your logs:

    ExecXmlConfig:  Error 0x8007006e: failed to load XML file: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_mediumtrust.config

    The error code is different than the one described above in this blog post, so I’m not surprised that the workaround listed here didn’t work in this case.  This error code 0x8007006e means “The system cannot open the device or file specified.”  Can you check and see if this file exists on your system, and if so, if there are any settings on it that would prevent it from being opened (for example – is it marked as compressed or encrypted or something like that?)

  • Hi,

    I am getting the following error:-

    [07/21/10,21:02:59] Microsoft .NET Framework 3.5 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603

    [07/21/10,21:03:16] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.5 'package' is not installed.

    I tried the above steps, but no luck!

    Any clue!

  • Hi Paul - Error 1603 just means that setup failed, and there are many possible causes for that.  This blog post describes only one of the possible causes.  In order to diagnose this further, we'll need to look at your log files and see what the exact root cause of the failure is.  Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to gather all of your log files, then post the file named %temp%\vslogs.cab that this tool creates to a file server (such as http://skydrive.live.com), then reply back here with a link I can use to download your logs and take a further look?

  • I have problem while installing visual studio 2008

    09/03/10,09:55:17] Microsoft .NET Framework 3.5: ***ERRORLOG EVENT*** : Error code 1603 for this component means "Fatal error during installation.

    "

    [09/03/10,09:55:17] Setup.exe: AddGlobalCustomProperty

    [09/03/10,09:55:17] Microsoft .NET Framework 3.5: ***ERRORLOG EVENT*** : Setup Failed on component Microsoft .NET Framework 3.5

    [09/03/10,09:55:17] Setup.exe: GetGlobalCustomProperty - Property: {BBE1827C-F2FD-4FDA-A6D6-C83B62FFFDCA} - PropertyName: compfailed - Value: 0

    [09/03/10,09:55:17] Microsoft .NET Framework 3.5: CBaseComponent::LaunchWatson() - Obtained CSetupWatson instance

    [09/03/10,09:55:17] Microsoft .NET Framework 3.5: ISetupManager::GetGlobalCustomProperty() failed to find global prop in CBaseComponent::GetGlobalCustomProperty()

    [09/03/10,09:55:17] Microsoft .NET Framework 3.5: ISetupManager::GetGlobalCustomProperty() failed to find global prop in CBaseComponent::GetGlobalCustomProperty()

    [09/03/10,09:55:17] Microsoft .NET Framework 3.5: CBaseComponent::LaunchWatson() - Creating a PreReq Watson report with manifest: C:\DOCUME~1\MOONLI~1.RAW\LOCALS~1\Temp\MAN125.tmp

    [09/03/10,09:55:17] Microsoft .NET Framework 3.5: CBaseComponent::LaunchWatson() - Using manifest: C:\DOCUME~1\MOONLI~1.RAW\LOCALS~1\Temp\MAN125.tmp

    [09/03/10,09:55:17] Microsoft .NET Framework 3.5: ISetupManager::GetGlobalCustomProperty() failed to find global prop in CBaseComponent::GetGlobalCustomProperty()

    [09/03/10,09:55:17] Microsoft .NET Framework 3.5: CBaseComponent::LaunchWatson() - Setting the property CustomCoreProp_WatsonManifestReady to use the GenComp Manifest.

    [09/03/10,09:55:17] Setup.exe: AddGlobalCustomProperty

    [09/03/10,09:55:17] Microsoft .NET Framework 3.5: CBaseComponent::LaunchWatson() - Completed

    [09/03/10,09:55:17] Setup.exe: GetGlobalCustomProperty - Property: {2B7DE335-914B-476F-AF77-E9EF03938188} - PropertyName: Component Number - Value: 3

    [09/03/10,09:55:17] Setup.exe: GetGlobalCustomProperty - Property: {2B7DE335-914B-476F-AF77-E9EF03938188} - PropertyName: Component Number - Value: 3

    please if any one know how to solve this problem, help me urgently

  • Hi Rawaa - Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to gather all of your .NET Framework setup log files, then post the file named %temp%\vslogs.cab that this tool creates on a file server (such as http://skydrive.live.com), then reply here and provide a link that I can use to download your log files and take a look?

  • Reregistering the DLL fixed this issue for me.  I was spending hours trying to fix it.  Looking at the logs helped find the exact error message that was preventing it from installing.

    Thanks.

  • I followed your directions above and have posted the vslogs.cab to the following link:  

    cid-596dad0f029a45f8.skydrive.live.com/redir.aspx!596

    Thanks in advance to any assistance you may be able to offer to me;-)

    Chris

    (I removed dot net framework 2.0 & attempted to reinstall before reading the directions to run the tool above)

Page 1 of 5 (65 items) 12345
Leave a Comment
  • Please add 1 and 7 and type the answer here:
  • Post