What's wrong with DCOM?
What's wrong with DCOM? There seems to be a lot of enmity against DCOM, and I'm curious to understand why. For a company still writing to the Win32 SKD using C++, is there any real reason not to use DCOM in current or future development? Is some future version of Windows not going to support it? Is it too fragile and fails to work often? Is it too complicated to implement compared to other technologies? What's the deal? Well, DCOM is a distributed version of COM and COM is very complex by itself and it's very easy to do something wrong unintentionally (see this recent question and the answer to it for examples). With DCOM you just have even more ways to hurt yourself. Other than that it works and is for example a good way for hosting in-proc COM components in a separated process. I implemented a large system using DCOM in the late 90's. Although it worked pretty well, there were

Going from COM to DCOM
Going from COM to DCOM I have a out of proc COM server (ATL based) and a Java app that instantiates objects from this COM server on the same machine. What more is needed to DCOM enable it? Is work needed on the COM server only or server and client? I know this is not a direct answer, but I can't help thinking that perhaps DCOM is no longer the right solution. You can instead wrap the COM object's functionality in a WCF web service that can be easily called from Java or C# or whatever. Please consider this alternative. Usually all you need is to have the proxy interface registered... of the server where the actual objects reside. As with any DCOM remoting you may have issues with DCOM permissions from the client to the server, which can be typically be resolved by using DCOMCnfg on the server side (Possibly on the client as well, if callbacks are being used). And of course potential

DCOM CoCreateInstanceEx E_ACCESSDENIED
DCOM CoCreateInstanceEx E_ACCESSDENIED I am working with 2 PCs, both running both running Windows XP. Both have the same application registered with its DCOM interface. Now i'm trying to start the program from one computer on the other. First I called CoInitializeSecurity, after that CoCreateInstanceEx, but the result is a E_ACCESSDENIED. I did also run dcomcnfg, to give anyone access, but it didn't help. access is ONE choice under dcom... you also need Launch and Activation settings... I'd hit that next... You have to add the user explicitly and give him all permissions. After that it works

Windows 2008 DCOM problem
Windows 2008 DCOM problem Hi, I have an DCOM server and when a process calls a method that changes the password of an user the next petition fails. This problem only occurs when the machine is a Windows 2008 working as Domain Controller. Anyone knows how to fix it? Thanks EDIT: There is an audit security error with the code 4625, I have been searching in google and there is a bug in MS Exchange 2007 with Windows Server 2008 that has the same behaviour, but was solved with a Hotfix of Exchange

Is there a viable counterpart to DCOM in .NET?
Is there a viable counterpart to DCOM in .NET? I know .net has WCF, which I believe was touted as the replacement for COM when it was codenamed Indigo(?) - but is it actually suitable for use in a .NET app, providing the same functionality as a C++/DCOM application? A DCOM app on a client-server... interface for writing client/server applications such as SOAP web services and remoting applications independently of the protocol/transport/serialization mechanism used. You can use WCF very efficiently by choosing the right behavior / serialization / protocol. Actually using COM/DCOM with dot-net will be less efficient today b/c of passing from dot net to com is slow. I'm not aware of any official guidance that names a successor for DCOM, but .NET has two frameworks that can replace usage of DCOM. They are WCF and .NET Remoting. WCF can be used as a replacement for all of the transport

The relationship between OPC and DCOM
The relationship between OPC and DCOM Hi all, I am trying to grasp the link between OPC and DCOM. I have watched all four of the tutorials here and I think I have a good feeling for what OPC is, but in one of the tutorials (the third one 35 seconds in) the narrator states that OPC is based on DCOM, but I do not understand how the two are really linked. My confusion comes from a question my professor posed in which he asked "How and where would you deploy OPC instead of DCOM and vice-versa." His question makes it seem like the two are not as linked as my research suggests. I'm not looking for anyone to answer the question my professor asked, I just want to know the relation between OPC and DCOM, then I can figure the rest out. Specifically I would like to know if: 1.) One is always based on the other 2.) One can always be deployed without the other. The way I read this is that DCOM

DCOM server debug
DCOM server debug Hi, I'm learning DCOM and I need to debug a class that I have created, how can I do this? Write a simplest client that does CoInitialize(), then CoCreateInstance(). Insert delays (call to Sleep() for example) into DllGetClassObject() of your server - with ATL you have the full source. After the client calls CoCreateInstance() attach the debugger to the server host process. I think DebugBreak could be of great help for this. You just need to add a conditional compilation line in the debug build to allow execution of this line and the debugger will start. The other way is attaching the debugger to the process and set a breakpoint in the process

Is there a alternative to DCOM on unix?
Is there a alternative to DCOM on unix? Hi All, Is there a COM implementation on UNIX platform. My requirements is that I have a COM client on windows , But I want the server on a AIX servers. I want to write COM clients and servers on unix platforms. Is there anyway to do this?. I tried looking for EntireX from software ag, but couldn't find it. also tried other commercial implementation of DCOM .like COMbridge , Java com bridge. But I need a open source production ready alternative. Am I asking for too much? Thanks all

