CC2 Keyboard error Vista x64

Bodega · Apr 15, 2009

Hi!
I was hoping someone might be able to help me resolve the error:
ERROR 20090315-193248-0.008332s load_dll#267: could not load key_export.dll

Running:
Vista Ult x64
CC2 31/03/09
CF_USB_2-02-04
CFA635

C:\Program Files(x86)\CrystalControl2\cc2_keyboard.dll
C:\Windows\System32\key_export.dll copied from C:\Program Files(x86)\CrystalControl2\extras\keyboard-dll\
C:\ProgramData\CrystalControl2\cc2_keyboard.ini
[options]

[input00]
id=3347061253
repeat=250
key0=0x1048
key1=0

[input01]
id=3456925997
repeat=250
key0=0x101d
key1=0x1038
key2=0x1050
key3=0

C:\ProgramData\CrystalControl2\cc2_service.ini
. . .Attempt at winamp volume up
[m00-event01]
if_type=1
if=3347061253
cond=0
to=1.000000
do_type=3197071286
do=1.000000

I've followed the tips for running CC2 in vista and have cc2_service.exe configured as an automatic service.
The key-test.exe runs fine but cannot get any hotkeys to function.
Any advice would be much appreciated!!

Ringo Kid · Apr 15, 2009

Hi Bodega,

I just rebuilt my XP box and ran into the same thing. It was a year since I installed CC2 and I was at a loss for a while. I copied key_export.dll into system32, problem solved...

Beyond double-checking to be sure key_export.dll is in system32, fire up your system event log and see what the error actually is. There's usually more information in the system event log than in the cc2_keyboard.log. My own log told me key_export.dll was missing.

There may be some other rules at play here inside your Vista 64 environment. I haven't played with it much other than some simple functional testing within virtual machines -- hopefully, someone else might chime in.

One thing you could try is dropping the DLL into C:\Program Files(x86)\CrystalControl2 directory. DLLs are not required to be in system32 as long as they are visible to the program that tries to invoke the function in the DLL.

Let us know how you come out...

CF Mark · Apr 15, 2009

CC2 will need to be configured to run in the startbar tray for hotkeys to work.
Open up the CC2 config window, select the "General Options" tab, then select "User Tray Application" from the drop down box.

Note: that i have not tried this in Vista x64 myself

Bodega · Apr 17, 2009

Thank you both for your advice, unfortunately still not working but here is what I've tried:

When switching to User Tray Application, receive an Error Popup "Could write value to registry"
I am comfortable making edits to the registry if you could provide path and values.

Also, double-checked key_export.dll is present within the C:\windows\system32 folder.
Copying the key_export.dll file into the C:\Program Files(x86)\CrystalControl2 folder does indeed remove the error from cc2_keyboard.log:
NOTICE 20090317-201429-0.060229s load_dll#285: key_export.dll loaded successfully

But still the keyboard will not control the screen...
Checking through the Event logs I find:
The description for Event ID 4 from source cc2_keyboard cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
CRITICAL 20090315-205717-22.653434s DllMain#66: plugin exception error, terminated
the message resource is present but the message is not found in the string/message table

Please let me know if there are any suggestions.
Thanks!

Bodega · Apr 18, 2009

Hi, some progress but more problems

I was able to get the CC2_TRAY option setup by changing those settings from the Admin account.
And I have seen the keyboard keys work briefly to dim the display and scroll screens!
Unfortunately the light at the end of the tunnel dims fast and I loose key functions within a minute.

Now the issue seems to be a conflict problem in CC2_TRAY.EXE.
Some symptoms: my windows taskbar will freeze up, also while browsing directories in explorer, it will go to Not Responding status. As soon as I kill the cc2_tray task, the not responding goes away and the system behaves fine.

Noticing these Error events in the Application around that time, also attaching logs from \Program Data\CC2:
The COM+ Event System could not remove the EventSystem.EventSubscription object {CEB8B221-89C5-41A8-98CE-79B413BF150B}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The HRESULT was 80070005.

Activation context generation failed for "C:\Program Files (x86)\CrystalControl2\cc2_tray.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\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001.18000_none_5cdbaa5a083979cc.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001.18000_none_152e7382f3bd50c6.manifest.

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

The program Explorer.EXE version 6.0.6001.18164 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Problem Reports and Solutions control panel. Process ID: bb0 Start Time: 01c9c03e0d1b92b8 Termination Time: 0

Any help in translation or suggestions for a workaround would be most welcome.
Thanks!

PS: Vista Ult x64 - AMD Phenom II X3 720

Bodega · Apr 19, 2009

While searching the errors:
"Error in manifest or policy file. A component version required by the application conflicts with another component version already active"
I came across this blog which speaks to the root cause:
"not all parts of application’s source code are built with the same version of VC++ libraries and tools"
and recommends "must rebuild all parts of your code with the newest toolset and libraries"

http://younsi.blogspot.com/2007/06/manifest-hell.html

I do have MSVC++ 2008 Express 9.0.30729.1 SP and .NET Framework 3.5 SP1 installed but would need some additional help in attempting either of the 3 solutions presented in that blog. If that is correct and applies, you can never trust what you read I well understand

Second opinions please!

Ringo Kid · Apr 20, 2009

Sorry you're still being challenged by this.

I too have a quirky problem that I've lived with since I got this thing. In my circumstance, I cannot drag a custom character in CC2's screen editor. When I do it hangs. And it has done this through two complete builds of my system. I only mention this because I too have Visual Studio installed. Is there a connection?!?! In my case, I hand edit the INI when I need a custom character and everything works.

