• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 245
  • Last Modified:

MSXML3 Error on Window 2003

I have a Windows 2003 SP 2 server with IIS 6.0 running in 32-bit mode. This the same type of server and configuration as two of my other Windows 2003 SP2 servers on which my test works, but this one server it does not work. I am convinced it is server specific with permissions around MSXML of some sort. I am just not sure what else to do. Below is a code example that works on ALL servers except this one.

I have a site configured in IIS named "test.com" which points to the directory "D:\Websites\Test". Within that directory I have two files: "index.asp" and "test.asp". The content of those files are shown below. Using a browser I then browse to "http://test.com".

The result of the page is show below. As you can see "Hello World" is displayed; however, when executing MSXML to go after the other content we get an error.

-- Result Page --

Hello World

msxml3.dll error '800c0005'

System error: -2146697211.

/index.asp, line 9


-- index.asp --

<% @ LANGUAGE = VBScript.Encode %>

<html>
<body>
<h1>Hello World</h1>
<%
set myXML = Server.CreateObject("MSXML2.XMLHTTP")
myxml.open "GET", "http://test.com/test.asp", false
myXML.send
Response.Write myXML.ResponseText
set myXML = Nothing
%>
</body>
</html>

-- test.asp --

<% @ LANGUAGE = VBScript.Encode %>

<h2>Hello World from ASP File</h2>
0
Bizzuka IT
Asked:
Bizzuka IT
  • 5
  • 5
1 Solution
 
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
I wonder if this could be the reason why

http://support.microsoft.com/kb/316451

can you try calling another server?
0
 
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
you may also want to consider the version you're using as version 3 is pretty old

http://support.microsoft.com/kb/269238
0
 
Bizzuka ITAuthor Commented:
@Big Monty
The first article is for ServerXMLHTTP and WinHTTP neither of which I am using. I know about this issue if using those.

Yes version 3 is pretty old but for Windows 2003 it is perfectly fine and as indicated, I have two other servers with exact same code and no issues.
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
i don't think it's a permissions issue as you're calling the same site that the original call is being made from. Have you tried un-registering and re-registering the dll for MSXML2.XMLHTTP (I'm not sure which dll it is off hand, I'm sure google will tell you)? you're not behind any kind of proxy and/or firewall on this new server, are you?
0
 
Bizzuka ITAuthor Commented:
@ Big Monty
No I am not behind a proxy on the server; however, the the server is behind the same firewall as the other servers which are working.

I will try to un-register and re-register the DLL once I find how to do that and will report back. Any more information you might have would be helpful.
0
 
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
i believe msxml3.dll is in %SystemDrive%\Windows\system32\

if I come up with any other ideas, I'll post them here
0
 
Scott Fell, EE MVEDeveloper & EE ModeratorCommented:
Some options that may help:

Make sure your test.asp is in a different folder than your index.asp.  
myxml.open "GET", "http://test.com/some_folder/test.asp", false

Open in new window


set myXML = Server.CreateObject("MSXML2.XMLHTTP.3.0")
0
 
Bizzuka ITAuthor Commented:
@Big Monty
I have re-registered the DLL and rebooted the machine and the problem remains

@Scott Fell
I have tried your suggestion and the problem remains
0
 
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
is the version of the dll the same version as your other working servers?
0
 
Bizzuka ITAuthor Commented:
Thanks everyone!!

The issue was that DNS Doctoring was not enabled for that server which was causing the error.
0
 
Bizzuka ITAuthor Commented:
I accepted my own solutions because it was indeed the issue. After doing additional research and discovering that DNS Doctoring was not enabled on that server we attempted to enable and re-execute the tests and all succeeded.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now