Help me help you if you have setup bugs


I’ve gotten some email questions from customers about setup failures that they’ve seen on their computers.  Some of them are 1935 errors that match some of the previous blog posts I’ve written, some are .NET Framework errors, and some are general problems getting some program installed.

I cannot guarantee that I will be able to help solve all setup-related problems you may encounter, but I can guarantee that I will take a look and try to help if I can.  In order to do so I would like to ask that you try to gather some detailed information and send it to me if you contact me via email to aid in troubleshooting and debugging:

  1. As much detail about the error message as possible, including the full text of any error messages.
  2. Any troubleshooting steps that you have already tried, including links to any of my other blog posts that you’ve already tried.
  3. Most importantly – log files from the setup if at all possible.  You can zip and upload log files to a file server of your choice and include a link to the log files when you contact me.  My preference is http://skydrive.live.com because it is free, gives you a lot of storage space, and doesn’t contain annoying ads to try to get you to pay for “premium” services like faster download speeds.

Most setups are Windows Installer MSIs.  For those products, you can enable verbose logging by setting a couple of registry values and then reproducing the problem.  Here are a set of steps you can use to gather a Windows Installer verbose log file:

Important note – some MSI-based setups, including the .NET Framework 2.0, 3.0, 3.5 and higher, will not create log files named %temp%\msi*.log even if using the instructions listed below.  Please see this blog post for more details about why that is the case and also for a list of some products that I know of that use different log file creation logic and the locations of the log files that they create.

  1. If you are running Windows XP or older:  Click on the Start menu, choose Run, type cmd and click OK
  2. If you are running Windows Vista or newer:  Click on the Start menu, choose All Programs, then Accessories, then right-click on the item named Command prompt and choose Run as administrator
  3. Copy this command into the cmd prompt and press enter to run it:  reg add “HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer” /v Debug /t REG_DWORD /d 7 /f 
  4. Copy this command into the cmd prompt and press enter to run it:  reg add “HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer” /v Logging /t REG_SZ /d voicewarmupx! /f
  5. Re-run the setup and let it fail one more time
  6. Go to your temporary folder (go to the Start menu, choose Run, and type %temp%)
  7. Locate a file named msi*.log (where * is a randomly generated set of letters and numbers)
  8. Zip the msi*.log file (because it tends to be very large but since it is text it compresses nicely)
  9. Run this command in the cmd prompt:  reg delete “HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer” /v Debug /f
  10. Run this command in the cmd prompt:  reg delete “HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer” /v Logging /f
  11. Upload the zipped log files to a file server such as http://skydrive.live.com

<update date=”3/27/2007″> Changed steps to enable/disable verbose logging to not require downloading .reg files from my file server </update>

<update date=”2/27/2008″> Added a link to a new blog post with information about some products that create their own verbose log files and therefore do not create %temp%\msi*.log, even when the verbose logging policy is enabled on the system. </update>

<update date=”12/2/2010″> Added information about uploading log files to http://skydrive.live.com. </update>

<update date=”11/17/2011″> Added clarifications to steps 2 and 3 to indicate that the commands need to be run separately, not as a single command. Also added a note about running as administrator on Windows Vista or later. </update>

 

