Event ID 80 SideBySide

Report · Sep 26, 2013

I am getting the below error while trying to open Dreamweaver though the application runs alright. The errors started to appear after the CC update. Could someone please suggest me how to fix these issues.

Activation context generation failed for "C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC\Dreamweaver.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.

Report · Dec 17, 2013

Preran said "From what I understand, we have logged a bug for this issue and it is going to be fixed in the next update."

It wasn't.

Just installed the DW update, and it wasn't fixed.

The 2nd workaround fixed it. For now.

Next time it gets updated I will need to edit Dreamweaver.exe again. And my Resource Tuner trial will have expired and I will need to purcahse it.

Why doesn't Adobe just FIX this problem?

Report · Dec 18, 2013

Indeed - was hopefull for a second and then it closed. Same thing happens in Photoshop

I've taken to use Visual Studio Express now. Mostly because it works. Might have to seek an alternative to Photoshop now as well.

Report · Jan 04, 2014

I have exactly the same issue on a Win7 64-bit machine -- Side By Side errors int he Event Log for Dreamweaver CC every time I launch it. Only difference is that it doesn't crash; I can still use it... I don't get the error at all for Photoshop.

I do have DW CS6 still installed - would that cause the issue?

Report · Jan 17, 2014

Hi Arindam,

Method #2 definitely worked for me. It appears that my manifest had two entries for Microsoft.Windows.Common-Controls. One had a processorArchitecture entry of "*" and the other had "x86". I assume the problem was caused by the conflict. As instructed, I removed the entry for "*".

Obviously this is not a great workaround for everyone, as it is pretty technical. I definitely hope this will be resolved in a future patch.

Like BlueBear, the problem didn't cause me to crash--Dreamweaver still ran fine. Like him, I also still had CS6 installed as well, so maybe that is a culprit?

Thanks,

Christopher

Report · Jan 23, 2014

Hi All,

We are constantly working on the issue. The only problem is that we still haven't been able to reproduce the issue in-house.

I kindly request all of you, if anybody has exact reproducible steps to replicate this issue, please let us know. We will work on priority to fix this.

Please let us know.

Thanks,

Arindam Ghosh

Report · Jan 23, 2014

For me the exact steps are:

1. Start Dreamweaver.

Report · Jan 23, 2014

Hi Arindam,

I'll tell you my machine setup. I am running Windows 7 Pro (64-bit) SP1. I have both CS6 and CC installed. CS6 was installed before the Creative Cloud installer was available, and I have gone through numerous updates of the CC main application; I have not uninstalled CS6 which I think causes some confusion. For example, when updates are available I still get old style Adobe Application Manager notifications as well as notifications in the Creative Cloud app (not sure if this is normal behavior).

Since I tried your 2nd workaround, I have not seen the behavior return. But before I did that, I would get this error periodically in my event log, often at login or after the computer resumed from sleep, in addition to when Dreamweaver is first run. The problem did not affect my use of the program.

Hope this is helpful.

--

Christopher

Report · Jan 23, 2014

My setup and symptoms are exactly like Christopher Smith's, except the workaround DIDN'T work and I continually see the error EACH TIME I start Dreamweaver....

Report · Jan 28, 2014

Workround 2 fixed the error that I'm seeing on my Event log not sure if it is related or not but I'm seeing tmp file being create for the files that I'm working on. Let say I'm working a filename called index.html it will generate index.html~RF######.tmp, where # is some random digit mostly but occasionally letters. It happen randomly. It will generate several index.html~RF######.tmp and sometime it doesn't.

I download this app, Process Monitor. which allow me to track down which process created those ~RF#####.tmp file.

http://technet.microsoft.com/en-us/sysinternals/bb896645

It shows that dreamweaver does create <original filename>~RF######.tmp and it also removed it. But there are times that it failed to removed it which result to actual creating of the file.

Just to point out that I still be able to run dreamweaver before applying the workround 2 and I don't have cs6 installed.

Ben

Report · Jan 30, 2014

Hi All,

We are investigating the issue. We need some help from you guys as well.

Can you please send these 2 files (in a zipped format - .zip) from your affected systems to my email ID: arghosh@adobe.com

Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6 595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest

Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_659 5b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest

