Peter,
The webserver isn't trying to access a COM object on another machine.
Just to make sure I watched the ports being accessed using Systernals
TCP View, and the webserver app never made any calls to a remote
endpoint, only loopbacks. (note: the Windows Firewall service is
disabled, but is getting an ipnat.sys error when you attempt to open it
thru control panel)
Right now I am just trying to get the client & server running on the
same server. However, when I attempt to access the client app setup
file (this request is what should create the COM object) from the web,
it errors out. So, right now there are no other machines that connect
to the server, or are being connected to. This is completely
standalone. This server in question is running Windows Server 2003 SP1
Standard, is not joined to a domain, it is on a workgroup.
I did change the Access, and the Launch and Activation permissions using
dcomcnfg to explicitly allow the NETWORK SERVICE user, and this made no
difference. I still recieved the error.
I was able to install the software on another PC on the workgroup
without any issues whatsoever, and without having to change any
permissions or anything, which would lead me to believe there is
something wrong with the Component Services on the machine that is
getting the errors.
Thanks
Chris
Peter Huang [MSFT] wrote:
> Hi
>
[quoted text clipped - 15 lines]
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no rights.
"Peter Huang" [MSFT] - 10 Dec 2005 04:36 GMT
Hi
Based on your description so far, I understand that your WebServer will
call a COM object and that is what cause the error.
The COM object is located on the localmachine in a COM+ service.
If you install the WebServer and COM object on another machine, all works
fine.
If I misunderstood, please describe your scenario more detailed.
So far we can try to make a simple VB6 com dll and install into the com+ on
the problem machine to see if that works. So that we can make sure the COM+
service working well.
If that is true, we may try reinstall the COM Object in COM+ to see if that
works.
or, delete the COM Object from the COM+, that is to say call the COM Dll
from webserver directly to see if that works.
Also please check the eventlog to see if there is any security denied event.
Please perform the test and let me know the result.
Best regards,
Peter Huang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.