This is scatter gunning. I've included a link for Belarc Advisor. This software audits your system and tells you if there are any missing or improperly applied critical updates as well as other information. It's free in a non-commericial situation and runs from inside your browser. In my experience, if Windows Explorer tanks, then there is some internal issue with the system. http://www.belarc.com/free_download.html

Bodega · Apr 26, 2009

ERROR: Activation Context generation failed.

Thanks for the tips but Belarc did not reveal any issues.

Researching more into the Side By Side Event 78:
Activation context generation failed for "C:\Program Files (x86)\CrystalControl2\cc2_config.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\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001.18000_none_5cdbaa5a083979cc.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001.18000_none_152e7382f3bd50c6.manifest.

All the information I can find points to a problem with the build of the application.
Also by running sxstrace I was able to create the following log with some more information about the event associated with cc2_config.exe:

Code:

Begin Activation Context Generation.
Input Parameter:
	Flags = 0
	ProcessorArchitecture = AMD64
	CultureFallBacks = en-US;en
	ManifestPath = C:\Program Files (x86)\CrystalControl2\cc2_config.exe
	AssemblyDirectory = C:\Program Files (x86)\CrystalControl2\
	Application Config File = 
-----------------
INFO: Parsing Manifest File C:\Program Files (x86)\CrystalControl2\cc2_config.exe.
	INFO: Manifest Definition Identity is cc2_config.exe,processorArchitecture="*",type="win32",version="1.0.0.0".
	INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="*",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
	INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762"
	INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
INFO: Resolving reference Microsoft.Windows.Common-Controls,language="*",processorArchitecture="*",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0".
	INFO: Resolving reference for ProcessorArchitecture AMD64.
		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_64\Microsoft.Windows.Common-Controls\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.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_64\Microsoft.Windows.Common-Controls\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
				INFO: Did not find manifest for culture en.
			INFO: End assembly probing.
		INFO: Resolving reference for culture Neutral.
			INFO: Applying Binding Policy.
				INFO: Auto Servicing Policy redirected assembly version.
				INFO: Post policy assembly identity is Microsoft.Windows.Common-Controls,processorArchitecture="AMD64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.6001.18000".
			INFO: Begin assembly probing.
				INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001.18000_none_152e7382f3bd50c6.manifest.
				INFO: Manifest found at C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001.18000_none_152e7382f3bd50c6.manifest.
			INFO: End assembly probing.
INFO: Resolving reference Microsoft.Windows.Common-Controls.mui,language="*",processorArchitecture="AMD64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.6001.18000".
	INFO: Resolving reference for ProcessorArchitecture AMD64.
		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_64\Microsoft.Windows.Common-Controls.mui\6.0.6001.18000_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.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_64\Microsoft.Windows.Common-Controls.mui\6.0.6001.18000_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.
				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.50727.762".
	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.3053_none_516e2c7b0f48c07f.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.3053".
			INFO: Begin assembly probing.
				INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.3053_none_d08d7bba442a9b36.manifest.
				INFO: Manifest found at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.3053_none_d08d7bba442a9b36.manifest.
			INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC80.CRT.mui,language="*",processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.3053".
	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.3053_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.3053_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
				INFO: Did not find manifest for culture en.
			INFO: End assembly probing.
INFO: Resolving reference Microsoft.Windows.Common-Controls,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0".
	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.Windows.Common-Controls\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.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.Windows.Common-Controls\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
				INFO: Did not find manifest for culture en.
			INFO: End assembly probing.
		INFO: Resolving reference for culture Neutral.
			INFO: Applying Binding Policy.
				INFO: Auto Servicing Policy redirected assembly version.
				INFO: Post policy assembly identity is Microsoft.Windows.Common-Controls,processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.6001.18000".
			INFO: Begin assembly probing.
				INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001.18000_none_5cdbaa5a083979cc.manifest.
				INFO: Manifest found at C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001.18000_none_5cdbaa5a083979cc.manifest.
			INFO: End assembly probing.
ERROR: Two assemblies have the same assembly name with different version. Assembly 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001.18000_none_5cdbaa5a083979cc.manifest. Assembly 2: INFO: Manifest found at C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001.18000_none_5cdbaa5a083979cc.manifest..
ERROR: Activation Context generation failed.
End Activation Context Generation.

Any help resolving would be much appreciated, thanks!

(edit by admin: added code tags)

CF Mark · Apr 27, 2009

Thanks for all the information and links guys, it helps a lot.

First thing ill try is making sure my VS2005 install is up to date, and im using the latest 2005 redist package.
Ill then completely rebuild CC2, create an installer, and put it up in here for you guys to try.
Ill have it up later today or tomorrow.

CF Mark · Apr 28, 2009

Give this new build a try.
All code has been built by VS2005 SP1 with all updates, etc.
Included is also the latest VS redist package.

The new build is attached...

Ringo Kid · Apr 29, 2009

I've tried the new build and the screen editor still hangs when I try to drag and drop a custom character. I had hoped that there was a common link between Bodega's problem and mine since we both have Visual Studio installed.

Maybe you'll have better luck Bodega and I'll monitor this thread, but I'm at a loss and doubt I have much else to contribute.

Note to CC2 Administrator:

As soon as the new CC2 screen editor is started -- the following message is displayed. Please click it to see a larger version.

The text is a little clipped and maybe the message shouldn't display at all since the version installed is a later version anyway.

CC2 Keyboard error Vista x64

Bodega

New member

Ringo Kid

New member

CF Mark

Administrator

Bodega

New member

Bodega

New member

Attachments

Bodega

New member

Ringo Kid

New member

Bodega

New member

CF Mark

Administrator

CF Mark

Administrator

Attachments

Ringo Kid

New member