Solved

MSXML3 Error on Window 2003

Posted on 2014-12-10
11
169 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 32

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 32

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
 
LVL 32

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
Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

 
LVL 32

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 52

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 32

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

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Scenerio: You have a server running Server 2003 and have applied a retail pack of Terminal Server Licenses.  You want to change servers or your server has crashed and you need to reapply the Terminal Server Licenses. When you enter the 16-digit lic…
Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
This video discusses moving either the default database or any database to a new volume.
Illustrator's Shape Builder tool will let you combine shapes visually and interactively. This video shows the Mac version, but the tool works the same way in Windows. To follow along with this video, you can draw your own shapes or download the file…

708 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

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now