So it seems to just be some kind of anomoly in the windows 2008.
Kevin
*************************************************************************
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
*************************************************************************
I was just about to send Rick an email to ask him for a phone call on this issue.
Another iisreset fixes it
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!