Local Registration of Remote COM Server

Posted on 2000-02-09
Medium Priority
Last Modified: 2012-05-04
An Active Form Application embbeded in a simple html page. The Application interacts with an Automation server residing on a remote machine. The Active Form will Auto Connect to the Automation server on a predefined machine.

The html page resides on a web server.

When a client pc loads the page the embedded ActiveX application tries to connect to the Remote Automation Server,but fails.

Question: Does the client PC have to have entries in its registry describing the remote automation server?
Question by:bfjvr
  • 2
LVL 12

Expert Comment

ID: 2506778

Accepted Solution

ellessar earned 600 total points
ID: 2506958
No it does not require that the remote automation server be registered, but only if your application can connect to the remote server on it's own. For instance, the Midas TDCOMConnection object can connect to a remote server, as can the TSocketConnection. If you are not using internal mechanisms to connect, then you will need to register the server so that the object can be found (using Distributed COM). For windows 95 this means a downloaded application (search for DCOM95), WinNT and Win98 come with a dcom configuration tool.

Author Comment

ID: 2510575
The component in the client was imported from the automation object's type library and installed as a component in Delphi5.

This component has machine name and connect kind properties - therefor I take it that it knows how to connect to the remote server on its own.

However, it still gives trouble on client machines

Author Comment

ID: 2511178
I have reworked things somewhat and now have the following situation:

The Client PC has no registry entries describing the server. (WHAT I WANT)

When a client pc loads the html page, I can see that the embedded ActiveX control (ActiveForm)makes a connection to the server - I know this because if I try to close the server, it tells me that the server is in use and cannot be shut down.If the server is not in use, one can normally just exit it without any warnings.

However, when I try and execute one of the server methods from the client, the client reports the following error -Interface not Supported.

If I run the Server.exe once on the client PC it adds entries to the client pc registry which describe the server (WHICH I DONT WANT). After this, the whole thing work correctly.

Any comments would be appreciated.

Featured Post

[Webinar] Improve your customer journey

A positive customer journey is important in attracting and retaining business. To improve this experience, you can use Google Maps APIs to increase checkout conversions, boost user engagement, and optimize order fulfillment. Learn how in this webinar presented by Dito.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The uses clause is one of those things that just tends to grow and grow. Most of the time this is in the main form, as it's from this form that all others are called. If you have a big application (including many forms), the uses clause in the in…
Have you ever had your Delphi form/application just hanging while waiting for data to load? This is the article to read if you want to learn some things about adding threads for data loading in the background. First, I'll setup a general applica…
The Relationships Diagram is a good way to get an overall view of what a database is keeping track of. It is also where relationships are defined. A relationship specifies how two tables connect to each other. As you build tables in Microsoft Ac…
Enter Foreign and Special Characters Enter characters you can't find on a keyboard using its ASCII code ... and learn how to make a handy reference for yourself using Excel ~ Use these codes in any Windows application! ... whether it is a Micr…
Suggested Courses

601 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question