COM on windows 2003 cluster

Tech-Archive recommends: Fix windows errors by optimizing your registry

Are there any special considerations or settings when running COM
server on a cluster, compared to single computer? I didn't find
anything on docs or MSDN - but if there's an article on such matters, a
link would be very helpful.
---
We have a setup consisting of COM server and 2 local COM clients: one
is our own (so we have full access to source), another is commercial
(OpcLink). Server and both clients are running as services, under same
user account. COM object is also configured (with dcomcnfg) to run
under the same user account. COM clients connect to 'localhost' with
CoCreateInstanceEx.

It works without any problems on a single machine Windows Server 2003.
But when we deploy it on a two-node active/passive cluster (all 3
services in the same cluster group), a weird problem appears. That is,
OpcLink fails to connect to COM server after our own client:
1. OpcLink connects (success), then our client connects (success)
2. Our client connects (success), then OpcLink connects (failure)
3. OpcLink connects (success), then our client connects (success),
OpcLink disconnects, then connects (failure).

There are no errors in event logs when connection fails.
It looks a bit like it tries to launch new instance of COM server
process if the current process was 'spoiled' by another client (and
fails, because second instance is not allowed).

Services and DCOM are configured exactly same on a single pc and
cluster systems, so I'm pretty sure the problem lies in clustering.

.

Relevant Pages

  • Re: Point and Print Restrictions policy
    ... You will need to enable DNS registration in order for the cluster name to ... Client side ... Disable the policy in a domain GPO that applies to all users (the policy is ... enabled since it's not configured by default) or add the server names to the ...
    (microsoft.public.win2000.printing)
  • Re: XML Well Services + .NET Remoting Design Pattern
    ... that allows a user to issue commands or retrieve info from the cluster. ... Would you classify the relationship between the remote stations and the ... initiated by both client and server, such as events/callbacks) or as purely ...
    (microsoft.public.dotnet.framework.remoting)
  • Another COM activation and windows stations question
    ... I've got similar situation - both client and COM server are services on ... The problem only appears on cluster, ... security and window station (when changing user account is not enough)? ...
    (microsoft.public.win32.programmer.ole)
  • Re: Multiple subnets and clustering (DCOM Client/Server app)
    ... > resource dll to communicate with my server app and all is working fine. ... Client PCs are connected to both subnets. ... > servers in my cluster configuration) to connect to the server application ... > Resource type: Network Name ...
    (microsoft.public.windows.server.clustering)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)