How to get Isolated COM Activation (Registration-Free COM using a .manifest file) to work on Windows Server 2003, Enterprise x64 Edition?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

DR - 18 Jan 2008 23:59 GMT

How to get Isolated COM Activation (Registration-Free COM using a .manifest
file) to work on Windows Server 2003, Enterprise x64 Edition?

The Isolated COM examples work on my Windows XP Pro but not on Windows
Server 2003, Enterprise x64 Edition.

On Windows Server 2003, Enterprise x64 Edition I get this error from
applications that use a manifest file to access com objects:
Retrieving the COM class factory for component with CLSID{......} failed
due to the following error 800700c1

On my XP Pro machine i have installed:
ms .net frmwrk 1.1
ms .net frmwrk 1.1 hotfix(kb928366)
ms .net frmwrk 2.0 service pack 1
ms .net frmwrk 3.0 service pack 1
ms .net frmwrk 3.5 framework 3.5 (prereleased version)

on my Windows Server 2003, Enterprise x64 Edition i have installed:
ms .net compact frmwrk 1.0 SP3 Developer
ms .net compact frmwrk 2.0
ms .net framework 2.0 (x64)

here example of Registration-Free COM using a .manifest file that I tested
on both machines:

Isolated COM Activation tutorial:
http://msdn.microsoft.com/msdnmag/issues/05/04/RegFreeCOM/

Isolated COM Activation sample project:
http://download.microsoft.com/download/2/e/9/2e9bde04-3af1-4814-9f1e-733f732369a
3/RegFreeCOM.exe

Reply to this Message

Nicholas Paldino [.NET/C# MVP] - 19 Jan 2008 02:33 GMT

DR,

Is the COM component you are trying to get to work a native component?
If so, is it compiled for a 64 bit machine? Or is it the 32 bit version?

Signature

- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com

> How to get Isolated COM Activation (Registration-Free COM using a
> .manifest file) to work on Windows Server 2003, Enterprise x64 Edition?
[quoted text clipped - 27 lines]
> Isolated COM Activation sample project:
> http://download.microsoft.com/download/2/e/9/2e9bde04-3af1-4814-9f1e-733f732369a
3/RegFreeCOM.exe

Reply to this Message

Willy Denoyette [MVP] - 19 Jan 2008 10:43 GMT

If they work fine on XP, and not on WS2003 X64, it means that the COM
components are 32-bit. That means that the client must be 32-bit too. If the
clients are managed applications, then you'll have to set the target
platform in your project properties to "X86" instead of "AnyCPU".

Willy.

Reply to this Message

How to get Isolated COM Activation (Registration-Free COM using a .manifest file) to work on Windows Server 2003, Enterprise x64 Edition?

Free Magazines