iis 6 - same server, get url: vbscript msxml3.dll 80004005 unspecified error, or msxml6.dll error '80072ee6' System error: -2147012890 -


what's correct way output of asp page located on same server?

<%  geturl "/route/to/abc/123/"  function geturl(url)     set objxmlhttp = createobject("msxml2.serverxmlhttp.3.0")     objxmlhttp.open "get", url, false     objxmlhttp.send()     if objxmlhttp.status = 200         response.write objxmlhttp.responsetext     end if     set objxmlhttp = nothing end function  %> 

results in pesky error.

msxml3.dll error '80004005' unspecified error /test.asp, line 7 

switching newer serverxmlhttp

set objxmlhttp = server.createobject("msxml2.serverxmlhttp.6.0") 

reveals different, more meaningful error:

msxml6.dll error '80072ee6' system error: -2147012890. /test.asp, line 8 

which google happily found reason to, says "don't use serverxmlhttp connect same server. (https://support.microsoft.com/en-us/kb/316451) use? article didn't offer much.

anyway cool, there's proper reason error. use connect same server, under classic asp, capture output of pages? article (https://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/iis/aa23d158-000a-4ba2-8fe8-99895854d7f0.mspx?mfr=true) mentions if i'm doing isolation mode, process runs seperate web server process , there can't use ssi, can't figure out how enable in first place anyway. sounds nasty anyway. ssi critical in app, can't consider it.

what left (besides obvious: ditch asp)? spawn wscript.shell command prompt , pull there, echoing stdout? bounce off reflector server? grr

you cannot request web page web site running under the same application pool.

a finite number of worker threads (in inetinfo.exe or dllhost.exe process) available execute asp pages. if of asp worker threads send http requests same inetinfo.exe or dllhost.exe process on server requests sent, inetinfo.exe or dllhost.exe process may deadlock or stop responding (hang), because pool of worker threads process incoming requests exhausted. design.

if single recursive request causes iis deadlock, typical cause asp script debugging enabled.

solution: create new folder, put script inside folder. after in iis create new application pool , create new application folder.

how create new application folder: enter image description here

sample when folder assigned new application pool: enter image description here

note: not try 3rd part dll's download web page same application pool. result same. tested free http component.


Comments

Popular posts from this blog

c# - Validate object ID from GET to POST -

node.js - Custom Model Validator SailsJS -

php - Find a regex to take part of Email -