800A01FB An_exception_occurred:_'xml.URL'

We have recently migrated a legacy ASP application from an NT4 server running IIS 4.0 to a Win2003 server running IIS6.0.

An Anonymous User account is being used to access a file server via IIS, retrieve the file, then a Java class is being used to uncompress the file before presenting it to the users desktop.

We are intermittently getting this 800A01FB error in the IIS logs.

This function will work 4 or 5 times with success reports (200 0) in the IIS logs but then it will fail with the above error and the function will hang. Restarting IIS seems to resolve the issue but then it will fail again eventually.

Has anybody come across this before? What does the xml.URL mean in the error? Any help appreciated. Thanks.

Would this have anything to do with the number of connections allowed on to the Win2003 server?

re: 800A01FB An_exception_occurred:_'xml.URL'

Unfortunately, you're going to have to do some error-trapping and log the data that causes the error to occur. You have little chance of solving the problem if
you cannot cause it to occur reliably. I am confident that it is not an IIS problem.

re: 800A01FB An_exception_occurred:_'xml.URL'

Ok, after putting is some error trappings I have managed to get some more details in the IIS log. This is the last line which appears in the log:

2007-08-01 11:39:04
POST ../Custom/FileShortcuts/GetFileShortcut.asp Open+START+http://pxp-wi0-flweb02/frontlinecheck/custom/fileshortcuts/xml_fileoperations.asp?
Action=jsDoesFileExist&FileName=\\pxp-wi0-fs2v3\filename.txt
+END+|196|800a01fb|An_exception_occurred:_'sURL.UR L' 80 pxp-wi0-flweb02 500 0 0

Everything between the START and END tags is what is being passed in the xml.URL property. If you copy and paste this into IE6.0 the function works ok and it calles the procudure jsDoesFileExist without error. But when running through the app I get the EXCEPTION OCCURRED error.

Also, this works ok half a dozen times in the application and only after this do we get the error. Could it be a memory issue on the server? Any other suggestions greatly received.