Soap and XML fun
Posted on May 4, 2007
2 Comments
Writing this up as the result of a nudge from our CIO: We had the situation described below and didn't find a whole lot as we searched the web for tips. So, next time this happens to someone, maybe this'll help.
While making web service call from one of our (classic ASP) web applications, we received this message:
-
Server:XML Parser failed at linenumber 44889, lineposition 73, reason is:
-
Not enough storage is available to complete this operation.
-
HRESULT=0x80004005: Unspecified error - Client:Loading the request into SoapReader failed.
-
HRESULT=0x80070057: The parameter is incorrect. - Client:Unspecified client error.
-
HRESULT=0x80070057: The parameter is incorrect.
The chunk of data the web service was sending was a bit larger than normal. Maybe around 5MB?
After some stumbling around, we came to the conclusion that something was "off" with our SOAP toolkit or the XML processor (yes, call us Captains of Obvious! Once I remembered to check the server's event viewer, MSSOAP was right there). To keep it interesting, this worked on a dev server, but not our production server.
While I was trying to determine exactly what versions of SOAP and XML we had, I decided to pop over to Windows Update and see if I was missing anything. Lo and behold, I found an optional MSXML Core Services 6 Service Pack 1. Neither server had it installed, but our Dev server has a ton of assorted xml toolkits, toys and utilities so it may have go the updates via another vector.
I found it interesting that after the install, the dev server wanted a reboot. The production server didn't.
Regardless, the service pack fixed us up. All good now!
Tags: ASP, error, server, service-pack, soap, xml
Possibly Related Posts
Comments
2 Responses to “Soap and XML fun”
Leave a Reply
With new theme your text box is fixed width and that fixed width is bigger than the column so it runs over into the sidebar.
I imagine you’ve noticed already.
Nicely done on the link colors BTW.
Hmm, I thought I’d fixed that. You’re talking about the “code” box, right? Be sure to refresh your cache, as the fix was CSS related.