ASP.NET Web Service Strange Behaviour...

Tags: Rants, Tech Geek

Wednesday, July 14, 2004 11:24:00 AM

So we have this Web Service in production, its not all that special; just handles thousands upon thousands of transactions per day.  Well I uploaded an assembly (after some extensive testing on a staging environment, of course) which was specific to a provider and is actually loaded in at runtime by .NET.  Think of it as a plug-in for the Web Service to make a call out to the 3rd party in real-time to handle a specific duty for the transaction.

Well for some reason, once I uploaded the assembly it broke the service.  We managed to pull some logs from the VB6 client and it states:

WSDLReader:XML Parser failed at linenumber 0, lineposition 0, reason is: The download of the specified resource has failed.  HRESULT=0x1: Incorrect function.  - WSDLReader:Loading of the WSDL file failed HRESULT=0x80070057: The parameter is incorrect.  - Client:One of the parameters supplied is invalid. HRESULT=0x80070057: The parameter is incorrect.

The reason for this error, it would appear, is that it could not download the WSDL from the ASMX; which means my ASP.NET 1.1 app could not generate it for some reason or another.

So, I immediately attempted to load up the ASMX in the local browser on the transaction server to reproduce the issue and get a more detailed description of the error.  It loaded up perfectly, and guess what?  That caused web service to behave normally from now on on the clients.

Nothing of use in any log (event, iis, etc..).  The only thing I have to go on is the error above, and the fact that by loading the ASMX up in IE fixed it.

Anyone have any ideas?  Have you seen this?  How on earth would I even begin to find out the cause?

 

2 Comments

Comments have been disabled for this content.