locked
side-by-side error windows 7 x64 SP1 RRS feed

  • Question

  • So far we've ran malwarebytes to remove all the malware, ran an sfc /scannow, removed AVG, re-installed all the redistributables. At this point I am not sure what else to try. Here is the sxstrace.exe log file, if anyone can has seen this before and can point me in the right direction that would be great. It happens when opening almost anything, iTunes, word, excel, outlook, etc...He is running windows 7 pro x64 sp1

     

    =================
    Begin Activation Context Generation.
    Input Parameter:
        Flags = 0
        ProcessorArchitecture = Wow32
        CultureFallBacks = en-US;en
        ManifestPath = C:\Program Files (x86)\Microsoft Office\Office12\WINWORD.EXE
        AssemblyDirectory = C:\Program Files (x86)\Microsoft Office\Office12\
        Application Config File =
    -----------------
    INFO: Parsing Manifest File C:\Program Files (x86)\Microsoft Office\Office12\WINWORD.EXE.
        INFO: Manifest Definition Identity is winword,processorArchitecture="x86",type="win32",version="1.0.0.0".
        INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0"
    INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0".
        INFO: Resolving reference for ProcessorArchitecture WOW64.
            INFO: Resolving reference for culture Neutral.
                INFO: Applying Binding Policy.
                    INFO: No publisher policy found.
                    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.50608.0__1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.DLL.
                    INFO: Did not find manifest for culture Neutral.
                INFO: End assembly probing.
        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.5592_none_517247830f45081d.manifest
                    INFO: Publisher Policy redirected assembly version.
                    INFO: Post policy assembly identity is Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.5592".
                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.5592__1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.DLL.
                    INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Office\Office12\Microsoft.VC80.CRT.DLL.
                    INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Office\Office12\Microsoft.VC80.CRT.MANIFEST.
                    INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Office\Office12\Microsoft.VC80.CRT\Microsoft.VC80.CRT.DLL.
                    INFO: Attempt to probe manifest at C:\Program Files (x86)\Microsoft Office\Office12\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.50608.0".
    ERROR: Activation Context generation failed.
    End Activation Context Generation.



    • Edited by GlenTech83 Wednesday, September 7, 2011 1:32 AM
    Wednesday, September 7, 2011 1:18 AM

Answers

  • Hi,

     

    As the side by side issue, mostly miss a Visual C++ runtime which is needed to run the application.

     

    I recommend that you could follow the following steps to check the the problem cause:

     

    1.       Run the Command prompt (CMD) with as administrator  and run this command:

    SxsTrace Trace -logfile:SxsTrace.etl

     

    2.       Run one of the programs which causes the Side By Side error.

     

    3.       Run the following command in Command prompt:

     

    sxstrace Parse -logfile:SxSTrace.etl -outfile:SxSTrace.txt

     

    More SxSTrace.txt

     

    4.       Check which VC++ runtime is missing.

     

    If you are unsure, please upload the complete SxSTrace.txt to your SkyDrive and post a link here.

     

    Please refer http://blogs.msdn.com/b/junfeng/archive/2006/04/14/576314.aspx


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Robinson Zhang Friday, September 23, 2011 9:42 AM
    Friday, September 9, 2011 6:30 AM
  • Actually installing .net updates from windows update did the trick. Thanks for the reply though
    • Marked as answer by GlenTech83 Friday, September 23, 2011 2:28 PM
    Friday, September 23, 2011 2:28 PM

All replies

  • Hi,

     

    As the side by side issue, mostly miss a Visual C++ runtime which is needed to run the application.

     

    I recommend that you could follow the following steps to check the the problem cause:

     

    1.       Run the Command prompt (CMD) with as administrator  and run this command:

    SxsTrace Trace -logfile:SxsTrace.etl

     

    2.       Run one of the programs which causes the Side By Side error.

     

    3.       Run the following command in Command prompt:

     

    sxstrace Parse -logfile:SxSTrace.etl -outfile:SxSTrace.txt

     

    More SxSTrace.txt

     

    4.       Check which VC++ runtime is missing.

     

    If you are unsure, please upload the complete SxSTrace.txt to your SkyDrive and post a link here.

     

    Please refer http://blogs.msdn.com/b/junfeng/archive/2006/04/14/576314.aspx


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Robinson Zhang Friday, September 23, 2011 9:42 AM
    Friday, September 9, 2011 6:30 AM
  • Actually installing .net updates from windows update did the trick. Thanks for the reply though
    • Marked as answer by GlenTech83 Friday, September 23, 2011 2:28 PM
    Friday, September 23, 2011 2:28 PM