An update on the issue:
I've built an ActiveX DLL (RemSvrInt.dll) that references MSXML3.dll internally.
When I built an Standard Exe test harness to test my RemSvrInt.dll and deployed
it onto my NT Server box it ran OK. I was able to create an MSXML2.XMLHTTP30
object and call the send method posting a string to it. (It failed a few

Afterwards, I took my RemSvrInt.dll and referenced from another ActiveX DLL
that is created by IIS. When a call was made to my RemSvrInt.dll it failed
on the MSXML.XMLHTTP30.send( ) method reporting Method "~" of object "~"
failed. Being ActiveX dll they are running in the IIS server process which
it doesn't seem to like one bit.

1: Server 2 Server calls work sporadically
2: The send method of MSXML.XMLHTTP30 does not function inside of an IIS
process (btw - this is on a client machine which is using PWS and doesn't
have NT Server security!)

Anyone have any thoughts?


"Paul" <> wrote:
>I have installed an application on my server and was calling another server
>and sometimes it stalled on the send (there could be other reasons) but

>following link explains its limitations(just in case you weren't aware).
>I haven't benchedmarked the behaviour of it yet (It does work sporadically).
>I'm using this call inside an activeX dll - apartment threaded.
>Also when you say WININET does support server to server, what do you mean?
>The following link states that the Win32 Internet functions do not support
>server implementations and should not be used from a service.
>As an aside. Did you have problems installing the MSXML3 on your machine.
>When I downloaded it and ran the install alongside previous version .exe
>which allows it to run with previous versions(I had msxml v1) the entries
>it placed in the registry and the progIDs seemed different. In VB when I
>set myObjHttp = new MSXML2.XMLHTTP30 it worked fine.
>When I was building a dll I replaced new with CreateObject, it failed as
>the registry had the prog_id as MSXML2.XMLHTTP.3.0? Is there a reason/explanation
>for this?
>I'm looking at programming sockets for the request which I was hoping to
>avoid....(hands dirty time !)
>Thanks for your reply..
>"John Timney (MVP)" <> wrote:
>>Ive never had any problems getting the xml http object to work for server

>>server communications. You need a reference to MSXML2.XMLHTTP.3.0 if your
>>using it from VB (off the cuff guess so I could have a number out) - the
>>object is free threaded so should be suitable for VB. Alternatively

> you
>>can use good old apartment threading with a reference to
>>MSXML2.DOMDocument.3.0 from VB and it should still work. I do not believe
>>the object uses wiinet at all so you should have no problems.
>>Although the wiinet api does supprt server to server, you can not
>>efficiently use winnet api from vb as you seem to be aware unless its a

>>client not a dll from asp due to threading problems with vb, if you cant

>>a third party compnent then use a socket to the remote servers port 80

>>issue http commands direct to the port, or use java if you know the
>>John Timney
>>Microsoft MVP
>>Co-Author Professional JSP
>>ISBN: 1-861003-62-5
>>Paul <> wrote in message news:39b3777a$
>>> I'm trying to send a http request server to server. All I want to do

>>> to an ASP page, get a response back and do some action based on the

>>> Its looking pretty grim at the minute. I've tried 2 approaches.
>>> 1. Using the MSXML object but this doesn't support server 2 server and

>>> on the httprequest.send( ) method
>>> 2. The WININET API which also doesn't support server 2 server
>>> FYI - the MSXML.HTTP object uses WININET so I guess this is the reason

>>> its limitations.
>>> I'm using VB6.
>>> Can anyone point me in another direction.
>>> I need to get this done ASAP
>>> Thanks
>>> Paul