View Full Version : How to register DCOM server?
11-11-2002, 03:15 AM
My application consists of two layers that can be installed on the same computer or on two different computer using DCOM.
1) I would like to know how I can register the DCOM server on the client computer during the installation process
2) How can I change the security properties of the server so it will accept remote connections automatically. I know how to do it using dcomcnfg.exe but I want InstallShield to do it for me, if it is possible.
11-12-2002, 12:16 PM
Which development environment are you using? VC++ ? VB ?
1. You must register the type library on the client. Use the
Component Wizard to create a COM Server component that
includes only the type library;
2. Launch the dcomperm tool. It is available from MSDN as a
sample. Download the source and compile it.
11-13-2002, 01:47 AM
I'm using both VB and VC.
I've tried the dcomperm.exe but it throws an exception while I'm using it.
Is there a way for InstallShield to perform the duties of dcomperm?
Since it can extract the COM data and retreive all the registry keys then it shouldn't be a problem to add the necessary data to the registry in order to set the security, Or perhaps I can access the extracted data and do it myself somehow?
11-13-2002, 04:46 AM
Exception ? Which exception ?
I'm using dcomperm without problems.
Settings ACLs can be tricky. I strongly suggest you to
give dcomperm another try.
11-13-2002, 05:27 AM
I can't remember the exact message but it happend both on NT4 and on w2K.
If there's no better solution i will give it another go
11-15-2002, 11:55 AM
I found the easiest way to register the client side object is to simply install and register the same DLL on both the client and server machines. In VB6, to instantiate the remote object, I used CreateObject() and specified both the ProgID and the server. This permitted the server used to be a configurable option. On the server side, we use the COMAdmin.dll object to directly set up the COM+ servers. We did this outside of InstallShield since we needed a utility to manage the configuration anyway.
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.