locked
Deploying WPF app - runtime error R6034 RRS feed

  • Question

  • I have recently developed a WPF application in VS2008 SP1.  The app runs fine on any of the development machines (Vista, VS2008, .NET Framework 3.5 SP1), but crashes with the R6034 runtime error on the client's machine as well as the three test machines (with clean installs of Vista also with .NET Framework 3.5 SP1).

    I have tried reinstalling .NET Framework 3.5 SP1 to no avail.  I've read several forum entries and other blogs speaking of embedding the manifest, but since I'm using C# and VS2008 that's already being done, I believe.

    Any help at this point would be greatly appreciated.

    Robert

    Here is the output of the sxstrace on the test machines:

    =================
    Begin Activation Context Generation.
    Input Parameter:
     Flags = 0
     ProcessorArchitecture = x86
     CultureFallBacks = en-US;en
     ManifestPath = C:\Windows\assembly\GAC_32\PresentationCore\3.0.0.0__31bf3856ad364e35\PresentationCore.dll
     AssemblyDirectory = C:\Windows\assembly\GAC_32\PresentationCore\3.0.0.0__31bf3856ad364e35\
     Application Config File =
    -----------------
    INFO: Parsing Manifest File C:\Windows\assembly\GAC_32\PresentationCore\3.0.0.0__31bf3856ad364e35\PresentationCore.dll.
     INFO: Manifest Definition Identity is PresentationCore,processorArchitecture="X86",type="win32",version="1.0.0.0".
     INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.1830"
    INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.1830".
     INFO: Resolving reference for ProcessorArchitecture x86.
      INFO: Resolving reference for culture Neutral.
       INFO: Applying Binding Policy.
        INFO: Find publisher policy at C:\Windows\WinSxS\manifests\x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.1434_none_516c10c30f4aae68.manifest
        INFO: No binding policy redirect found.
       INFO: Begin assembly probing.
        INFO: Did not find the assembly in WinSxS.
        INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC80.CRT\8.0.50727.1830__1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.DLL.
        INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\PresentationCore\3.0.0.0__31bf3856ad364e35\Microsoft.VC80.CRT.DLL.
        INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\PresentationCore\3.0.0.0__31bf3856ad364e35\Microsoft.VC80.CRT.MANIFEST.
        INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\PresentationCore\3.0.0.0__31bf3856ad364e35\Microsoft.VC80.CRT\Microsoft.VC80.CRT.DLL.
        INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\PresentationCore\3.0.0.0__31bf3856ad364e35\Microsoft.VC80.CRT\Microsoft.VC80.CRT.MANIFEST.
        INFO: Did not find manifest for culture Neutral.
       INFO: End assembly probing.
     ERROR: Cannot resolve reference Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.1830".
    ERROR: Activation Context generation failed.
    End Activation Context Generation.

    Update: I have also tried deploying a blank WPF application (no additional XAML or code-behind) onto the test laptops. I still get the R6034 runtime error.

    • Edited by Robert957 Monday, February 22, 2010 8:33 PM Moved sxstrace output into post
    Monday, February 22, 2010 1:59 PM

