Event ID/Source search
Keyword search
Example: Windows cannot unload your registry file
Event ID: 80 Source: SideBySide
| Source: SideBySide |
| Type: Error |
| Description: Activation context generation failed for "C:\Program Files (x86)\2.T1\Acrobat 9.0\Designer 8.2\FormDesigner.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.7600.16385_none_fa645303170382f6.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc.manifest. |
| English: Request a translation of the event description in plain English. |
| Concepts to understand: What is the role of Side-by-Side? What is a manifest? |
| Comments: EventID.Net There are many programs that can generate this type of error. Any suggestions found on support forum or software developers sites should be verified that they apply to your application (though comments for other applications may provide additional clues in solving this). The first step in troubleshooting this would be to check for updates for the application specified in the event. A common application causing this problem is Adobe Designer (C:\Program Files (x86)\Adobe\Acrobat 9.0\Designer 8.2\FormDesigner.exe). From an Adobe Support Forum: "For Vista 64 bit users this error seems to be caused by a wrong manifest embedded in the FormDesigner application. It references the common controls dll - one processor-agnostic (*) version and one version requiring x86. On a 64-bit machine processor-agnostic references will apparently resolve to the 64-bit version. The error in the event log is legitimate since imports are already defined from whatever version was process first." A similar comment (almost identical but with more details), that apparently, if followed, can fix the problem: "This error is caused by a wrong manifest embedded in the FormDesigner application. If you open the application in Visual Studio and extract the manifest you will see two references to the common controls dll - one processor-agnostic (*) version and one version requiring x86. On a 64-bit machine processor-agnostic references will apparently resolve to the 64-bit version. The error in the event log is legitimate since imports are already defined from whatever version was process first. To test just try removing the processor-agnostic reference from the manifest and resave the app in Visual Studio. When you rerun the app the errors are gone. IMO this should be fixed by Adobe - and obviously since the FormDesigner app is 32-bit the reference should be restricted to 32-bit."  x
9
|
| Private comment: Subscribers only. See example of private comment |
| Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue - More links... |
| Custom search for *****: Google - Bing - Microsoft - Yahoo |
| Feedback:
Send comments or solutions
- Notify me when updated
|
| Printer friendly |
Subscribe to EventID.Net now!