Quantcast
Channel: West Wind Message Board Messages
Viewing all articles
Browse latest Browse all 10393

Re: Class definition MSXML2.DOMDOCUMENT is not found

$
0
0
Re: Class definition MSXML2.DOMDOCUMENT is not found
Web Connection
Re: Class definition MSXML2.DOMDOCUMENT is not found
Jan. 10, 2013
11:45 am
3OT0P6SZCShow this entire thread in new window
Gratar Image based on email address
From:Kevin Emmrich
To:MB
I did a search and found this (yes, the error in the below blog did show up somewhere in the context of the MSXML2 error):

Also, this is probably the cause of that Class definition MSXML2.DOMDOCUMENT is not found error (and maybe the Class definition EXCEL.APPLICATION is not found error, too):

http://blogs.msdn.com/b/distributedservices/archive/2009/11/06/a-com-server-application-may-stop-working-on-windows-server-2008.aspx

You might want to pass this along to the windows team and see if it worthwhile to make the suggested change or just deal with it when it happens.

So it seems to just be some kind of anomoly in the windows 2008.

Kevin

*************************************************************************


Did you ever figure this out? We have the same issue happening on 'some' 2008 servers. We cannot force it to happen. It just happens and then an app pool reset usually cures it (or an iisreset).

I was just about to send Rick an email to ask him for a phone call on this issue.


I am following along to see what becomes of all this. I have noticed that if I run an update programs and run iisreset while folks are active, then that error "Class definition MSXML2.DOMDOCUMENT is not found" pops up sometimes -- even though I have "#DEFINE XML_XMLDOM_PROGID "MSXML2.DOMDocument.6.0" in the wconnect.h file. Pretty weird.

Another iisreset fixes it



Okay, the plot continues to thicken. I'm also getting the same behavior I described below when I try to use a Scripting.FileSystemObject instance to move files between folders. The error message I receive is, "Class definition SCRIPTING.FILESYSTEMOBJECT is not found."

Just like the MSXML2.DomDocument errors I described below, the error does NOT occur until after the server instances have been loaded and running for awhile. Then, at some point the errors start occurring and continue to occur until the servers are reloaded. So, it's like something is occurring to suddenly disable the ability to create instances of either MSXML2.DomDocument or Scripting.FileSystemObject.

I should probably also mention that initially I had to register the Scripting.FileSystemObject (with "regsvr32 scrrun.dll") on the server before I could use it. After doing that I seemed to have some rights issues that seemed to be solved with an update of the security for those folders. However, this could have been coincidental with the way the failures don't occur until a while after the server's have reloaded.

C'mon, guys! I need help here. The client's getting frustrated and impatient and I'm out of ideas. Help!



Viewing all articles
Browse latest Browse all 10393

Trending Articles