Answers

  • - Ran the verification tool
    - Found one key (HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727\SP) was set at 1 and was looking for 2.  Fixed that.
    - An error still occurs when installing VS 2008 on the machine (R6034 runtime error).  I will collect and post the logs to Microsoft Connect.


    Robert, thanks very much for your followup and the system info. 

    "Found one key (HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727\SP) was set at 1 and was looking for 2.  Fixed that." -> That is where the problem resides. For some reason your Vista SP1 test machines do not have the .NET 2.0 SP2 patch that the 3.5 SP1 installer is supposed to apply.

    If you look in Control Panel > Programs > Programs and Features > Installed Updates on a 3.5 SP1 Vista system, there are two updates that should always be there: "Update for Microsoft Windows (KB948609)" (2.0 SP2) and "Update for Microsoft Windows (KB948610)" (3.0 SP2). When trying a reinstall, make sure these patches are uninstalled from the system before the reinstall. After the framework is installed, these patches should appear again under Installed Updates, the SP keys under "NET Framework Setup" should be correctly set, and the SxS problem should (I hope) be repaired. If anything goes wrong, do post the install logs.
    • Marked as answer by Robert957 Thursday, March 4, 2010 7:52 PM
    Wednesday, March 3, 2010 6:58 PM
  • "Found one key (HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727\SP) was set at 1 and was looking for 2.  Fixed that." -> That is where the problem resides. For some reason your Vista SP1 test machines do not have the .NET 2.0 SP2 patch that the 3.5 SP1 installer is supposed to apply.
    Thank you, Greg,

    I checked all of the test machines and none of them had the KB946809 patch installed.  Neither repairing nor reinstalling .NET Framework 3.5 SP1 would install the patch (I checked the install logs for any reference to 946809 and found none).  Manually installing the KB946809 update as in the first response found here (http://social.msdn.microsoft.com/Forums/en/netfxsetup/thread/2e053b62-8583-4c94-a570-5a06d6964d70) I was able to get the WPF app to work properly.

    Robert
    • Marked as answer by Robert957 Thursday, March 4, 2010 7:52 PM
    Thursday, March 4, 2010 7:51 PM

All replies

  • INFO: Parsing Manifest File C:\Windows\assembly\GAC_32\PresentationCore\3.0.0.0__31bf3856ad364e35\PresentationCore.dll.
     INFO: Manifest Definition Identity is PresentationCore,processorArchitecture="X86",type="win32",version="1.0.0.0".
     INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.1830"

    Where can I download the Microsoft.VC80.CRT.manifest version 8.0.50727.1830 and corresponding dll files (3 of them)?

    Robert

    Wednesday, February 24, 2010 1:28 AM
  • It was suggested that the version 8.0.50727.1830 should be included in the VC++ 2005 redist. 

    I have completely removed the VC++ 2005 redist and VC++ 2005 SP1 redist.  Reinstalled them.  And still get R6034 runtime error.  The problem according to sxstrace that I'm still getting is the PresentaionCore.dll is referencing Microsoft.VC80.CRT version 8.0.50727.1830.  I have checked 5 different machines running either XP SP3 or Vista SP2 and all of them have version 762, 1434, 3053, and 4016.  There is no version 1830.

    I have on the Net the 762 manifest and 3 accompanying dlls and put them with the executable.  That didn't work, obviously it was still looking for version 1830 not 762.  So I "renamed" the 762 version number in the manifest file to 1830, but still it didn't work.

    Any other ideas?
    Wednesday, February 24, 2010 3:35 PM
  • Hi Robert,

        Do you perhaps have any hotfixes installed that may have patched PresentationCore?  You may want to check this and clean any files left behind when re-installing 3.5 Sp1, as mismatched versions occasionally lead to un-modified files.

    For 3.5 Sp1 "gold", you should end up with both PresentationCore.dll and msvcr80.dll that have version *.3053.  The .1830 I believe corresponded with 3.5 RTM.  This implies to me you may have a mix between 3.5 SP1 and RTM WPF binaries on the machine, which can definitely cause issues.  Without actually seeing the machine I don't have many more ideas...

    -Matt


    SDET : Deployment/Hosting
    Wednesday, February 24, 2010 6:13 PM
  • Do you perhaps have any hotfixes installed that may have patched PresentationCore?  You may want to check this and clean any files left behind when re-installing 3.5 Sp1, as mismatched versions occasionally lead to un-modified files.


    Thanks, Matt, for replying.

    I have two hotfixes for .NET Framework 3.5 SP1 installed: KB953595 and KB958484.

    A complete uninstall of the hotfixes and .NET Framework 3.5 SP1 and clean reinstall of .NET Framework 3.5 SP1 did not work.

    I'm next tried to install VS 2008 to see if that works, since the development machines run with WPF app just fine.  However, during the install I received two R6034 errors identical to this post: http://social.msdn.microsoft.com/Forums/en/vssetup/thread/46804ece-703e-4427-88d7-d483e363da9a

    Any other comments/suggestions would be great!

    Update:  Recompile of app using VS 2008 (not SP1) on test delivery was successful; but launch that program (as well as trying to view in XAML in Design mode) resulted in R6034.  Will try updating to VS 2008 SP1 next.

    Update 2: VS 2008 SP1 didn't resolved the issue either.
    • Edited by Robert957 Wednesday, February 24, 2010 8:40 PM Update 2
    Wednesday, February 24, 2010 6:57 PM
  • Robert,

    Have you run the Verification Tool ( http://blogs.msdn.com/astebner/pages/8999004.aspx ) on the failing systems, as seen in the vssetup forum thread?

    Also, what Vista Service Pack is on these failing systems?

    Checklist:

    - Enable "Microsoft .NET Framework 3.0" feature.
    - Run the Verification Tool and inspect the log files.
    - If errors are in log, run the repair steps ( http://blogs.msdn.com/astebner/archive/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx ) and reverify.
    - If no errors are in log and you still see the runtime error, collect the log and post the link to it ( http://blogs.msdn.com/heaths/archive/2008/05/09/visual-studio-and-net-log-collection-utility.aspx ).

    Greg
    Tuesday, March 2, 2010 2:18 AM
  • Also, what Vista Service Pack is on these failing systems?
    All of the machines are running Vista Enterprise SP1.

    Checklist:

    - Enable "Microsoft .NET Framework 3.0" feature.
    - Run the Verification Tool and inspect the log files.
    - If errors are in log, run the repair steps ( http://blogs.msdn.com/astebner/archive/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx ) and reverify.
    - If no errors are in log and you still see the runtime error, collect the log and post the link to it ( http://blogs.msdn.com/heaths/archive/2008/05/09/visual-studio-and-net-log-collection-utility.aspx ).


    - Enabled the Microsoft .NET Framework 3.0 feature from the "Programs and Features" category in Control Panel.  Only the XPS viewer was original enabled, so I also checked "WCF HTTP Activation" and "WCF Non-HTTP Activation".
    - Ran the verification tool
    - Found one key (HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727\SP) was set at 1 and was looking for 2.  Fixed that.
    - An error still occurs when installing VS 2008 on the machine (R6034 runtime error).  I will collect and post the logs to Microsoft Connect.


    Installing VS2008 on the machine was just an attempt by me to see if it installed any files that would solve my original problem.  The development machines (also Vista Enterprise SP1) have VS 2008 installed.  The WPF app works fine on ALL development machines.  It just the test machines that can't run the app (R6034 runtime error) nor install VS 2008 (also R6034 runtime error).  VS 2008 runs it just will not show any XAML in design view (R6034).  Running sxstrace still reviews that the Microsoft.VC80.CRT is still looking for the incorrect version.

    Hopefully posting the install logs will shed more light.

    Robert
    • Edited by Robert957 Tuesday, March 2, 2010 2:13 PM Added info about VS2008 install
    Tuesday, March 2, 2010 2:04 PM
  • - Ran the verification tool
    - Found one key (HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727\SP) was set at 1 and was looking for 2.  Fixed that.
    - An error still occurs when installing VS 2008 on the machine (R6034 runtime error).  I will collect and post the logs to Microsoft Connect.


    Robert, thanks very much for your followup and the system info. 

    "Found one key (HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727\SP) was set at 1 and was looking for 2.  Fixed that." -> That is where the problem resides. For some reason your Vista SP1 test machines do not have the .NET 2.0 SP2 patch that the 3.5 SP1 installer is supposed to apply.

    If you look in Control Panel > Programs > Programs and Features > Installed Updates on a 3.5 SP1 Vista system, there are two updates that should always be there: "Update for Microsoft Windows (KB948609)" (2.0 SP2) and "Update for Microsoft Windows (KB948610)" (3.0 SP2). When trying a reinstall, make sure these patches are uninstalled from the system before the reinstall. After the framework is installed, these patches should appear again under Installed Updates, the SP keys under "NET Framework Setup" should be correctly set, and the SxS problem should (I hope) be repaired. If anything goes wrong, do post the install logs.
    • Marked as answer by Robert957 Thursday, March 4, 2010 7:52 PM
    Wednesday, March 3, 2010 6:58 PM
  • "Found one key (HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727\SP) was set at 1 and was looking for 2.  Fixed that." -> That is where the problem resides. For some reason your Vista SP1 test machines do not have the .NET 2.0 SP2 patch that the 3.5 SP1 installer is supposed to apply.
    Thank you, Greg,

    I checked all of the test machines and none of them had the KB946809 patch installed.  Neither repairing nor reinstalling .NET Framework 3.5 SP1 would install the patch (I checked the install logs for any reference to 946809 and found none).  Manually installing the KB946809 update as in the first response found here (http://social.msdn.microsoft.com/Forums/en/netfxsetup/thread/2e053b62-8583-4c94-a570-5a06d6964d70) I was able to get the WPF app to work properly.

    Robert
    • Marked as answer by Robert957 Thursday, March 4, 2010 7:52 PM
    Thursday, March 4, 2010 7:51 PM
  • I am in the same circle of ____ that this poster was.  I have been working on this with Microsoft reps as well, and as yet we have been unable to fix it.

    The two KB bits that you describe are NOT shown as installed updates on this Vista Enterprise system.

    The trouble began when I installed VS2010 RC.  So when you ask if anything was installed that may have "patched PresentationCore.dll" I would like to respond: "You tell me?  Did you guys patch presentation core in VS2010 RC?"  And how can I get presentationCore set back to wanting the MSVCR80.DLL that I *have*?

    Thanks

    Randy

    Friday, June 25, 2010 12:03 AM