Looking forward to hearing from you.

Thanks,

Arindam Ghosh

Report · Jan 31, 2014

Hi Arindam,

I sent you the files from my email account. Please let me know if you don't receive it.

Thanks,

Christopher

Report · Jun 18, 2014

Hi All,

This bug has been fixed in the latest version of Dreamweaver CC 2014, which is now available for download.

Download it from https://creative.adobe.com/ or directly through the Creative Cloud desktop app.

We’re excited to hear back from you. Please share your feedback.

Report · Jun 28, 2014

Your excitement may be short lived I'm afraid, I still have this issue. From event logs:

Activation context generation failed for "c:\program files (x86)\Adobe\adobe dreamweaver cc\Dreamweaver.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.

Using Dreamweaver CC 2014 build 6733.

Report · Jun 28, 2014

Specs, Do you have both versions installed? The old version will still cause this error until it is uninstalled. Even if you don't start it up.

Report · Jul 13, 2014

dv8kiwi.

Thanks for your help,

Sorry took so long but I get over 100 emails a day and I am just plowed under.

Anyway the creative cloud app is more intelligent now and for the first time since it's release it now RECOGNIZEES when a CC program has been deleted and allows the re-installation or a new one. And that was the solution to the problem. I deleted DW with Revo-uninstaller (great program) which removes all of the leftover crumbs and registry bits which allows the clean install of the cc program. I deleted DW and re-installed, that did not quite get it so I deleted and reinstalled Creative Cloud app.-- that was a final fix.

I still have no clue what Side-by-side error is (I think it was a Broadway show which went Bankrupt) but it seems to require the removal of both the CC app and the CC program app.

To answer your question: no I wiped all of the pre 2014 stuff. I t would be nice if Adobe put all of the customization of the various apps in a single location without having to back up user files and some of the customized program files (presets, required, workspaces, shortcuts...).

Report · Aug 20, 2014

dv8kiwi,

I have uninstalled the older version of DW CC.

Adobe Creative Cloud is in the latest Version, DW CC 2014 corresponds to Build 6733.

Nevertheless I still find «Event ID 80 SideBySide» with following details (in German, sorry):

Fehler beim Generieren des Aktivierungskontexts für "c:\program files (x86)\Adobe\adobe creative cloud\Utils\Creative Cloud Uninstaller.exe". Fehler in Manifest- oder Richtliniendatei "" in Zeile . Eine für die Anwendung erforderliche Komponentenversion steht in Konflikt mit einer anderen, bereits aktiven Komponentenversion. In Konflikt stehende Komponenten:. Komponente 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest. Komponente 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest.

What have I to do to get this bug fixed ???

Thanks in advance for your help.

Windows 7 Ultimate (64 Bit), all updates excepted KB 2982791 which has been uninstalled as recommended by MS

Report · May 22, 2014

Hello fellow error sufferers:

I am having the same error 80. As I read the description it says DW.exe's " manifest or policy file" is in conflict with: "A component version required by the application conflicts with another component version already active." The other component appears to be:

"manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest".---

You know, I don't want to get into a rant here but it is not my job as a customer to trouble shoot and fix these errors such as listed above. I am glad to cooperate but, I think I have been more than cooperative and actually tried the suggestions. Ya, I hear the suggested fix has worked for some people, I guess we are just special people.

I have no IDEA what that string means or what I would do when , IF, I ever found it wherever it may be. For me this has been going on to months, MONTHS, and all I have so far is 1 (one) "suggestion" from Adobe and 0 (zed) from MS-- "call Adobe it is their software.. I have gone all the way back to WIPING THE DISK and installing a build of win 7 "hot off the griddle downloaded from MS directly. I am at my Even MSC and it says I have 141 DW ERROR 80 IN THE LAST 30 DAYS!! I read the problem is shared by a lot of good people here and we are the ones who still are HOPEING some Tech Coder will sit down and spend a weeks worth of Adobe's/Gate's money to give us an answer besides go back 90 day-- I have gone back with clean installs, in windows 7 time, about 5 years.

How about this as a suggestion from me: the error 80 conflict says it is part of the x86 manifest, I am running x64 and DW is 32 bit, right? So could the problem be there? I am just asking.

