Aaron Stebner's WebLog

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

Help me help you if you have setup bugs

Help me help you if you have setup bugs

Rate This
  • Comments 74

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>

 

  • hi

    realy thx for your time

    i upload some fils

    www.twisterflasher.net/neterrors.rar

  • 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:\Programme\Reference Assemblies\Microsoft\Framework\v3.0\System.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!

  • 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

  • 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?

  • 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

  • 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?

  • 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.

  • 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

  • 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.

  • 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.

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

  • 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.

  • 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

  • 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?

  • 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

  • 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:\Windows\winsxs\amd64_microsoft-windows-

    servicingstack_31bf3856ad364e35_6.0.6002.18005_none_676975d87cc9b6e6\cbscore.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:\Windows\WinSxS\InstallTemp\20100106094707699.0\x86_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:

    \Windows\system32\msiexec.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:\Windows\WinSxS\InstallTemp\20100106094710140.0\8.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:\Windows\system32\msiexec.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:\longhorn\base\wcp\componentstore\csd_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:\longhorn\base\wcp\componentstore\csd_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

    ------------------------------

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