64-bit W7 install/side-by-side configuration is incorrect

I have installed CS4 Extended and Lightroom 2 with W7 64-bit.  CS4 64-bit does not function and gives the error "side-by-side configuration is incorrect."  CS4 with what appears to be 32 bit works, and Lightroom 2 64 bit works (though does not connect to CS4, I assume because the 64-bit application fails). I tried rebooting the PC and re-launching the application as suggested in the knowledge base for similar problems with Vista.   Suggestions? Would it make sense to uninstall and re-install all of CS4? Or??

Try installing C++ 2008.
Here are the links for 64 bit:
http://www.microsoft.com/downloads/details.aspx?familyid=BD2A6171-E2D6-4230-B809-9A8D7548C 1B6&displaylang=en
Here is the link for C++ service pack 1
http://www.microsoft.com/downloads/details.aspx?familyid=BA9257CA-337F-4B40-8C14-157CFDFFE E4E&displaylang=en
I installed Windows 7 and I am pretty sure I had to install this seperate. Either way it won't hurt.

Similar Messages

  • "Side-by-side configuration is incorrect" when trying to install MS DirSync tool

    Apologies if this is the wrong thread, but it seems like every thread is the wrong thread for this one :)  Yes, I've checked all the other "side-by-side configuration" threads, but none of them seems to apply to this case.
    I have a SBS 2012 machine, acting as DC, AD DS and DNS, and our organization has recently signed up for Office 365 Online E1, and we've migrated our mail there.  Everything is set up, but now I'd like to sync our AD with MS Online.  I enabled directory
    sync in the admin user and group controls on the Office 365 site and as per instructions, I downloaded the latest version of DirSync from here:http://social.technet.microsoft.com/wiki/contents/articles/18429.microsoft-azure-active-directory-sync-tool-version-release-history.aspx.
    However, when I try to install it on the server, I get this error message:  "The application has failed to start because its side-by-side configuration is incorrect. Please run sxtrace or see the application event log for more detail."
    Sxtrace gives the following results:
    =================
    Begin Activation Context Generation.
    Input Parameter:
    Flags = 0
    ProcessorArchitecture = AMD64
    CultureFallBacks = en-US;en
    ManifestPath = N:\temp\dirsync.exe
    AssemblyDirectory = N:\temp\
    Application Config File = 
    INFO: Parsing Manifest File N:\temp\dirsync.exe.
    INFO: Manifest Definition Identity is (null).
    ERROR: Line 0: XML Syntax error.
    ERROR: Activation Context generation failed.
    End Activation Context Generation.
    Things I've tried:
    Other posts seem to indicate that it's often an issue with missing visual C++ libraries, but I installed both the 2008 and 2010 C redistributables for x86 and x64, and nothing has changed.  
    One solution for a similar message had a typographical error in an xml configuration file, however in this case the "Application config file" field is blank.  
    As several other (non TN threads) around the 'net recommend, I ran SFC.  It appears to work for others with the same error message.  It fixed some issues and spit out a huge log file, but the problem persists, and I don't know where in the log
    file to look, assuming anything in there is relevant (the file is over 700kb, so I'm not going to start spamming big chunks of it just yet unless I know what to look for).
    The problem seems to come up in the context of software development (another thread on this subject is about the user developing an application from scratch) but I have no background in software dev, and this is supposed to be an official tool from Microsoft,
    for crying out loud, not some homebrew thing I'm putting together.  
    This one issue is keeping us from moving ahead with our entire plan for user access, so any help would be
    much appreciated. Thanks!!!

    Hi AGrush,
    Based on your description, did you mean that attempt to install Microsoft Azure Active Directory Sync tool
    on Windows Server 2012 Essentials?
    The Azure Active Directory Sync tool should be installed on a computer which isn't a domain controller. For
    more details, please refer to the System requirements in the following KB.
    How to troubleshoot Azure Active Directory Sync tool installation
    and Configuration Wizard error messages
    In addition, I’m a little confused that why install DirSync (That is what the Windows Server Essentials Office
    365 integration is for) on Windows Server 2012 Eseentails.
    Manage Office 365 in Windows Server Essentials
    If anything I misunderstand or any update, please don’t hesitate to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • When I try to install Itunes64setup software in a w vista 64 notebook I get an error message "The application has failed to start because its side-by-side configuration is incorrect." Can you help me ?

    When I try to install Itunes64setup software in a w vista 64 notebook I get an error message "The application has failed to start because its side-by-side configuration is incorrect." Can you help me ?

    This forum is for questions from those managing sites on iTunes U, Apple's service for colleges and universities to post educational material in the iTunes Store. You'll be most likely to get help with this issue if you ask in the general iTunes for Windows forum.
    Regards.

  • This application failed to start because it's side-by-side configuration is incorrect....

    This is a redirected question from
    here
    While trying to run YouCam.exe, i encountered the error message,
    "The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. "
    I then searched the forums and installed a slew of updates that mostly VC++ Redistritutable 64-Bit version, DotNetFix etc etc but it still did not work.
    I then ran 'Event Viewer' and pulled out the error logs for the YouCam program.
    "Activation context generation failed for "C:\Program Files\CyberLink\YouCam\YouCam.exe.Manifest". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0" could not be found.
    Please use sxstrace.exe for detailed diagnosis."
    I am using a Fujitsu SH760 laptop which is running a Win7 64-bit Enterprise OS.
    Note that I do not have the recovery disk.
    Please assist and if you require further information, i will try to give it asap.
     Thank You.

    I ran sxstrace.exe and here is the log file i obtained. Details as follows,
    =================
    Begin Activation Context Generation.
    Input Parameter:
        Flags = 0
        ProcessorArchitecture = Wow32
        CultureFallBacks = en-US;en
        ManifestPath = C:\Program Files (x86)\CyberLink\YouCam\YouCam.exe.Manifest
        AssemblyDirectory = C:\Program Files (x86)\CyberLink\YouCam\
        Application Config File =
    INFO: Parsing Manifest File C:\Program Files (x86)\CyberLink\YouCam\YouCam.exe.Manifest.
        INFO: Manifest Definition Identity is YouCam,processorArchitecture="X86",type="win32",version="3.0.1104.3278".
        INFO: Reference: Kanten.X,type="win32",version="1.0.0.0"
        INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0"
        INFO: Reference: Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0"
    INFO: Resolving reference Kanten.X,type="win32",version="1.0.0.0".
        INFO: Resolving reference for ProcessorArchitecture Kanten.X,type="win32",version="1.0.0.0".
            INFO: Resolving reference for culture Neutral.
                INFO: Applying Binding Policy.
                    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:\Program Files (x86)\CyberLink\YouCam\Kanten.X.DLL.
                    INFO: Attempt to probe manifest at C:\Program Files (x86)\CyberLink\YouCam\Kanten.X.MANIFEST.
                    INFO: Manifest found at C:\Program Files (x86)\CyberLink\YouCam\Kanten.X.MANIFEST.
                INFO: End assembly probing.
    INFO: Resolving reference Kanten.X.mui,language="*",type="win32",version="1.0.0.0".
        INFO: Resolving reference for ProcessorArchitecture Kanten.X.mui,language="*",type="win32",version="1.0.0.0".
            INFO: Resolving reference for culture en-US.
                INFO: Applying Binding Policy.
                    INFO: No binding policy redirect found.
                INFO: Begin assembly probing.
                    INFO: Did not find the assembly in WinSxS.
                    INFO: Did not find manifest for culture en-US.
                INFO: End assembly probing.
            INFO: Resolving reference for culture en.
                INFO: Applying Binding Policy.
                    INFO: No binding policy redirect found.
                INFO: Begin assembly probing.
                    INFO: Did not find the assembly in WinSxS.
                    INFO: Did not find manifest for culture en.
                INFO: End assembly probing.
    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.4940_none_516d712b0f495a45.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.4940".
                INFO: Begin assembly probing.
                    INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc.manifest.
                    INFO: Manifest found at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc.manifest.
                INFO: End assembly probing.
    INFO: Resolving reference Microsoft.VC80.CRT.mui,language="*",processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4940".
        INFO: Resolving reference for ProcessorArchitecture WOW64.
            INFO: Resolving reference for culture en-US.
                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.mui\8.0.50727.4940_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
                    INFO: Did not find manifest for culture en-US.
                INFO: End assembly probing.
            INFO: Resolving reference for culture en.
                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.mui\8.0.50727.4940_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
                    INFO: Did not find manifest for culture en.
                INFO: End assembly probing.
        INFO: Resolving reference for ProcessorArchitecture x86.
            INFO: Resolving reference for culture en-US.
                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.mui\8.0.50727.4940_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
                    INFO: Did not find manifest for culture en-US.
                INFO: End assembly probing.
            INFO: Resolving reference for culture en.
                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.mui\8.0.50727.4940_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
                    INFO: Did not find manifest for culture en.
                INFO: End assembly probing.
    INFO: Resolving reference Microsoft.VC80.MFC,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.MFC\8.0.50608.0__1fc8b3b9a1e18e3b\Microsoft.VC80.MFC.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: 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.MFC\8.0.50608.0__1fc8b3b9a1e18e3b\Microsoft.VC80.MFC.DLL.
                    INFO: Attempt to probe manifest at C:\Program Files (x86)\CyberLink\YouCam\Microsoft.VC80.MFC.DLL.
                    INFO: Attempt to probe manifest at C:\Program Files (x86)\CyberLink\YouCam\Microsoft.VC80.MFC.MANIFEST.
                    INFO: Attempt to probe manifest at C:\Program Files (x86)\CyberLink\YouCam\Microsoft.VC80.MFC\Microsoft.VC80.MFC.DLL.
                    INFO: Attempt to probe manifest at C:\Program Files (x86)\CyberLink\YouCam\Microsoft.VC80.MFC\Microsoft.VC80.MFC.MANIFEST.
                    INFO: Did not find manifest for culture Neutral.
                INFO: End assembly probing.
        ERROR: Cannot resolve reference Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50608.0".
    ERROR: Activation Context generation failed.
    End Activation Context Generation.

  • "failed to start... side-by-side configuration is incorrect'

    Running Vista Ultimate 32-bit. When I try to start DW CS4 or
    Fireworks CS4 I get the following message:
    "The application has failed to start because its side-by-side
    configuration is incorrect. Please see the application event log
    for more detail."
    Checking the event log, the entry shows this:
    "Activation context generation failed for "E:\Adobe\Adobe
    Dreamweaver CS4\Dreamweaver.exe". Dependent Assembly
    Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="wi n32",version="8.0.50727.762"
    could not be found. Please use sxstrace.exe for detailed
    diagnosis."
    I found a couple of KB articles, one of which suggested
    installing the VC++2005 runtime, which I did, and the other the
    VC++2008 runtime, which I also did. No joy.
    Oddly enough, all of the non-Web-related apps in Design
    Premium that I've tested are working. I can launch PS, AI, ID,
    Bridge, Acrobat Pro, etc. But DW, Fireworks, and Flash Pro won't
    launch.
    I've Googled this, to no avail. When I try to run a forum
    search on the topic I get a server error asking me to contact the
    site admin. Right.
    Anybody got any ideas?
    cheers,
    scott

    Thanx man, you are the best!
    I mistakenly found an easier solution to this problem.
    I had exactly the same problem with DW. I actually solved
    this issue by mistake, but without reading your post I would'nt
    have known it's possible!
    Here's what happened:
    With no connection to this issue I downloaded and installed
    Windows Live Messenger, and in the installation info I see it
    includes the VS installation! Since you said re-installing VS
    solved your problem, I uninstalled DW and then allowed the
    Messenger installation to continue - and in the next time I
    installed DW it works perfectly!
    So I guess you don't need to uninstall the VS, only install a
    new version of it.
    Tanx again!

  • What happened? After this morning Firefox's update, I couldn't get into Firefox but got this message, "The application failed to start because it's side-by-side configuration is incorrect.

    This morning I went to go into Firefox, a message came up stating it was updating. After the update, Firefox didn't open, so I clicked on the icon and got this message. C:\Program Files (x86) Mozilla Fire\firefox.exe. The application has failed to start because its side-by-side configuration is incorrect. I tried removing & re-installing and I even try the Window's restoration point of a couple days back and I still get the message. Has anyone had or have this problem?

    You can click the link in my above post if you haven't done that yet.
    *https://support.mozilla.org/questions/910134
    That SxS error seems to be caused by a corrupted Visual C installation that requires some DLL files to be reinstalled.
    *http://www.vistax64.com/software/245768-side-side-configuration-incorrect.html

  • Cannot run Photoshop CS5.1 setup; "side-by-side configuration is incorrect"

    When I try to install Photoshop CS5.1 Extended, I get an error message that reads "The application has failed to start because it's side-by-side configuration is incorrect. Please see the application event log for more detail."
    Is there a way to fix this (and if so, what is it), or should I just try to get a new copy?

    I received this message when invoking the installer.
    I actually tried just reinstalling Microsoft Visual C++ 2005, like right after i made this ticket and that worked. so, problem solved

  • Side-by-side configuration is incorrect? Urgent Help

    I downloaded a game and I get a very high ping, the game I downloaded offers a program to download that tries to help lower your ping. I installed the program but I get this error "The Application has failed to start because its side-by-side configuration
    is inocrrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail."
    I have done some looking around and found that I needed to do a sxstrace and I did but I do not know how to find my problem, if someone could please tell me how to fix my program from doing this that would be great. This is the text gathered from the sxstrace:
    =================
    Begin Activation Context Generation.
    Input Parameter:
    Flags = 0
    ProcessorArchitecture = Wow32
    CultureFallBacks = en-US;en
    ManifestPath = C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\QQAcc.exe
    AssemblyDirectory = C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\
    Application Config File = 
    INFO: Parsing Manifest File C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\QQAcc.exe.
    INFO: Manifest Definition Identity is Tencent.QQ,processorArchitecture="X86",type="win32",version="1.0.0.0".
    INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053"
    INFO: Reference: Microsoft.VC80.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053"
    INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="X86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
    INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053".
    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.50727.4053__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.4940_none_516d712b0f495a45.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.4940".
    INFO: Begin assembly probing.
    INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc.manifest.
    INFO: Manifest found at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc.manifest.
    INFO: End assembly probing.
    INFO: Resolving reference Microsoft.VC80.CRT.mui,language="*",processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4940".
    INFO: Resolving reference for ProcessorArchitecture WOW64.
    INFO: Resolving reference for culture en-US.
    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.mui\8.0.50727.4940_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en-US.
    INFO: End assembly probing.
    INFO: Resolving reference for culture en.
    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.mui\8.0.50727.4940_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en.
    INFO: End assembly probing.
    INFO: Resolving reference for ProcessorArchitecture x86.
    INFO: Resolving reference for culture en-US.
    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.mui\8.0.50727.4940_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en-US.
    INFO: End assembly probing.
    INFO: Resolving reference for culture en.
    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.mui\8.0.50727.4940_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en.
    INFO: End assembly probing.
    INFO: Resolving reference Microsoft.VC80.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053".
    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.ATL\8.0.50727.4053__1fc8b3b9a1e18e3b\Microsoft.VC80.ATL.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: 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.ATL\8.0.50727.4053__1fc8b3b9a1e18e3b\Microsoft.VC80.ATL.DLL.
    INFO: Attempt to probe manifest at C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\Microsoft.VC80.ATL.DLL.
    INFO: Attempt to probe manifest at C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\Microsoft.VC80.ATL.MANIFEST.
    INFO: Attempt to probe manifest at C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\Microsoft.VC80.ATL\Microsoft.VC80.ATL.DLL.
    INFO: Attempt to probe manifest at C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\Microsoft.VC80.ATL\Microsoft.VC80.ATL.MANIFEST.
    INFO: Did not find manifest for culture Neutral.
    INFO: End assembly probing.
    ERROR: Cannot resolve reference Microsoft.VC80.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053".
    ERROR: Activation Context generation failed.
    End Activation Context Generation.
    =================
    Begin Activation Context Generation.
    Input Parameter:
    Flags = 0
    ProcessorArchitecture = Wow32
    CultureFallBacks = en-US;en
    ManifestPath = C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\QQAcc.exe
    AssemblyDirectory = C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\
    Application Config File = 
    INFO: Parsing Manifest File C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\QQAcc.exe.
    INFO: Manifest Definition Identity is Tencent.QQ,processorArchitecture="X86",type="win32",version="1.0.0.0".
    INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053"
    INFO: Reference: Microsoft.VC80.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053"
    INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="X86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
    INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053".
    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.50727.4053__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.4940_none_516d712b0f495a45.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.4940".
    INFO: Begin assembly probing.
    INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc.manifest.
    INFO: Manifest found at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc.manifest.
    INFO: End assembly probing.
    INFO: Resolving reference Microsoft.VC80.CRT.mui,language="*",processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4940".
    INFO: Resolving reference for ProcessorArchitecture WOW64.
    INFO: Resolving reference for culture en-US.
    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.mui\8.0.50727.4940_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en-US.
    INFO: End assembly probing.
    INFO: Resolving reference for culture en.
    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.mui\8.0.50727.4940_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en.
    INFO: End assembly probing.
    INFO: Resolving reference for ProcessorArchitecture x86.
    INFO: Resolving reference for culture en-US.
    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.mui\8.0.50727.4940_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en-US.
    INFO: End assembly probing.
    INFO: Resolving reference for culture en.
    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.mui\8.0.50727.4940_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en.
    INFO: End assembly probing.
    INFO: Resolving reference Microsoft.VC80.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053".
    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.ATL\8.0.50727.4053__1fc8b3b9a1e18e3b\Microsoft.VC80.ATL.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: 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.ATL\8.0.50727.4053__1fc8b3b9a1e18e3b\Microsoft.VC80.ATL.DLL.
    INFO: Attempt to probe manifest at C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\Microsoft.VC80.ATL.DLL.
    INFO: Attempt to probe manifest at C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\Microsoft.VC80.ATL.MANIFEST.
    INFO: Attempt to probe manifest at C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\Microsoft.VC80.ATL\Microsoft.VC80.ATL.DLL.
    INFO: Attempt to probe manifest at C:\Program Files (x86)\Tencent\TXAcc\AccPlatform\Microsoft.VC80.ATL\Microsoft.VC80.ATL.MANIFEST.
    INFO: Did not find manifest for culture Neutral.
    INFO: End assembly probing.
    ERROR: Cannot resolve reference Microsoft.VC80.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053".
    ERROR: Activation Context generation failed.
    End Activation Context Generation.

    Hi,
    Check this knowledge basic article to see if it helps:
    Prevent "The application has failed to start because its side-by-side configuration is incorrect..." error starting Access
    http://support.microsoft.com/kb/2525435
    Karen Hu
    TechNet Community Support

  • Error message: "application cannot be opened as side by side configuration is incorrect"

    When trying to open a number of programmes including Microsoft Works Word processor is "application cannot be opened as side by side configuration is incorrect"
    How do I tackle this please!

    Hi
    To be honest I never meet such problem with the operating system but firstly I would recommend trying to repair the OS.
    Boot up the notebook and press F8. Then choose option called Repair the Computer.
    Now you will see a some options. Here I would recommend choosing the first option called: Startup Repair.
    This option automatically fixes problems that are preventing Windows from starting.
    But Im not quite sure if this is good enough to fix your issue with the system.
    If this does not help I would recommend reinstalling this Microsoft Works package.

  • The application has failed to start because it's side-by-side configuration is incorrect. Please see

    When opening preimere pro cs5.5 i get this:
    the application has failed to start because it's side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail

    Moving this discussion to the Premiere Pro CS5 & CS5.5 forum.

  • OBIEE 10g Installation error "The application has failed to start because its side-by-side configuration is incorrect"

    Hi,
    I did installation of OBIEE10g on windows server 2008r2 which is placed on VM ware, Installation completed successfully. but while starting the BI services or opening the administration tool it is showing error as below
    "The application has failed to start because its side-by-side configuration is incorrect.Please see application event log or use the command line sxtrace.exe tool for more detail."
    Please guide me any suggestions.
    Thanks in advance
    Regards,
    Satya

    check these Error: The application has failed to start because the side by - Microsoft Community https://forums.oracle.com/message/10578756
    https://forums.oracle.com/thread/958782
    Resolving Side-by-Side Configuration Issues - OJ's perspective

  • CS6 says "The application has failed to start because its side-by-side configuration is incorrect..."?

    CS6 won't open--whenever I try to open a CS6 application, a windows pops up and says "The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail." This occurs for every single CS6 program (PS, Flash, etc.) except Illustrator. Illustrator is the only one that will open.
    I have Windows 8. I've had CS6 for about half a year and this is the first time this has happened.

    Did you ever find resolution?

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

    I am getting an error when I launch Premier Pro that says, "The application has failed to start because side by side configuration is incorrect." I have the Production Premium Suite and all the programs are running fine except for Premier Pro
    Message was edited by: Kevin Monahan
    Reason: Title was too long

    Hi Kevin,
    Thanks for the reply. I tried that yesterday, it din't work and actually caused the same error for my other Adobe software (eg Flash, Illustrator, etc.) I had to do a system restore to get things back working. All my other programs are fine except for Premier Pro.
    I updated my all my MS Visual C++, still same problem. I also tried this - How To Fix Side-By-Side Configuration Error Step By Step (Windows 7) - YouTube
    Still getting the same error Premier Pro.

  • I go to start the "Apple Mobile Device" and it says the side-by-side configuration is incorrect. (Error 14001)  How do I fix this?

    I go to start the "Apple Mobile Device" and it says the side-by-side configuration is incorrect. (Error 14001)  How do I fix this?

    Delete them and then download them from the desired Apple ID. This may require repurchasing paid applications.
    (95675)

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

    Bootcamp 4.01 Windows Support setup.exe error message after first boot when you need to add the drivers for Windows7 to use the Mac-Mini.

    Did you ever find resolution?

Maybe you are looking for

  • Problems with local DNS after 10.6.8

    Have a Snow Leopard server that's been running quite well. After (I think) the 10.6.8 update, I've encountered a really weird error regarding dns - the internal DNS doesn't recognize the top level DNS domain (companyname.net), so internally we can't

  • Subscriptions in a blog page

    Can anyone provide me with information on how the subscription part of the blog page works. does it email them subscriber about the update? is it possible to capture the information from the subscriber for future marketing?

  • Outlook integration problem

    hello,      I had configured the outlook properly , but  it does not able to send the main in my configred mail id & within the outlook.          some times it is work properlly after new installation of outlook addon  but when  i am change  the user

  • AIR 3.4 - Android - netstream freezes between 110 and 240 seconds

    Hi, On Android, netstream freezes between 110 and 240 seconds with videos in http://xxx/..../video.mp4 format. For more details, see bug: https://bugbase.adobe.com/index.cfm?event=bug&id=3323362 Each video freezes at the same time on 3 different devi

  • To drop a 10g Express DB

    Hi, I think we can manually remove everything of that including its entries in the registry. Will there be any potential issues when we then further reset that up in the same PC (that uses Win XP)? Bst Rgds, HuaMin