OCX "not correctly registered" on 64 bit Windows Server 2008 R2

I have an ActiveX control that works fine on all other boxes and OS versions except for this 64 bit 2008 Server. I have tried everything I know to make it work. I have 2 versions of this control, our version 1 and version 2. Version 1 works fine, version 2 gives the dreaded "component 'version2.ocx' or one of its dependencies is not correctly registered". I have supervisor rights and I also right click on a shortcut to the cmd window on my desktop so I can make sure I "run as supervisor" when running regsvr32.

1. I used the exact same procedure to register my version 1 and version 2 controls. Version 1 has 2 dependent dll's that I also must register, while version 2 was re-written to eliminate depenencies and get rid of the license file.

2. I use the 32 bit regsvr32.exe in the SysWow64 folder and install my OCX into this folder. It "says" it registers correctly. Any anybody download my OCX and the test program and see what it does on their 64 bit 2008 server?

3. Version 1 OCX works fine while version 2 OCX throws the error when I run a very simple VB6 sample program.

4. Dependency walker is identical when analyzing each OCX. I can't see anything that would be different or that would be other than a warning.

5. The only difference other than the error is that if I run my test app in profile mode, I see a first change exception:

00:00:04.602: LoadLibraryExA("C:\Windows\system32\version1.OCX", 0x00000000, LOAD_WITH_ALTERED_SEARCH_PATH) returned 0x024A0000.
00:00:05.148: GetProcAddress(0x024A0000 [version1.OCX], "DllRegisterServer") called from "MSVBVM60.DLL" at address 0x729AAD4B and returned 0x024BA364.
00:00:05.164: First chance exception 0x0EEDFADE (Unknown) occurred in "KERNELBASE.DLL" at address 0x7736B727.

I notice that despice having the OCX in SysWow64, the path here shows System32. I am assuming this is ok and it is redirecting. Otherwise, something must be wrong in the registry. I don't know if the log window is synced with the error box, but the last lines to execute in dependency walker when the error box pops up are these:

00:00:01.420: LoadLibraryExW("C:\Windows\syswow64\MSCTF.dll", 0x00000000, LOAD_WITH_ALTERED_SEARCH_PATH) called from "USER32.DLL" at address 0x756E982D.
00:00:01.420: LoadLibraryExW("C:\Windows\syswow64\MSCTF.dll", 0x00000000, LOAD_WITH_ALTERED_SEARCH_PATH) returned 0x76E70000.
00:00:01.420: GetProcAddress(0x771A0000 [GDI32.DLL], "GdiIsMetaPrintDC") called from "USP10.DLL" at address 0x770C8306 and returned 0x771B8846.

Thanks for any help. How can I debug this further to actually find the error. There must be some way to see exactly where it is failing so I know how to fix it.

version2.ocx may have compiled wrong try recompiling it

I believe I have figured out part of the problem on Vista. It has to do with registry virtualization. So far, I haven't had any luck getting around it, but I'm using Perl. I bet if you're using C++ or something like that, there will be a better supported way around it. Right now, I can see the key and confirm that it will decode when I export it using the "reg" command. This is the "DigitalProductId" field. The ID4 has nothing to do with it.

********************
links removed-not permitted on forum

Maybe I missed something but did you say what the application is - I mean the parent application. Is that a 32bit application or is it a .net application ? If it's a dot.net application then, by default, it will try to run in 64 bit mode on a 64bit OS and when in 64bit mode I don't think it can load a 32bit ocx.

If it's a dot.net application did you compile it for x86 ?