?
Solved

MSXML3 Error on Window 2003

Posted on 2014-12-10
11
Medium Priority
?
222 Views
Last Modified: 2015-01-26
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
Comment
Question by:Bizzuka IT
  • 5
  • 5
11 Comments
 
LVL 34

Expert Comment

by:Big Monty
ID: 40491422
I wonder if this could be the reason why

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

can you try calling another server?
0
 
LVL 34

Expert Comment

by:Big Monty
ID: 40491429
you may also want to consider the version you're using as version 3 is pretty old

http://support.microsoft.com/kb/269238
0
 

Author Comment

by:Bizzuka IT
ID: 40491450
@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
Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

 
LVL 34

Expert Comment

by:Big Monty
ID: 40491481
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
 

Author Comment

by:Bizzuka IT
ID: 40491506
@ 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
 
LVL 34

Expert Comment

by:Big Monty
ID: 40491519
i believe msxml3.dll is in %SystemDrive%\Windows\system32\

if I come up with any other ideas, I'll post them here
0
 
LVL 54

Expert Comment

by:Scott Fell, EE MVE
ID: 40491521
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
 

Author Comment

by:Bizzuka IT
ID: 40491675
@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
 
LVL 34

Expert Comment

by:Big Monty
ID: 40491680
is the version of the dll the same version as your other working servers?
0
 

Accepted Solution

by:
Bizzuka IT earned 0 total points
ID: 40562110
Thanks everyone!!

The issue was that DNS Doctoring was not enabled for that server which was causing the error.
0
 

Author Closing Comment

by:Bizzuka IT
ID: 40570210
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

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Running classic asp applications under Windows Server 2008 R2 (x64) and IIS 7 is not as easy as one may think. It took me a while to figure it out while getting error 8002801d a few times. After you install the OS you will need to install the fol…
If you don't have the right permissions set for your WordPress location in IIS, you won't be able to perform automatic updates. Here's how to fix the problem.
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…

831 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question