Server object error 'ASP 0177 : 800401f3'

I am developing my new photography website, but I'm sporadically getting this error while in my XML/ASP driven galleries section:

Server object error 'ASP 0177 : 800401f3'
Server.CreateObject Failed
/NewSite/Weddings.asp, line 106
800401f3

This appears to be the offending code:

Set objWeddingsXML = Server.CreateObject("Msxml2.FreeThreadedDOMDocument.4.0")
objWeddingsXML.async = False
objWeddingsXML.Load(Server.MapPath("photosxml.xml"))

I later set this object to nothing. Apparently my host doesn't support the use of the .dispose() or .close() methods.

I don't understand why the error is only sporadic. I would think that it should either work or not work at all.

Should I be creating a different object? While I develop frequently in ASP, I'm new to XML.

I hope I put this in right forum.

 

Can you confirm with your host that component is installed on the server.

 

Yep, I asked them that. They say it is...

 

perhaps since it only happens sporadically, testing objWeddingsXML before the CreateObject might help if an old one is still hanging around.

If Not objWeddingsXML Is Nothing Then
	Set objWeddingsXML = Nothing 
End If

Code (markup):

 

Man! I thought you had it there for a while. Your idea seemed to work...for about 10 minutes, then I got the error again.

 

I wonder if it is an old version of the component. try running the checker on your site to see what version it is...
http://www.pensaworks.com/prg_com.asp

I believe the latest version is 4.20.9839.0

 

These are the only XML components it detected:
1 XML Installed Microsoft ServerXMLHTTP
2 XML Installed Microsoft XMLDOM Component
3 XML Installed Microsoft XMLHTTP Component
4 XML Installed Microsoft XMLDOM 3.0 Component

No mention of the Msxml2.FreeThreadedDOMDocument.4.0 COM.

 

I would expect that Microsoft XMLDOM 4.0 Component should be installed. what is really odd is that you are able to create the object 'sometimes'.

 

Well, I just noticed something quite interesting. That component tester that you suggested listed it as not installed, but then a few minutes later it listed it as installed. Not surprisingly, when it was listed as NOT installed, my website didn't work, and when it was listed as installed, it worked.

I've emailed my host to tell them all this...I wonder what they'll say? They've been insinuating that my code is somehow faulty.

 

Oh! And when it is listed as installed it says it's version 4.0.9406.0

 

That is an old version SP1 or earlier. The current version can be found here...

http://www.microsoft.com/downloads/details.aspx?familyid=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en

hopefully once your host updates the machine, it will stabilize your script. since your appears to be pointing the finger at you, I doubt they will check the server logs for an Event ID to diagnose it further

 

I'm just glad to be getting to the bottom of this. I've been banging my head on a brick wall for days on this!

Thanks for all your help. It's greatly appreciated.

I'll let you know what they say.

 

They got back to me and said that they didn't have MSXMLDOM 4.0 installed on one of their servers and this is what was throwing the error.

Mystery solved.

 

That will do it they must have the servers clustered at your host. glad to see it is all sorted now.