Hi Darren,

EXE servers have both Access and Launch permissions and it looks while you may have set one you may not have set the other. DCOM permissions are one of most complex operations related to COM because correct permissions may have to be set in many places.

There are two sets of permissions: Global DCOM permissions and local to the server. In both cases you'll want to make sure that the or group user launching server has rights to do so for both Access and Launch.

In Windows Server 2003 SP1 there additional options for completely restricting access to a server via options to restrict DCOM access via checkboxes on the global settings, which IMHO is extremly confusing as they overlap with original functionality.

In Web Connection EXE COM configuration is common, but there's a setup application that can manage all that automatically. However I have docs that describe the process step by step here:

http://www.west-wind.com/webconnection/docs/index.htm?page=_S901DVUWG.htm

This might help you on where to look at what to set...

Hope this helps,

+++ Rick ---



>Hi All,
>
>I am having problems with setting up a com application. I have added a test application to my server (SBS 2003) and can access it locally on the server and can also create the object with createobjectex() on a remote machine. But when I try to access a function in the object eg. oObject.mytest(2,5) I am getting a "Access is denied error".
>
>On the server I have 'Enforce access checks for this application" unchecked for testing purposes, but I can't work out why I can't access the function once the object is created.
>
>Any help appreciated.
>
>Regards
>Darren