Re: 64 bit C# trying to call a 32 bit CPP ATL Service

Your #3 is exactly the situation we have. The C# program is a separate process using a CCW to call into a ATL SERVICE, which is DCOM and should satisfy #3. But this still does NOT work.


"Jialiang Ge [MSFT]" <jialge@xxxxxxxxxxxxxxxxxxxx> wrote in message news:zjpUWXcqIHA.1784@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello Scott,

From your post, my understanding on this issue is: you wonder how to use a
64bit C# client consume a 32bit ALT service. If I'm off base, please feel
free to let me know.

Based on my experience, this is a very common question when developers
migrate applications from 32bit platform to 64bit. The answer that 64bit
process cannot load a 32bit module into its process space, and vice versa,
applies to all the Windows applications, besides this COM scenario. From
your issue description, I see the ALT service is configured as a in-process
component. "In-process" means that the 32bit component will be loaded into
the process space of the client application (64bit). 32bit components are
registered to HKEY_CLASSES_ROOT\WOW64\CLSID in a 64bit system while 64bit
components are registered to HKEY_CLASSES_ROOT\CLSID. Because our 64bit
client cannot find the component with CLSID or ProgID under
HKEY_CLASSES_ROOT\CLSID registry key, the error 0154(Class not registered)
is thrown.

To workaround this 32bit versus 64bit conflict, we have three choices:
1. As you've already tried, we can compile the client application to target
x86 platform that is compatible with the COM component. The problem of this
workaround is that none 64bit client can consume the component.

2. We build a 64bit version of the ATL service, apart from the 32bit one.
Then register both on the 64bit machine. In this way, all clients
(regardless of whether 32bit or 64bit) can consume the component.

3. We configure the 32bit ATL service as out-of-process component (e.g.
DCOM), so that the 64bit client process can access the 32-bit DLL across a
process boundary when the 32-bit DLL is loaded into a separate 32-bit
surrogate process space.

I'd also suggest you read
http://dnjonline.com/article.aspx?ID=jun07_access3264, and the articles in
its "References" section. They describe the 64-bit versus 32-bit issue in
very detail.

Let me know if you have any other questions or concerns.

Regards,
Jialiang Ge (jialge@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


.

Relevant Pages

  • RE: Outlook does not find name in addess list - exchange
    ... For the client workstion's OS is a non-English version, ... contact the local CSS for support. ... Microsoft CSS Online Newsgroup Support ... Please check the RPC_Binding_Order registry value on the machine. ...
    (microsoft.public.windows.server.sbs)
  • Re: 64 bit C# trying to call a 32 bit CPP ATL Service
    ... Since my last post I have created a 64 bit CPP exe that does a CoCreateInstanceEx to my CPP ATL service, currently running on the same machine, and I get the same results as with the C# 64 bit process. ... My first candidate would be the registry reflection. ... What version of VS are you using to build the C# client, are you sure that the client isn't running in the "Virtualized" mode?. ... Microsoft Online Community Support ...
    (microsoft.public.vc.atl)
  • Re: 64 bit C# trying to call a 32 bit CPP ATL Service
    ... CoCreateInstanceEx to my CPP ATL service, currently running on the same machine, and I get the same results as with the C# 64 bit process. ... Virtualized mode is for backward compatibility, this is the mode that turns on filesystem and registry reflection, it's only applicable for 32-bit processes running under Wow64. ... What version of VS are you using to build the C# client, are you sure that the client isn't running in the "Virtualized" mode?. ... Microsoft Online Community Support ...
    (microsoft.public.vc.atl)
  • Re: windows client cant start completely...get blank desktop and no icons, start button, task bar, e
    ... Can you access the registry remotely from another workstation or the ... "Logon to the problematic client as a user who can logon to other ... Logon to a working client as the user who encountered the problem. ... not supported in newsgroup support. ...
    (microsoft.public.windows.server.sbs)
  • Re: 64 bit C# trying to call a 32 bit CPP ATL Service
    ... Working with the Microsoft tech on a live session we could easily duplicate ... the error from both a 64/cpp and a 64/.net client to the 32 bit atl service. ... candidate would be the registry reflection. ... Microsoft Online Community Support ...
    (microsoft.public.vc.atl)
Loading