CreateObject with Server name

From: Vincent Finn (1_at_2.com)
Date: 07/21/04 

Date: Wed, 21 Jul 2004 14:28:24 +0100

Hi,

I an trying to call CreateObject with a server name from a VB.Net web
service.
The local version works the remote one fails
"Cannot create ActiveX Component"

The syntax is the same as I am using in a VB.Net app (which works,
i.e. the component is properly registered and working on the server
machine) so I assume the problem is because it is being called from
the web service

Do I need to give the ASPNet user special permissions for it to be
able to use DCOM remotely?

Everyone has Launch and Access permissions for DCOM on my machine and
the remote machine

Anyone seen this problem?

        Vin

Relevant Pages

  • Re: Remote Web Workplace - Desktop/Server ActiveX component problem
    ... I've tried it on too many different computers, ... It is something wrong with the server. ... >> the IE security settings are preventing the ActiveX component from ... >> Is there some other site that I can have my remote users access to ...
    (microsoft.public.windows.server.sbs)
  • Re: CreateObject with a server name
    ... > I an trying to call CreateObject with a server name from a VB.Net web ... > The local version works the remote one fails ... > Do I need to give the ASPNet user special permissions for it to be ... > the remote machine ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: CreateObject with a server name
    ... >> I an trying to call CreateObject with a server name from a VB.Net web ... >> The local version works the remote one fails ... >> Do I need to give the ASPNet user special permissions for it to be ...
    (microsoft.public.dotnet.framework.webservices)
  • CreateObject with a server name
    ... The local version works the remote one fails ... "Cannot create ActiveX Component" ... Do I need to give the ASPNet user special permissions for it to be ... the remote machine ...
    (microsoft.public.dotnet.framework.webservices)
  • CreateObject remotely as ASPNET user
    ... The local version works the remote one fails ... "Cannot create ActiveX Component" ... Do I need to give the ASPNet user special permissions for it to be ... the remote machine ...
    (microsoft.public.dotnet.languages.vb)