Comments (76)

  1. I don’t have a particular issue at the moment, but the most famous setup issue I have seen is the conflict between Acrobat Reader and Windows Journal Viewer such that launching Acrobat Reader triggers a reinstallation of Windows Journal Viewer. When the Journal Viewer was installed via Windows Update instead of separate download, this leads to a near infinite loop since the installation sources are unavailable. If you can shed detailed light on that issue, that’d be great.

  2. This type of reinstallation is a Windows Installer feature known as resiliency. Basically it has detected that some part of Windows Journal Viewer is broken and triggers a repair to fix it.

    This is very similar to a situation I described in a post a while back regarding the .NET Framework – http://blogs.msdn.com/astebner/archive/2004/08/24/219764.aspx.

    Just like Windows Journal Viewer, the .NET Framework is packaged as a self-extracting EXE that you install from the %temp% folder, and that the source location is deleted for after setup completes. So if a resiliency repair is triggered, the installation source is unavailable.

    I describe how to locate the installation source for the .NET Framework in my previous post. For other products such as Windows Journal Viewer, you would need to re-download the setup package and save it to your machine and then figure out what command line switches to use to extract it to a local folder. Then you should be able to browse to that folder if a resiliency repair happens, and hopefully the repair will fix the issue.

    I say "hopefully" because I have seen cases like this where the repair did not fix the underlying issue for one reason or another, and the machine was essentially stuck in this state. This happened to me recently – I have Windows Messenger since I am running Windows XP SP2, but then I also installed the MSN Messenger 7.0 beta. One of the recent critical updates tried to patch Windows Messenger but did not work correctly because I also had MSN Messenger installed. So I eventually found a Windows Messenger repair getting kicked off every time I tried to send an IM. I couldn’t get it fixed by repairing Windows Messenger so I eventually had to uninstall both and then reinstall them.

  3. I got a question from a customer who is trying to use the instructions in this blog post to perform a…

  4. The following log files are produced during Visual Studio .NET 2003, .NET Framework 1.1 and J# redistributable…

  5. The following log files are produced during Visual Studio .NET 2002 and .NET Framework 1.0 setup

    Visual…

  6. The Product Feedback web site can be used to report bugs in Visual Studio, the .NET Framework and other…

  7. Microsoft has created what I think is a really cool mechanism for customers to report bugs and suggestions…

  8. Abi says:

    Hi,

    I am having problems trying to install Nokia PC Suite, I receive the following error:

    Error 1935

    An error occurred during the installation of assemly ‘Microsoft.msxmL2, publickeytoken=’6bd6b9abf345378f".version="4.20.9818.0" type="win32" processor architechture ="x86" Please refer to help and support for more information. HRESULT: 0x80070002

    Following this is get a nokia window pop up saying: Rolling back action

    Followed by:

    Error 1603 – fatal error during installation; Consult windows installer help msi.chm or MSDN.

    I have tried to follow your instructions above but I seem to fail on step one. I don’t get an option to select YES to add the keys to the registry. Please help!!

  9. Abi – can you please try the workarounds for this error that are listed at http://blogs.msdn.com/astebner/archive/2005/02/01/364375.aspx and see if any of them resolve the issue that you are seeing?

  10. Sven says:

    I had the same problem. Everything went well after I turned off my spyware shield and firewall.

  11. Tim Whelan says:

    Hi,

    I am a student beginning my final year dissertation and i am having trouble trying to install Visual Studio .Net 2003 on my NEW pc at home. I have taken a picture of the setup failed screen and the problems it has trying to find log files etc. I have also followed your steps to create a log of the errors when i try to reinstall it. I am just wondering if there is anyy wayi can send the log files to you to have a look at.Thanks in advance

    Tim

  12. Tim Whelan says:

    my email address is tadhg88@gmail.com by the way….. thanks again

  13. Hi Tim – I will contact you via email so you can send me your log files. I’m sorry you’re running into this problem….

  14. William says:

    I am caught in an infinite loop vortex of some sort, I have tried everything I can to fix my Adobe/Windows Journal Viewer problem and nothing works. I ALWAYS get the same error message even when I point the installer to the MSI file installed to a temp folder, can’t fix, can’t uninstall can’t stand this any longer. Asside from scratching my whole HD, and dealing with Microsoft again about my keys, do you have any suggestions? BTW, your information has been, thus far, the BEST I have found on the entire internet. My compliments to you.

  15. Hi William – I would suggest trying to use the MSI Cleanup Utility to forcibly uninstall the program that is popping up tihs error message asking for the original MSI file in the temp directory (I can’t tell from your description whether the broken program is Adobe or Windows Journal Viewer from your description above).

    You can find the MSI Cleanup Utility at http://support.microsoft.com/default.aspx?scid=kb;en-us;290301.

    After using this tool to uninstall, you should be able to install the product again and hopefully this infinite repair loop will be broken and things will work correctly.

    Let me know how it goes for you please. Also, thanks for your feedback on my blog, it is comments like this that keep me going 🙂

  16. Winnie says:

    sorry.mine is error 1603 also.but when i was checking my PC,the error also was said that cannot access the net work error 1603.what can i do???

  17. Jody says:

    After saving msidebug.reg it is saved as a note pad file and there is no option to add it to the reg – I have not worked with regedit in a long time and do not want to make a mistake editing what to do

  18. Hi Jody – I have to save the files as text files because my file server will not allow me to save files with the .reg extension. You will need to save the file to your desktop and then rename it from msidebug.reg.txt to msidebug.reg. After you rename it, you will be able to double-click on it and add it to your registry.

  19. Keller says:

    The Debug logfile on the XP SP2 workstation I was troubleshooting was WIXTEXT.log instead of MSIxxxx.log. Turned out to be some issue with a German Office XP language pack causing issues with other MSI installed software after the German Office 2003 language pack was installed.

  20. Alma Rosa says:

    j# redistributlable install error just installing Vs net 2003

  21. Hi Alma – Can you please gather the J# log files listed at http://blogs.msdn.com/astebner/articles/447004.aspx and send them to me at Aaron.Stebner (at) microsoft (dot) com so I can try to take a look and see if I can figure out how to fix this issue on your system?

  22. johnywhy says:

    Hi

    Setup hangs about 80% through "Loading installation files"

    You can retrieve my log file here:

    http://rapidsharing.com/download.php?id=AAA96B60

    or

    http://tinyurl.com/gqkta

    thx

  23. Hi Johnywhy – I took a look at the log file and I can’t find anything in there to indicate why setup is hanging like that.  You are entited to a free technical support case for setup-related issues such as this, so I would suggest contacting Microsoft technical support for further troubleshooting assistance.  I’m sorry I’m not able to be more helpful here.

  24. johnywhy says:

    hi

    i checked microsoft online support, and only the full paid versions are listed as eligible for support.

    http://support.microsoft.com/select/?LN=en-us&x=9&y=9&target=assistance&c1=501

    or

    http://tinyurl.com/j5eo7

    johny

  25. I received a mail from a customer this week regarding an installation failure that proved to be fairly…

  26. Recently I started rebuilding my personal laptop and made the decision to see whether I could get away

  27. A while back, I posted a list of instructions that can be used to enable Windows Installer verbose logging

  28. A while back, I posted a list of instructions that can be used to enable Windows Installer verbose logging

  29. A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installation

  30. A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installation

  31. sba says:

    I’m hit by the transient resiliency repair window…

    All I get in the verbose MSI log is:

    === Verbose logging started: 2008/04/09  11:55:45  Build type: SHIP UNICODE 3.01.4000.4039  Calling process: I:PROGRA~1MI1933~1OFFICE11WINWORD.EXE ===

    MSI (c) (E4:70) [11:55:45:223]: Resetting cached policy values

    MSI (c) (E4:70) [11:55:45:223]: Machine policy value ‘Debug’ is 7

    MSI (c) (E4:70) [11:55:45:223]: ******* RunEngine:

              ******* Product: {9AE192E3-7B50-4EF0-9993-3B3280240AD2}

              ******* Action:

              ******* CommandLine:  ADDDEFAULT=_MainFeature

    MSI (c) (E4:70) [11:55:45:238]: Client-side and UI is none or basic: Running entire install on the server.

    MSI (c) (E4:70) [11:55:45:238]: Grabbed execution mutex.

    MSI (c) (E4:70) [11:55:45:801]: Cloaking enabled.

    MSI (c) (E4:70) [11:55:45:801]: Attempting to enable all disabled priveleges before calling Install on Server

    MSI (c) (E4:70) [11:55:45:847]: Incrementing counter to disable shutdown. Counter after increment: 0

    MSI (s) (5C:4C) [11:55:46:160]: Grabbed execution mutex.

    MSI (s) (5C:04) [11:55:46:160]: Resetting cached policy values

    MSI (s) (5C:04) [11:55:46:175]: Machine policy value ‘Debug’ is 7

    MSI (s) (5C:04) [11:55:46:175]: ******* RunEngine:

              ******* Product: {9AE192E3-7B50-4EF0-9993-3B3280240AD2}

              ******* Action:

              ******* CommandLine:  ADDDEFAULT=_MainFeature CURRENTDIRECTORY="H:" CLIENTUILEVEL=2  CLIENTPROCESSID=4580

    MSI (s) (5C:04) [11:55:46:175]: Machine policy value ‘DisableUserInstalls’ is 0

    MSI (s) (5C:04) [11:55:46:207]: MainEngineThread is returning 1605

    MSI (c) (E4:70) [11:55:46:222]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

    MSI (c) (E4:70) [11:55:46:222]: MainEngineThread is returning 1605

    MSI (c) (E4:C8) [11:55:46:285]: Entering MsiProvideComponentFromDescriptor. Descriptor: ‘]gAVn-}f(ZXfeAR6.jiHandWritingFiles>Wz_B=’plK=LZgdoVXdYG, PathBuf: 127A0C, pcchPathBuf: 127A08, pcchArgsOffset: 127968

    MSI (c) (E4:C8) [11:55:46:285]: Machine policy value ‘DisableUserInstalls’ is 0

    MSI (c) (E4:C8) [11:55:46:378]: MsiProvideComponentFromDescriptor is returning: 0

    === Verbose logging stopped: 2008/04/09  11:55:46 ===

    Any clue? How do I determine why that product is "needed" by e.g. Word and how to remove that dependency?

    P.S. msiexec /x ‘{9AE192E3-7B50-4EF0-9993-3B3280240AD2}’ tells me the product is not installed

  32. Hi Sba – For resiliency repairs like this, I typically look at the application event log first.  There should be 2 warnings logged at the time that you see this repair pop up on your system.  They will be from the source named MsiInstaller.  They should list the product code of the MSI being repaired.  One of the warnings should list the exact component GUID of the component that is being accessed that initiates the health check and the other warning should list the exact component GUID and resource that is missing that triggers the repair.

    Hopefully this helps you narrow this down further.

  33. A while back, I posted a list of possible log files for .NET Framework 3.5 and Visual Studio 2008 setup

  34. Nicol@s says:

    Hi Aaron,

    I’m trying to install a Win32 Shared assembly using IS12. I’ve got Error 1935.An error occurred during the installation of assembly component.

    The HRESULT is 0x800736B5 (The manifest file contains one or more syntax error). I have also a line with "MsiProvideAssembly is returning: 1607"

    Regards

  35. Hi Nicol@s – This sounds like a problem with the files that you are adding to your setup and/or a problem with the authoring of your MSI.  I’d suggest checking the syntax of your Win32 assembly manifest first.  Also, error code 1607 means "the component identifier is not registered."  I don’t have enough familiarity with InstallShield to know what to suggest to try to resolve that type of error, but it sounds like something with the way you are authoring your components.  Maybe they have an FAQ on their site that could help suggest some fixes, or maybe someone on their forums would be able to suggest some things for you to check in your setup authoring.

  36. Nicol@s says:

    Hi Aaron,

    I’m not sure there was a syntax error in my manifest. I solved my problem renaming the manifest file (it was not the same name as in the manifest file itself) and changing the publicKeyToken value (it was a wrong value, because I have 3 chained certificates, I do not execute the pktextract on the good one).

    Regards

  37. Question: I am attempting to automate the installation of the Visual Studio 2008 SDK , but have not been

  38. koksi says:

    hi

    i try now xx hours to install vcs btw net framework 3.5 sp1

    error:

    [11/07/08,22:51:43] Microsoft .NET Framework 3.0 SP2 x86: [2] Error: Installation failed for component Microsoft .NET Framework 3.0 SP2 x86. MSI returned error code 1603

    i open now dd_dotnetfxinstall and search for value:3

    i found that

    [11/08/08,03:02:29] Setup.exe: GetGlobalCustomProperty – Property: {2B7DE335-914B-476F-AF77-E9EF03938188} – PropertyName: Component Number – Value: 3

    [11/08/08,03:02:29] Setup.exe: GetGlobalCustomProperty – Property: {2B7DE335-914B-476F-AF77-E9EF03938188} – PropertyName: Component Number – Value: 3

    i have them around 20times

    i olso look on file called MSIdc507 but here i dont find a value 3

    thx i realy end of my power about this 🙁

  39. Hi Koksi – The file dd_dotnetfxinstall35.txt is not a verbose MSI log, so searching for "return value 3" in that log won’t help.  You will need to look at the verbose log file for the .NET Framework 3.0 SP2.  .NET Framework setup configures verbose logging by default, and the logs will be in the locations listed in the blog post at http://blogs.msdn.com/astebner/archive/2008/04/30/8445569.aspx.

    Specifically, you will want to look for a log named %temp%dd_net_framework30*.txt, and then search for "return value 3" in that log.

    Hopefully this helps.

  40. koksi says:

    so now i should have correct file

    dd_NET_Framework30_setupFB

    at least i saw in that log "Verbose logging stopped"

    MSI (s) (7C:8C) [05:12:58:171]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is ‘3’.

    MSI (s) (7C:8C) [05:13:07:343]: Note: 1: 2262 2: Error 3: -2147287038

    MSI (s) (7C:8C) [05:13:07:343]: Transforming table Error.

    from them i have many

    MSI (s) (7C:8C) [05:13:07:359]: Attempting to delete file C:WINDOWS.0Installerf6931.msp

    MSI (s) (7C:8C) [05:13:07:359]: Unable to delete the file. LastError = 32

    (i try to locate this file but could not find them)

    i copy them out what i think that could be intresting

    exactly that i not find value 3 or value:3

    btw i olso tryed msciuu2 cleaning tool and dotnetfx_cleanup_tool olso without success 🙁

    thx for your time

  41. Hi Koksi – Could you please zip your .NET Framework log files and post them to a file server (such as skydrive.live.com), and then post a link back here so I can download them and take a look to see if I can figure out what is causing this installation failure on your system?

  42. koksi says:

    hi

    realy thx for your time

    i upload some fils

    http://www.twisterflasher.net/neterrors.rar

  43. Hi Koksi – Thanks for posting these log files.  It looks like you’re running on a German version of Windows, so you cannot search for the string "return value 3" because that text gets translated in non-English log files.  In your logs, I had to search for "Rückgabewert 3" instead.

    Here is the exact error that is causing the failure on your system:

    Fehler 1321. Installer besitzt keine ausreichenden Berechtigungen, um diese Datei zu verändern: C:ProgrammeReference AssembliesMicrosoftFrameworkv3.0System.IdentityModel.dll.

    This means that there is some kind of permission problem to one of the folders on your system.  I’d suggest trying the steps listed at http://blogs.msdn.com/astebner/archive/2006/09/04/solving-setup-errors-by-using-the-subinacl-tool-to-repair-file-and-registry-permissions.aspx to try to fix this issue.

    Hopefully this helps!

  44. llhk186 says:

    Hi Aaron,

    I encountered a error when installing the dotnet framework 3.0. I can’t find any "return value 3" string in my log file. Would you please take a look on my log file? You can access it from the following link:

    http://www.geocities.com/llhk186/MSIbae0f.zip

    Many Thanks,

    Regards

  45. Hi Llhk186 – Some products create their own verbose logs by default, and when they do that, using the steps in this blog post to create verbose logs won’t work.  There is a link at http://blogs.msdn.com/astebner/archive/2008/02/27/7927123.aspx that you can use to find the names and locations of the log files created by .NET Framework 3.0 setup.  Can you please gather those logs and post them to your file server, then reply back here with a link to the logs so I can take a look and see if I can figure anything out?

  46. koksi says:

    hi

    SubInACL tool olso not help me

    so i try now to install from a DVD and i could not believe now it work 🙂

    only some error with sql2005 server.. but this i dont need at moment

    thx for help

  47. lulu24 says:

    Hey there. Can you help?

    I’m on Vista SP1, trying to install OpenOffice 3.1 (or any for that matter) and always seem to receive the error "error occurred during installation of assembly ‘policy 9.0.Microsoft.VC90.CRT,publicKeyToken=!1fc8b3b9a1e18e3b",version="9.0.21022.8",processorArchitecture="x86",type="win32policy"

    I don’t quite know what any of this means… I only JUST reinstalled Vista so it can’t be a severe problem 😐

    Any advice?

  48. Hi Lulu24 – Do you have a full log file from this installation failure?  There are a lot of possible causes for a 1935 error, and the full log usually includes more detailed error information to help narrow down the problem.

    This assembly that you list in your error is a VC runtime assembly.  The VC runtime assemblies are Win32 assemblies as opposed to managed assemblies, and on Windows Vista and later, Win32 assemblies are installed by the same infrastructure and engine as OS updates and hotfixes.  This type of error typically means that there is something wrong with the OS update installation engine on the system.

    I have posted some information about how I typically go about narrowing down OS update installation problems on Windows Vista and higher in the following blog posts:

    http://blogs.msdn.com/astebner/archive/2009/03/12/9472695.aspx

    http://blogs.msdn.com/astebner/archive/2009/01/09/9303167.aspx

    Hopefully this information will be helpful for you as well.

  49. swoodard says:

    Aaron,

    Is there a recommended workaround for Visual Studio installation erroring on Framework 2.0 because Framework 2.0 SP2 is installed?

    That is the conclusion I came to based on the below snip of the log.  

    ——————

    [07/27/09,11:56:39] Setup.exe: AddGlobalCustomProperty

    [07/27/09,11:56:39] Microsoft .NET Framework 2.0: ***ERRORLOG EVENT*** : Error code 1603 for this component means "Fatal error during installation.

    "

    [07/27/09,11:56:39] Setup.exe: AddGlobalCustomProperty

    ——————-

    Attempting to run the Framework directly from the embedded directory gave me a "The version of Framework you are installing is incompatible…" error message.  The link on the error message states you can’t install Framework 1.0 over 1.0 SP1.  So I am guessing that perhaps updating the source file to Framework 2.0 sp2 would eliminate the issue.

    Am I on the right track or offbase in my assumptions?

    -Steve

    PS Thanks for your help

  50. Hi Swoodard – Are you talking about VS 2005 in this scenario?  If so, as long as you don’t yet have VS 2005 installed, the VS 2005 installer should detect that you already have the .NET Framework 2.0 SP2 installed and skip that component.  If you already have VS 2005 installed and are running in repair mode, you will see an error when it tries to repair the .NET Framework 2.0 in this scenario.  In that case, you can just ignore the error because it will repair the other components in VS 2005 despite that error.  You can run the repair for the .NET Framework 2.0 SP2 using its separate Add/Remove Programs entry.

    If you see this error during initial install, can you please zip your VS 2005 setup logs and post them on a file server, then reply back here with a link to the logs so I can download them and take a look?  You can find a list of VS 2005 setup log files at http://blogs.msdn.com/astebner/articles/447012.aspx.

  51. MikeMio says:

    Hi Aaron,

    Thanks for your very kind offer to help with setup bugs. I am not entirely sure if this is a bug or my own fault but perhaps you can tell me.

    I have had several users of report problems with an installation package lately. The error message are various but all seem to be related to the system merge modules. The majority of installations are uneventful but the frequency of these error seems to have increase since our last few updates.

    The two most common errors are:

    The application has failed to start because its side-by-side configuration is incorrect

    and

    An error occurred during the installation of assembly

    The package in question installs an unmanaged program, some dlls, content and  Microsoft_VC80_CRT_x86.msm,  Microsoft_VC80_MFC_x86.msm, policy_8_0_microsoft_vc80_crt_x86.msm and policy_8_0_microsoft_vc80_mfc_x86.msm modules. I am using a VS2005 setup project.

    For the details, I will concentrate on one particular case where I have more detailed information:

    The OS is Vista x64 with auto update on. ( I have some hardware info)

    The installer error is:

    An error occurred during the installation of assembly

    ‘policy.8.0 Microsoft.VC80.MFC,type="win32-policy",version="8.0.50727.4053" ,publicKey

    Token="1fc8b3b9a1e18e3b" ,processorArchitecture="x86" . Please refer to Help and Support for more information.

    I have the installer’s log. I have posted a snippet below and can post more if you tell me what you would like to see.

    One thing that may or may not be relevant is a warning that occurs during the package build.

    WARNING: Two or more objects have the same target location (‘[payload_ul]8.0.50727.4053.cat’)

    WARNING: Two or more objects have the same target location (‘[payload_ul]8.0.50727.4053.cat’)

    WARNING: Two or more objects have the same target location (‘[policydir]8.0.50727.4053.policy’)

    WARNING: Two or more objects have the same target location (‘[policydir]8.0.50727.4053.policy’)

    WARNING: Two or more objects have the same target location (‘[policydir]8.0.50727.4053.cat’)

    WARNING: Two or more objects have the same target location (‘[policydir]8.0.50727.4053.cat’)

    WARNING: Two or more objects have the same target location (‘[payload_ul]8.0.50727.4053.policy’)

    WARNING: Two or more objects have the same target location (‘[payload_ul]8.0.50727.4053.policy’)

    This seems to happen when I use the policies, listed as dependencies, for both the mfc and crt msm’s.

    (i.e. both  policy_8_0_microsoft_vc80_crt_x86.msm and policy_8_0_microsoft_vc80_mfc_x86.msm)

    If I exclude one or the other I don’t see the warning.

    Thanks again for any insight you can give (even if it is just: post the question to xxxx)

    Cheers,

    Mike

    installer’s log  snippet .

    ====================================

    MSI (s) (90:10) [17:09:24:022]: Note: 1: 1935 2: {68B7C6D9-1DF2-54C1-A01F-C8B3B9A1E18E} 3: 0x8007371B 4: IAssemblyCacheItem 5: Commit 6: policy.8.0.Microsoft.VC80.MFC,type="win32-policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"

    MSI (s) (90:10) [17:09:24:022]: Assembly Error (sxs): To get more diagnostic information, enable the Component Based Servicing Log.

    MSI (s) (90:10) [17:09:24:022]: Note: 1: 2262 2: Error 3: -2147287038

    MSI (c) (C8:2C) [17:09:24:024]: Note: 1: 2262 2: Error 3: -2147287038

    DEBUG: Error 2835:  The control ErrorIcon was not found on dialog ErrorDialog

    The installer has encountered an unexpected error installing this package.

    This may indicate a problem with this package.

    The error code is 2835. The arguments are: ErrorIcon, ErrorDialog,

    Error 1935. An error occurred during the installation of assembly ‘policy.8.0.Microsoft.VC80.MFC,type="win32-policy",

    version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"’. Please refer to Help and Support for more information.

    HRESULT: 0x8007371B. assembly interface: IAssemblyCacheItem, function: Commit, component: {68B7C6D9-1DF2-54C1-A01F-C8B3B9A1E18E}

    MSI (s) (90:10) [17:10:11:105]: Note: 1: 2262 2: Error 3: -2147287038

    MSI (s) (90:10) [17:10:11:105]: Product: SiteSpinner V2 —

    Error 1935. An error occurred during the installation of assembly ‘policy.8.0.Microsoft.VC80.MFC, type="win32-policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"’.Please refer to Help and Support for more information.

    HRESULT: 0x8007371B. assembly interface: IAssemblyCacheItem, function: Commit, component: {68B7C6D9-1DF2-54C1-A01F-C8B3B9A1E18E}

    Action ended 17:10:11: InstallFinalize. Return value 3.

    ====================================

  52. Hi MikeMio – The warnings that you’re seeing when you build your package (WARNING: Two or more objects have the same target location) are known issues when you include more than one of the VC runtime merge modules in your setup.  Those can be safely ignored, and should not be the cause of the installation errors that you are seeing.

    On Windows Vista and higher, Win32 assemblies (such as the VC runtime files) are installed by the same engine that installs the OS itself.  If there is something wrong with that engine or with the OS component store, it can lead to this type of failure.  I wrote some information about how I typically go about trying to diagnose and fix this type of error in the blog post at http://blogs.msdn.com/astebner/archive/2009/10/07/9904471.aspx.  I’d suggest taking a look at that to see if the information and links there help at all in your scenarios.

  53. MikeMio says:

    Hi Aaron,

    I posted the question above. I guess you are away for the holidays or just busy. Anyway, just to let you know, I am going to post this question elsewhere for now. I can post a link here if I do find a solution.

    Merry Christmas,

    Mike

  54. Hi MikeMio – I replied to your original question before I left for a holiday vacation last week.  Did the information I provided help at all?

  55. MikeMio says:

    Hi Aaron,

    Sorry, I somehow missed your post before I posted the second time. Not sure how but there you go…

    Anyway, thank you for the reply. I really do appreciate it. I have been in holiday mode lately and haven’t been following but I will read your article, rethink the problem and let you know what I come up with.    

    Hope you had a happy, restful holiday and have a happy and prosperous new year ahead.

    Cheers,

    Mike

  56. MikeMio says:

    Hi Aaron,

    Ok, well I have followed your posts and links and I think I know (just barely) what to try next but I wanted to run it by you first if you don’t mind.

    (I have included log snippets below where the installation log timestamp’s sync with the cbs.log.)

    So, reviewing the logs I see that I have the hresult 0x8007371B in both the installation log and the cbs log.

    0x8007371B tranlates to:

    ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE – One or more required members of the transaction are not present.

    This error is in the list that System Update Readiness Tool says it may fix.

    So… the next step would be to have the user install and run the System Update Readiness Tool with the hope that that will fix the problem.

    As I understand it, the Readiness Tool should apear in the Windows update list if the user has an error it can fix but he can manually download and install if it isn’t there.

    Does that sound about right? Is there anything I should do before that? or after?

    Thanks again for all your help.

    Cheers,

    Mike

    ————————————————

    Start installation log snippet  – Vista 64 bit

    ————————————————

    MSI (s) (F0:04) [09:47:29:931]: Note: 1: 1935 2: {68B7C6D9-1DF2-54C1-A01F-C8B3B9A1E18E} 3: 0x8007371B 4: IAssemblyCacheItem 5: Commit 6: policy.8.0.Microsoft.VC80.MFC,type="win32-

    policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"

    MSI (s) (F0:04) [09:47:29:931]: Assembly Error (sxs): To get more diagnostic information, enable the Component Based Servicing Log.

    MSI (s) (F0:04) [09:47:29:931]: Note: 1: 2262 2: Error 3: -2147287038

    MSI (c) (20:E8) [09:47:29:934]: Note: 1: 2262 2: Error 3: -2147287038

    DEBUG: Error 2835:  The control ErrorIcon was not found on dialog ErrorDialog

    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835. The arguments are: ErrorIcon,

    ErrorDialog,

    Error 1935. An error occurred during the installation of assembly ‘policy.8.0.Microsoft.VC80.MFC,type="win32-

    policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"’. Please refer to Help and Support for more information. HRESULT: 0x8007371B. assembly

    interface: IAssemblyCacheItem, function: Commit, component: {68B7C6D9-1DF2-54C1-A01F-C8B3B9A1E18E}

    MSI (s) (F0:04) [09:47:33:223]: Note: 1: 2262 2: Error 3: -2147287038

    MSI (s) (F0:04) [09:47:33:223]: Product: SiteSpinner V2 — Error 1935. An error occurred during the installation of assembly ‘policy.8.0.Microsoft.VC80.MFC,type="win32-

    policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"’. Please refer to Help and Support for more information. HRESULT: 0x8007371B. assembly

    interface: IAssemblyCacheItem, function: Commit, component: {68B7C6D9-1DF2-54C1-A01F-C8B3B9A1E18E}

    Action ended 9:47:33: InstallFinalize. Return value 3.

    ——————————

    End ss.log snippet

    ——————————

    ———————————————–

    Start cbs.log snippet

    ———————————————–

    2010-01-06 09:47:18, Info                  CBS    Loaded Servicing Stack v6.0.6002.18005 with Core: C:Windowswinsxsamd64_microsoft-windows-

    servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6cbscore.dll

    2010-01-06 09:47:18, Info                  CSI    00000001@2010/1/6:17:47:18.785 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7feec618c85 @0x7feec8753ae @0x7feec843ed1

    @0xffd049a8 @0xffd030c9 @0xffd03578)

    2010-01-06 09:47:18, Info                  CSI    00000002@2010/1/6:17:47:18.803 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7feec618c85 @0x7feec8b86cf @0x7feec8925d9

    @0x7feec843feb @0xffd049a8 @0xffd030c9)

    2010-01-06 09:47:18, Info                  CSI    00000003@2010/1/6:17:47:18.805 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7feec618c85 @0x7fef20a838d @0x7fef20a84ba

    @0xffd04207 @0xffd03125 @0xffd03578)

    2010-01-06 09:47:18, Info                  CBS    NonStart: Checking to ensure startup processing was not required.

    2010-01-06 09:47:18, Info                  CSI    00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition =

    @0x133fae0

    2010-01-06 09:47:18, Info                  CBS    NonStart: Success, startup processing not required as expected.

    2010-01-06 09:47:18, Info                  SXS    Install Assembly from C:WindowsWinSxSInstallTemp20100106094707699.0x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.4053_x-

    ww_b77cec8e.manifest

    2010-01-06 09:47:18, Info                  SXS    Submitting stage transaction with 6 operations

    2010-01-06 09:47:18, Info                  CSI    00000005 Performing 6 operations; 6 are not lock/unlock and follow:

     Stage (1): flags: 8 app: [Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8

    b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral]) comp: Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture

    neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral man: @0x3d06a8

     StageFile (2): flags: 8 app: [Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8

    b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral]) comp: Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture

    neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral file: [ml:22{11},l:20{10}]"mfcm80.dll" srcfile:

    @0x3d07c8

     StageFile (2): flags: 8 app: [Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8

    b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral]) comp: Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture

    neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral file: [ml:22{11},l:20{10}]"mfc80u.dll" srcfile:

    @0x3d08e8

     StageFile (2): flags: 8 app: [Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8

    b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral]) comp: Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture

    2010-01-06 09:47:18, Info                  CSI    neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral

    file: [ml:20{10},l:18{9}]"mfc80.dll" srcfile: @0x3b9bb8

     StageFile (2): flags: 8 app: [Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8

    b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral]) comp: Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture

    neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral file: [ml:24{12},l:22{11}]"mfcm80u.dll" srcfile:

    @0x3b9c48

     AddCat (14): flags: 0 catfile: @0x3b9d68

    2010-01-06 09:47:18, Info                  CSI    00000006 Creating NT transaction (seq 1), objectname [6]"(null)"

    2010-01-06 09:47:18, Info                  CSI    00000007 Created NT transaction (seq 1) result 0x00000000, handle @0x220

    2010-01-06 09:47:20, Info                  CSI    00000008@2010/1/6:17:47:20.248 CSI perf trace:

    CSIPERF:TXCOMMIT;497347

    2010-01-06 09:47:20, Info                  SXS    Submitting install transaction

    2010-01-06 09:47:20, Info                  CSI    00000009 Performing 1 operations; 1 are not lock/unlock and follow:

     Install (5): flags: 0 tlc: [Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8

    b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral]) ref: ( flgs: 00000000 guid: {27dec61e-b43c-4ac8-88db-e209a8242d90} name: [l:0]"" ncdata: [l:62{31}]"C:

    Windowssystem32msiexec.exe") thumbprint: [l:128{64}]"57d5c1e17d3b003378ace5418d822c42353f8141380788c095a600def44f4913"

    2010-01-06 09:47:20, Info                  CSI    0000000a Component change list:

    2010-01-06 09:47:20, Info                  CSI    0000000b Creating NT transaction (seq 2), objectname [6]"(null)"

    2010-01-06 09:47:20, Info                  CSI    0000000c Created NT transaction (seq 2) result 0x00000000, handle @0x29c

    2010-01-06 09:47:21, Info                  CSI    0000000d@2010/1/6:17:47:21.080 CSI perf trace:

    CSIPERF:TXCOMMIT;733104

    2010-01-06 09:47:21, Info                  CSI    0000000e Creating NT transaction (seq 3), objectname [6]"(null)"

    2010-01-06 09:47:21, Info                  CSI    0000000f Created NT transaction (seq 3) result 0x00000000, handle @0x238

    2010-01-06 09:47:21, Info                  CSI    00000010@2010/1/6:17:47:21.514 CSI perf trace:

    CSIPERF:TXCOMMIT;439235

    2010-01-06 09:47:21, Info                  SXS    Install Assembly from C:WindowsWinSxSInstallTemp20100106094710140.08.0.50727.4053.policy

    2010-01-06 09:47:21, Info                  SXS    Submitting stage transaction with 2 operations

    2010-01-06 09:47:21, Info                  CSI    00000011 Performing 2 operations; 2 are not lock/unlock and follow:

     Stage (1): flags: 8 app: [policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8

    b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral]) comp: policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA =

    PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral

    man: @0x3b9bb8

     AddCat (14): flags: 0 catfile: @0x3bb8f8

    2010-01-06 09:47:21, Info                  CSI    00000012 Creating NT transaction (seq 4), objectname [6]"(null)"

    2010-01-06 09:47:21, Info                  CSI    00000013 Created NT transaction (seq 4) result 0x00000000, handle @0x228

    2010-01-06 09:47:21, Info                  CSI    00000014@2010/1/6:17:47:21.830 CSI perf trace:

    CSIPERF:TXCOMMIT;264532

    2010-01-06 09:47:21, Info                  SXS    Submitting install transaction

    2010-01-06 09:47:21, Info                  CSI    00000015 Performing 1 operations; 1 are not lock/unlock and follow:

     Install (5): flags: 0 tlc: [policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.4053, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8

    b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral]) ref: ( flgs: 00000000 guid: {27dec61e-b43c-4ac8-88db-e209a8242d90} name: [l:0]"" ncdata: [l:62

    {31}]"C:Windowssystem32msiexec.exe") thumbprint: [l:128{64}]"81bffdab9f49ea0cc7eea7633b89d1381a501f384fb6e2698d6143ba4951cc8f"

    2010-01-06 09:47:21, Info                  CSI    00000016 Changelist shadowed missing its manifest – policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.762, pA =

    PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral

    2010-01-06 09:47:21, Error                 CSI    00000017@2010/1/6:17:47:21.851 (F) d:longhornbasewcpcomponentstorecsd_winners.cpp(953): Error

    STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null)

    [gle=0x80004005]

    2010-01-06 09:47:26, Error                 CSI    00000018 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3162# from CCSDirectTransaction::PerformChangeAnalysis(…)[gle=0xd0150024]

    2010-01-06 09:47:26, Error                 CSI    00000019 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3161# from CCSDirectTransaction::PrepareForCommit(…)[gle=0xd0150024]

    2010-01-06 09:47:26, Error                 CSI    0000001a (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3160# from CCSDirectTransaction::ExamineTransaction(…)[gle=0xd0150024]

    2010-01-06 09:47:26, Error                 CSI    0000001b (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3159# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(…)

    [gle=0xd0150024]

    2010-01-06 09:47:26, Info                  CSI    0000001c Changelist shadowed missing its manifest – policy.8.0.Microsoft.VC80.MFC, Version = 8.0.50727.762, pA =

    PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12}]"win32-policy", TypeName neutral, PublicKey neutral

    2010-01-06 09:47:26, Error                 CSI    0000001d@2010/1/6:17:47:26.813 (F) d:longhornbasewcpcomponentstorecsd_winners.cpp(953): Error

    STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null)

    [gle=0x80004005]

    2010-01-06 09:47:29, Error                 CSI    0000001e (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3315# from CCSDirectTransaction::PerformChangeAnalysis(…)[gle=0xd0150024]

    2010-01-06 09:47:29, Error                 CSI    0000001f (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3314# from CCSDirectTransaction::PrepareForCommit(…)[gle=0xd0150024]

    2010-01-06 09:47:29, Error                 CSI    00000020 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3313# from CCSDirectTransaction::GenerateComponentChangeList(…)[gle=0xd0150024]

    2010-01-06 09:47:29, Error                 CSI    00000021 (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3312# from

    Windows::COM::CPendingTransaction::ExtractInformationFromRtlTransaction(…)[gle=0xd0150024]

    2010-01-06 09:47:29, Error                 CSI    00000022 (F) HRESULT_FROM_WIN32(ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE) #3050# from

    Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(…)[gle=0x8007371b]

    2010-01-06 09:47:29, Error                 SXS    Analyze Transaction failed with 0x8007371b

    2010-01-06 09:47:38, Info                  SXS    Uninstall Assembly: policy.8.0.Microsoft.VC80.MFC,type="win32-

    policy",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"

    2010-01-06 09:47:38, Info                  SXS    Submitting uninstall transaction

    ——————————

    End cbs.log snippet

    ——————————

  57. Hi MikeMio – Yes, I’d suggest trying to download and run the System Update Readiness Tool as a next step here.  In some cases, that tool will be able to automatically fix this type of issue.  In other cases, it will report the root cause of the problem but may not be able to fix it, and you may need to try to manually fix things by using the log file that this tool creates (located at %windir%logscbschecksur.log).

    As far as I know, Windows Update will not automatically offer the System Update Readiness Tool if it detects a problem that requires it, so it will have to be downloaded manually.  In fact, some of the cases I’ve seen where this tool is needed can cause Windows Update to not offer any updates at all on a system.

    Step 3 in the blog post at http://blogs.msdn.com/astebner/archive/2009/01/09/9303167.aspx describes some steps I’ve used in the past to manually find and fix errors reported by the System Update Readiness Tool, so hopefully this might be helpful to you as well.

  58. MikeMio says:

    Hi Aaron – I posted this a few days ago but it’s not showing up so I am trying again – no need to post it twice of course.

    Mike

    —————————-

    Hey Aaron, Success!!!

    The system readiness tool appears to have done the job. After running it, the installation worked correctly.

    To recap the problem:

    After running the installation, this error appears:

    An error occurred during the installation of assembly

    ‘policy.8.0 Microsoft.VC80.MFC,type="win32-policy",version="8.0.50727.4053" ,publicKey

    Token="1fc8b3b9a1e18e3b" ,processorArchitecture="x86" . Please refer to Help and Support for more information.

    Checking the installation log and the corresponding section of the cbs log we see that the assembly failure returned an HRESULT of 0x8007371B.

    The 0x8007371B result is on the list of errors the System Update Readiness Tool can potentially address so we run the readiness tool.

    It finds and corrects some problems and the installation work now.

    Very simple once you know how;)

    Just for your information, I don’t know if this is typical but the readiness tools found a fixed a *lot* of problems. It apparently failed to replace some 3,630 missing Payload Files

    This is the System Update Readiness Tool Summary:

    Seconds executed: 25272

    Found 117971 errors

    Fixed 114337 errors

     CSI Missing Component Key Total count: 19270

     Fixed: CSI Missing Component Key.  Total count: 19270

     CSI Missing Pinned Component Key Total count: 6084

     Fixed: CSI Missing Pinned Component Key.  Total count: 6084

     CSI Missing Identity Total count: 25354

     Fixed: CSI Missing Identity.  Total count: 25354

     CSI Missing C Mark Total count: 30413

     Fixed: CSI Missing C Mark.  Total count: 30413

     CSI Payload File Missing Total count: 5192

     Fixed: CSI Payload File Missing.  Total count: 1562

     CSI F Mark Missing Total count: 37175

     Fixed: CSI F Mark Missing.  Total count: 37175

     CBS Watchlist Component Missing Total count: 4

     CSI Store Directory Missing Total count: 563

     Fixed: CSI Store Directory Missing.  Total count: 563

    Also, you had said: “As far as I know, Windows Update will not automatically offer the System Update Readiness Tool if it detects a problem that requires it.

    The reason I thought otherwise is a statement on the ‘Description of the System Update Readiness Tool’ page which said “You do not have to manually run this tool. This tool is offered automatically through Windows Update to computers that have a condition that the tool could resolve”. I may be misunderstanding that. In any case, for the above scenario it was not offered automatically.

    So… thanks once again for your generous help with this. I really appreciate it. I may never have solved it this problem without it.

    Cheers,

    Mike

  59. edgroc says:

    We have a program installer made using Wix 3.0 and have recently run into an error on one particular end user’s computer, where the install fails when trying to run a MS run time library merge module custom action (SxSInstallCA).

    The merge modules we include are:

    "microsoft_vc90_crt_x86.msm"

    "microsoft_vc90_mfc_x86.msm"

    "policy_9_0_Microsoft_VC90_CRT_x86.msm"

    "policy_9_0_Microsoft_VC90_MFC_x86.msm"

    The funny thing is that this end users computer and install has successfully run other installers which included these merge modules as well.

    An excerpt of the verbose log output just before and up to the first "return value 3" is as below.

    I have hunted around and haven’t been able to find any clues on how to debug the issue further from here. Any assistance you can provide would be greatly appreciated.

    ———–start of log excerpt ————–

    MSI (s) (2C:88) [13:02:29:500]: Doing action: InstallInitialize

    MSI (s) (2C:88) [13:02:29:500]: Note: 1: 2205 2: 3: ActionText

    Action 13:02:29: InstallInitialize.

    Action start 13:02:29: InstallInitialize.

    MSI (s) (2C:88) [13:02:29:500]: Machine policy value ‘AlwaysInstallElevated’

    is 0

    MSI (s) (2C:88) [13:02:29:500]: User policy value ‘AlwaysInstallElevated’ is 0

    MSI (s) (2C:88) [13:02:29:500]: BeginTransaction: Locking Server

    MSI (s) (2C:88) [13:02:29:500]: Machine policy value

    ‘LimitSystemRestoreCheckpointing’ is 0

    MSI (s) (2C:88) [13:02:29:500]: Note: 1: 1715 2: CCU 2.4.2

    MSI (s) (2C:88) [13:02:29:500]: Note: 1: 2205 2: 3: Error

    MSI (s) (2C:88) [13:02:29:500]: Note: 1: 2228 2: 3: Error 4: SELECT

    `Message` FROM `Error` WHERE `Error` = 1715

    MSI (s) (2C:88) [13:02:29:500]: Calling SRSetRestorePoint API.

    dwRestorePtType: 0, dwEventType: 102, llSequenceNumber: 0, szDescription:

    "Installed CCU 2.4.2".

    MSI (s) (2C:88) [13:02:33:593]: The call to SRSetRestorePoint API succeeded.

    Returned status: 0, llSequenceNumber: 904.

    MSI (s) (2C:88) [13:02:33:593]: Server not locked: locking for product

    {E67C9725-A794-4BD2-B0EA-986AC036158B}

    Action ended 13:02:33: InstallInitialize. Return value 1.

    MSI (s) (2C:88) [13:02:33:640]: Doing action: SxsInstallCA

    MSI (s) (2C:88) [13:02:33:640]: Note: 1: 2205 2: 3: ActionText

    Action 13:02:33: SxsInstallCA.

    Action start 13:02:33: SxsInstallCA.

    MSI (s) (2C:88) [13:02:33:640]: Creating MSIHANDLE (14) of type 790542 for

    thread 3720

    MSI (s) (2C:40) [13:02:33:640]: Invoking remote custom action. DLL:

    C:WINDOWSInstallerMSI1C.tmp, Entrypoint: CustomAction_SxsMsmInstall

    MSI (s) (2C:40) [13:02:33:671]: Closing MSIHANDLE (14) of type 790542 for

    thread 3720

    Action ended 13:02:33: SxsInstallCA. Return value 3.

    ———–end of log excerpt ————–

  60. Hi Edgroc – I can’t tell from the verbose log what the problem is in this case, but since it only happens on one computer, I’m guessing there is something wrong with that computer that is causing the VC++ runtime files custom actions to fail and that this problem isn’t specific to your setup package.  I would expect to see the standalone VC++ runtime redistributable to fail in the same way, so you may want to have the customer try that to double-check that.  If that also fails, then they will likely need to repair their OS to try to resolve this issue.  What version of Windows is this error being seen on?

  61. edgroc says:

    Thanks for the feedback.

    While your blog was undergoing "upgrades", we managed to determine that the .MSI file that the end user was running from was in fact corrupted!

    This certainly explains why a previous installer with the same VC++ runtime merge modules worked fine and the one in question failed.

    I thought the MSI files themselves were internally checksummed and this type of error would be caught by the installer engine, but I guess not.

  62. Sarhat says:

    when I install Python 2.7 on Windows 7 32 bit, the installation failed and I got this error

    An error occurred during the installation of

    assembly 'Microsoft.VC90.CRT, version="9.0.21022.8",publicKey

    Token="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32".  

    Please refer to Help and Support for

    more information.  

  63. Hi Sarhat – For installation issues with Win32 assemblies (like the Visual C++ runtime files) on Windows 7, I suggest using the troubleshooting information and links at blogs.msdn.com/…/9904471.aspx.

  64. Rod at Work says:

    Hi Aaron,

    I was pointed to your post on "How to locate the cause of error code 1603 in a verbose MSI log file", and in that post it lead me to this post.  I'm wondering if the registry keys and values you mention on this post, are still relevant for Windows 2008 R2 Web Servers?

  65. Hi Rod at Work – Yes, these registry keys are applicable to any version of Windows Installer on any version of Windows.  They should work fine on Windows Server 2008 R2.

  66. Rod at Work says:

    Thank you, Aaron.

  67. Manish says:

    Hi Aaron,

    I am using C# dll deferred custom action in my setup and it creates below entry in msi log files and writes all properties with 'Ignoring CustomActionData substring' <>, Can you please suggest if there is a way to hide this as this contains password entry as well. Log is added below for your reference.

    ———————————————-

    MSI (s) (1C:34) [00:01:36:125]: Executing op: CustomActionSchedule(Action=cs_CreateService,ActionType=11265,Source=BinaryData,Target=**********,CustomActionData=**********)

    MSI (s) (1C:CC) [00:01:36:140]: Invoking remote custom action. DLL: C:WindowsInstallerMSI21F3.tmp, Entrypoint: m5

    InstallShield: Attempting to load through CLR 4 APIs…

    InstallShield: Getting meta host…

    InstallShield: Loaded CLR  successfully

    InstallShield: Ignoring CustomActionData substring "C:Program Files (x86)TEST|C:||5|True|False|True|VM134|TEST_DB_CD16|||0|||||2012/06/12 10:29:28||||Testdomainadmin|admin123|||1|1||"

    InstallShield: Deferred action requested property MsiHiddenProperties not provided by CustomActionData

    InstallShield: Loading assembly DLPInstall from resource 4097

    InstallShield: Calling method with parameters [(System.IntPtr)424, (System.String)TestManager]

    ———————————————-

    Thanks in advance for your help & suggestion.

    Manish Jain

    manish1979@gmail.com

  68. Hi Manish – The MsiHiddenProperties property is used to control whether or not to show sensitive information in the MSI log file – msdn.microsoft.com/…/aa370308.aspx.  I'd suggest taking a look at that documentation to see if that will help you in this scenario.

  69. Volkan says:

    http://sdrv.ms/134Sdm4 there is the file. please help Aaron :/

  70. Hi Volkan – Your log looks like it is from an attempt to install the .NET Framework 1.1 on Windows 7.  This is the exact error that I see in your log:

    1: ERROR: Process returned non-0 value! CMDLINE: "C:windowssystem32URTTEMPregtlib.exe" "C:windowsMicrosoft.NETFrameworkv1.1.4322mscorlib.tlb"

    I'm not sure what the root cause is for that type of error though.  It might help to try the technique described at saranspot.blogspot.com/…/installing-dotnet-framework-11-on.html.

    If that doesn't help, then I'd suggest posting a question about this issue on the .NET Framework setup forum and hopefully someone there will have some additional suggestions for you to try.  You can find this forum at social.msdn.microsoft.com/…/threads.

  71. MHMOUD says:

    Error 1935. An error occurred during the installation of assembly component {74FD3CE6-2A8D-0E9C-A01F-C8B3B9A1E18E}. HRESULT: 0x80070002. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: Microsoft.VC80.MFCLOC,type=”win32″,version=”8.0.50727.762″,publicKeyToken=”1fc8b3b9a1e18e3b”,processorArchitecture=”x86″
    === Logging stopped: 3/25/2016 23:54:36 ===

    WHAT IS THE SOLUTION ?

    1. Hi MHMOUD – 1935 errors for Win32 assemblies are caused by a problem in the Windows OS component installation infrastructure on your PC. Here are the steps that I suggest for this type of error:

      1. Install the latest Windows service pack and updates if you haven’t yet.

      2. Try to run the System Update Readiness Tool from http://support.microsoft.com/kb/947821.

      3. Try to repair the files that are a part of your OS by using the steps listed at http://blogs.msdn.com/astebner/archive/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx.

      If none of the above help, you might need to repair/re-install Windows to fix this type of error. It might also help to post a question on one of the Windows forums at http://answers.microsoft.com/en-us/windows to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.