Hear from ya'all soon,
and see ya on the upload.

DBellas

P6T-V2 DELUXE, i7-950 oc 4.0, 12GB RAM Corsair Vengence, Quddro PNY 3800, 8TB RAID 5, 850W Master Cooler, 12 pair of black socks, Same boxer briefs, 3 pair shorts, and 1 cat...

Report · Oct 29, 2013

I am getting the same SideBySide error attributed to Dreamweaver.exe

Having only performed a clean install of W7 last week, I am unable to restore to a point prior to that.

Which is the MS security patch that's causing the issues?

Thanks.

Report · Nov 04, 2013

I would really like to fix this problem

Report · Feb 11, 2014

Under normal circumstances System Restore does exactly that.

It Restores the entire system BACK to an earlier time.

Restore system files and settings

System restore can help fix problems that might be making your computer run slowly or stop responding.

System restore does not effect any of your documents, pictures or personal data. Recently installed programs and drivers might be uninstalled*** Here is the point. Uninstall a program, do a system restore and it can be "re-installed"

This is part one of why this is not a fix.

Part 2 IF you follow these steps, it MAY work briefly, BUT once Windows does its updates (For security purposes it is a good idea and goos practice to keep ALL programs up to date) it will simply take you back to where you were, a complete waste of time frankly. I think ADOBE needs to stop BLAMING all the users, other software, users system faults and JUST FIX DREAMWEAVER CC it is full of BUGS!!!!

Report · Feb 11, 2014

Hi All,

We have been able to reproduce the issue at our end and are analyzing it. We are also working on prioritizing it for fixing.

Thanks for your patience.

Thanks,

Arindam Ghosh

Report · Feb 16, 2014

Good to hear.

Edit: I should say, that dreamweaver is running fine. With the exception of connecting to a server. It will time out and I must force quit dreamweaver. (This maybe due to a DHCP error)

OS Name: Microsoft Windows 7 Ultimate

OS Version: 6.1.7601 Service Pack 1 Build 7601

OS Manufacturer: Microsoft Corporation

OS Configuration: Standalone Workstation

OS Build Type: Multiprocessor Free

Original Install Date: 3/8/2011, 7:18:29 PM

System Boot Time: 2/16/2014, 3:32:55 PM

System Manufacturer: Hewlett-Packard

System Model: HPE-590t

System Type: x64-based PC

Processor(s): 1 Processor(s) Installed.

[01]: Intel64 Family 6 Model 44 Stepping 2 GenuineIntel ~3334 Mhz

BIOS Version: American Megatrends Inc. 6.10 , 9/16/2010

Total Physical Memory: 16,375 MB

Available Physical Memory: 11,821 MB

Virtual Memory: Max Size: 32,748 MB

Virtual Memory: Available: 28,270 MB

Virtual Memory: In Use: 4,478 MB

Report · Mar 06, 2014

Hi there,

We have same issue on multiple PCs with Windows 7, x64, with Adobe CC installed.

Please provide a fix to this asap

Thanks!

Chris

"

Log Name: Application

Source: SideBySide

Date: 3/6/2014 12:31:05 AM

Event ID: 80

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: xxxxxxxxxxxxx

Description:

Activation context generation failed for "c:\program files (x86)\Adobe\adobe dreamweaver cc\Dreamweaver.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.

Event Xml:

<Channel>Application</Channel>

<Computer>xxxxxxxxxxxxxxxxxxxxxxx</Computer>

</System>

<Data>C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest</Data>

<Data>C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>c:\program files (x86)\Adobe\adobe dreamweaver cc\Dreamweaver.exe</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

</EventData>

</Event>

"

Report · Mar 06, 2014

They still working on the solution. They provided some ugly fixed but in result causing a new problem me. Until they fixed the .net framework component or upgrade latest .net framework, I will stick with dreamweaver cs6 which is more stable unless you want to use the newer feature in cc.

Report · Mar 06, 2014

Hello everyone,

We have now fixed this issue internally and the fix should be available in the next release of Dreamweaver (I do not have a date for it).

Thanks,

Arindam Ghosh.