DCOM Server failed to register
DCOM Server failed to register Hi, I am getting this error Source : DCOM Event_ID: 10010 "The server {6FC4FDAE-96C8-11D3-9F9C-005004053207} did not register with DCOM within the required timeout." This is for a particular exe which when run as local system works fine but when... DCOM can make you miserable... They fall between the system administrator and the programmer, and until one knows enough about the other's part they can be quite hard to overcome. As for your particular problem, the cause of this error message is a too long server startup, delaying the call... rights on both originating and target computers....(at least to configure and inspect) DCOM can be bewildering. When dealing with DCOM across machine boundaries the problem is most likely to be security from Conflicting and/or no Credentials, firewalls, and DCOM settings for the local machine

Setting Remote Launch in DCOM
Setting Remote Launch in DCOM I can use DCOMCNFG to disable remote launch on my DCOM application, but I would like to do this programatically. I looked at CoInitializeSecurity, but that does not seem to do it. Anyone done this? I am using Delphi BTW. The permissions for Remote/Local Activation/Launch are stored in the registry under the AppID for the object. I'm not sure how to edit it programmatically. The binary data is simply a security descriptor structure (PSecurityDescriptor). I mean it is a copy of the memory of this structure. And, of course, the security descriptor is self relative. JWSCL can create such a structure easily. Launch- and AccessPermission list for every user access rights that also contain remote and local access. This is very similar to change Access Permissions in Component Services > COM Security with script/api? for which i posted a response

DCOM Failure of Office Automation
DCOM Failure of Office Automation I developed a C# program that pulls data from a SQL Server database and then generates Word documents which include the data. I've set the program up to run as part of an SSIS job on a Windows Server 2003 box. The program runs as user SQLSVC which doesn't have.... at IepGlance.Program.CreateNewIepFiles(Dictionary`2 iepDictionary, EasyIepDataContext dbContext) at IepGlance.Program.Main(String[] args) As far as I can figure out the problem is with DCOM permissions. I've used dcomcnfg to add all possible DCOM permissions to user SQLSVC, but this hasn't... not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run

Configure DCOM Settings with native .NET?
Configure DCOM Settings with native .NET? Some time ago I found aout about the System.Directory namespace in .NET 3.5 that enables me to basically manage local as well as domain accounts easily with native .NET methods instead of using API calls and importing unmanaged DLLs. Now I need to configure DCOM settings for some legacy application from within an MSI setup. As far as I know there is no way doing it with on board means of InstallShield 2009. Is there any way of configuring DCOM settings with .NET so that I would be able to write a managed Custom Action e.g.? As far as I know - not in .NET see http://stackoverflow.com/questions/454368/dcomcnfg-functionality-programmatically#455903

DLL/TLB in Java<->DCOM communication
DLL/TLB in Java<->DCOM communication I have to write an OpenOffice add-on (in Java) which communicates with DCOM server of some closed-source application. The major problem is that, I don't have any documentation about server's Interfaces . All I have is a VB/C++ SDK kit for the Application. SDK contain a library in dll and a bunch of *.tlb files. In SDK documentation there is an information, I can use java, but there is no example at all. I have read provided examples and it looks like all the communication wit DCOM goes through this dll. Is there a way to somehow import such dll/tlb functions def directly to java, bypass dll and comunicate with DCOM or I have to write a C++ wrapper(dll)? What is the best way to do it? Any hints are welcomed. You can use a project like j-Interop for communication with (D)COM servers

Excel VBA to VB (DCOM)
Excel VBA to VB (DCOM) I inherited an Excel VBA spreadsheet. I have been tasked to convert it to VB. The application acquires data from a PLC using a DCOM object (I think). The following code runs the sub SBR1Select when MX1.0 is updated. Sub Workbook_Open() ActiveWorkbook.SetLinkOnData "dassidirect|strandburner!MX1.0", "SBR1Select" End Sub When I open Control Panel -> Administrative Tools -> Component Services, and then navigate to Console Root -> Component Services -> Computers -> My Computer -> DCOM Config the item "DASSIDirect" is listed, which I believe is what Excel references. How do I connect VB code to the PLC through the DASSIDIRECT component? NOTE: DASSIDIRECT is also a Windows service (not sure if this helps answer the question). I did some work with PLCs along time ago and asked one of my old colleagues. He says you need InTouch from WonderWare which has a set

Accessing DCOM Security with System.Security.AccessControl possible?
Accessing DCOM Security with System.Security.AccessControl possible? I know that the DCOM topic has been discussed a couple of times already. However, I am not satisfied with the solutions that are available (yet). This is why I start a new question here. Every knows by now that The Access Control... structs whatsoever, but I am sure that it's possible to implement a nice and intuitive .NET library that enables us to deal with DCOM Security Settings from managed code. Does anyone have an idea of how to do it? While I have not been able to find a fully managed solution, you will find a sample program DCOMPerm in the "Server 2008 Windows SDK". This can be used as a model to create a fully managed version of DCOM security settings. In my case, I read the license for the SDK, which states that object code created from the samples may be distributed. So I ended up EXEC'ing DCOMPerm.exe to set