Your SAS programs, embedded in web apps and elsewhere

XML parsing and I/O errors

Posts: 0

XML parsing and I/O errors

I've put together several test stored processes running over XMLA and they seem to be working fine, but when I try to execute my final stored process with a large XML document I get the following types of errors in the logs:

2010-04-23T16:54:27,934 INFO [00014912] 558:webanon@saspw - ERROR: Undetermined I/O failure.
2010-04-23T16:54:27,934 INFO [00014912] 558:webanon@saspw - occurred at or near line 1, column 1
2010-04-23T16:54:27,934 INFO [00014912] 558:webanon@saspw - ERROR: XML parsing error. Please verify that the XML content is well-formed.
2010-04-23T16:54:27,934 INFO [00014912] 558:webanon@saspw - NOTE: The DATA step has been abnormally terminated.
2010-04-23T16:54:27,934 INFO [00014912] 558:webanon@saspw - NOTE: The SAS System stopped processing this step because of errors.
2010-04-23T16:54:27,934 INFO [00014912] 558:webanon@saspw - NOTE: SAS set option OBS=0 and will continue to check statements. This may cause NOTE: No observations in data set.

This happens the first time I try to use the mapped table in a data step. On the other hand a proc print on the same mapped table works fine:

2010-04-23T16:54:27,934 INFO [00014912] 558:webanon@saspw - 48 +proc print data=IN_XML.drivers;
2010-04-23T16:54:27,934 INFO [00014912] 558:webanon@saspw - 49 +run;
2010-04-23T16:54:27,934 INFO [00014912] 558:webanon@saspw -
2010-04-23T16:54:27,934 INFO [00014912] 558:webanon@saspw - NOTE: Access by observation number not available. Observation numbers will be counted by PROC PRINT.
2010-04-23T16:54:27,934 INFO [00014912] 558:webanon@saspw - NOTE: There were 1 observations read from the data set ACORDXML.drivers.
2010-04-23T16:54:27,934 INFO [00014912] 558:webanon@saspw - NOTE: The PROCEDURE PRINT printed page 1.

So, the questions:

1) What would cause the I/O error? It's not on this specific mapped table. I can try to access any one of my 7 mapped tables and I will get the same error so order is not important.

2) Are there any other BI logs which might give me more information? I'm currently looking in the STPServer logs for the errors.

3) Is there a limit to the size of the XML documents which can be sent over XMLA? The full SOAP request to the server is 24K total.

I've run a test where I post the XML via the XMLA SOAP interface and then rather than reading the stream I read a copy of the data from the filesystem using a fileref and that works without any problems at all. That's what's really hanging me up.

Any thoughts or suggestions?
Posts: 8,745

Re: XML parsing and I/O errors

I think this question might better be answered by Tech Support. They can examine the XML document and attempt to replicate the error in a similar environment to yours, using similar code.

To send a question to Tech Support, go to and in the left-hand navigation pane, click on the link entitled "Submit a Problem". Alternately, you can go directly to the Tech Support Problem Form here:

Posts: 0

Re: XML parsing and I/O errors

Thanks Cynthia. I figured since I ran them a bit ragged this week I would try the forums first Smiley Happy

I'll put in a ticket Monday morning and hopefully we can get this resolved.
Posts: 0

Re: XML parsing and I/O errors

Just to follow up my own issue with the solution support was able to give:

When creating your stored process, even when using an XMLMap you need to check the "Allow rewinding stream" option on the input XML. Even though an XMLMap is used it seems that you need to have the rewind on if you plan on processing multiple tables out of the map.

Hopefully this will save others some time if you run into the same problems.
Ask a Question
Discussion stats
  • 3 replies
  • 2 in conversation