在ASP页MSXML3.DLL错误“80072EE2” [英] msxml3.dll error '80072ee2' in ASP Page

问题描述

我们刚刚搬进了Windows 2008，我想用同一台服务器上访问ASP页一个新的专用服务器和SQL Server 2008 的Server.CreateObject（MSXML2.ServerXMLHTTP） 。

We have just moved to a new dedicated server that has Windows 2008 and SQL Server 2008. I am trying to access an ASP page on the same server using Server.CreateObject("MSXML2.ServerXMLHTTP").

在我们的previous 2003服务器这个工作正常，但与2008年新的服务器运行只是超时。

On our previous 2003 server this worked correctly, however with the new 2008 server the operation just times out.

下面是code：

strURL = "http://www.storeboard.com/profile/profile_view.asp?MemberID=" & MemberID & "&sid=" & cSession.SessionID
Set oXMLHttp = Server.CreateObject("MSXML2.ServerXMLHTTP")
oXMLHttp.open "GET", strURL, false
oXMLHttp.send()
IF oXMLHttp.status = 200 THEN 
  strOut = oXMLHttp.responseText
ELSE
  strOut  = "Could not get XML data."
END IF
Set oXMLHttp = nothing

在code是非常简单，但我得到以下错误：

The code is very simple but I get the following error:

msxml3.dll error '80072ee2'

The operation timed out

/handle404.asp, line 291 

291线是指oXMLHttp.Send（）行。

Line 291 refers to oXMLHttp.Send() line.

是否有其他code可以使用吗？我使用服务器上的其他服务器上访问文件脚本其他地方，他们正常工作，但对文件的任何访问我们的服务器无法正常工作。

Is there an alternative code I can use? I use the script other places on the server that access files on other servers and they work correctly, but any access to files on our server doesn't work.

是否有其他方法，让我保持网址在浏览器中完好无损？这个人可以写的URL在浏览器： http://www.example.com/hello 文件不存在，但我有一个404处理器的再分用户的正确路径不改变浏览器的URL这是我们的SEO评级是必不可少的。

Is there an alternative method that will allow me to keep the URL intact in the browser? The person could write the URL in their browser: http://www.example.com/hello the file doesn't exist but I have a 404 handler that then points the user to the correct path without changing the browser URL which is essential for our SEO ratings.

推荐答案

微软一发表了一篇题为信息知识库文章：不要发送ServerXMLHTTP的或WinHTTP的请求到同一台服务器

Microsoft has a published a KB article entitled INFO: Do Not Send ServerXMLHTTP or WinHTTP Requests to the Same Server

如果该ServerXMLHTTP的或WinHTTP的组件必须发送到请求
  另一个ASP在同一服务器上，目标ASP必须位于一个
  不同的虚拟目录，并设置为高隔离运行。避免
  使用ServerXMLHTTP或WinHTTP的发送到ASP是一个请求
  位于同一虚拟目录。

If the ServerXMLHTTP or WinHTTP component must send a request to another ASP on the same server, the target ASP must be located in a different virtual directory and set to run in high isolation. Avoid using ServerXMLHTTP or WinHTTP to send a request to an ASP that is located in the same virtual directory.

...

一个有限数量的工作线程（在Inetinfo.exe或Dllhost.exe
  过程）是可用于执行ASP页。如果所有的ASP工人
  线程发送HTTP请求回到同一Inetinfo.exe中或
  在服务器上dllhost.exe进程从其中请求被发送，
  在Inetinfo.exe或Dllhost.exe过程可能会死锁或停止
  响应（挂起），因为工作线程池来处理
  传入的​​请求将被耗尽。这是由设计。

A finite number of worker threads (in the Inetinfo.exe or Dllhost.exe process) is available to execute ASP pages. If all of the ASP worker threads send HTTP requests back to the same Inetinfo.exe or Dllhost.exe process on the server from which the requests are sent, the Inetinfo.exe or Dllhost.exe process may deadlock or stop responding (hang), because the pool of worker threads to process the incoming requests will be exhausted. This is by design.

至于去替代，这取决于您收到后，你的反应做什么。如果脚本的整个目的是转发到profile_view.asp的要求，你也许可以使用<一个href=\"http://msdn.microsoft.com/en-us/library/ms525800%28VS.90%29.aspx\"><$c$c>Server.Transfer来代替。

As far as alternatives go, it depends on what you're doing with the response after you receive it. If the entire purpose of the script is to forward the request to profile_view.asp, you might be able to use Server.Transfer instead.

这篇关于在ASP页MSXML3.DLL错误“80072EE2”的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！