<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SAS stored Process Report download in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/SAS-stored-Process-Report-download/m-p/197102#M49242</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi:&lt;/P&gt;&lt;P&gt;&amp;nbsp; Generally, a stored process that you execute through the Information Delivery Portal has to have a special destination coded if the results are being sent to Excel instead of the browser. For help with this issue, Tech Support will be your best resource, they will need to look at the stored process code, particularly the destination that was coded. They will need to look for any references in the code to STPSRV_HEADER to make sure that it was coded correctly. Generally, you get an XML Parse error from any of the ODS destinations that generate XML. Your SAS log from the stored process should tell you which destination is being invoked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; If you are using TAGSETS.EXCELXP as the ODS destination, typically, you need to have an STPSRV_HEADER coded in your stored process that explicitly tells the Portal browser that you want to launch Excel when the stored process results come back. That type of XML parse error can sometimes be caused by not using an updated destination template on your server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Again, this is really something best worked on with Tech Support.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cynthia&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 01 Jun 2015 18:51:24 GMT</pubDate>
    <dc:creator>Cynthia_sas</dc:creator>
    <dc:date>2015-06-01T18:51:24Z</dc:date>
    <item>
      <title>SAS stored Process Report download</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SAS-stored-Process-Report-download/m-p/197101#M49241</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have had a problem with SAS stored Process download through SAS portal. When I try to download a report , it just download data worth 1KB and when I open the excel .xls report then It gives workbook error message as . &lt;/P&gt;&lt;P&gt;""Problem came up in the following area during load"&lt;/P&gt;&lt;P&gt;Workbook Setting&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error log : C:\users\xxx\appdata\Local\Microsoft\Windows\temporaryInternet files\Content.MSO\123445.log&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I access the above location for logs and can see the below message:&lt;/P&gt;&lt;P id="imcontent"&gt;&lt;SPAN style="font-family: 'Segoe UI'; color: #000000; font-size: 10pt;"&gt;XML PARSE ERROR: Missing end-tag&lt;BR /&gt;Error occurs at or below this element stack:&lt;BR /&gt;&amp;lt;ss:Workbook&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Segoe UI'; color: #000000; font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Segoe UI'; color: #000000; font-size: 10pt;"&gt;Can I please expect a help from SAS experts ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Segoe UI'; color: #000000; font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Segoe UI'; color: #000000; font-size: 10pt;"&gt;thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Segoe UI'; color: #000000; font-size: 10pt;"&gt;Ritesh&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Jun 2015 11:18:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SAS-stored-Process-Report-download/m-p/197101#M49241</guid>
      <dc:creator>riteshfrank</dc:creator>
      <dc:date>2015-06-01T11:18:10Z</dc:date>
    </item>
    <item>
      <title>Re: SAS stored Process Report download</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SAS-stored-Process-Report-download/m-p/197102#M49242</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi:&lt;/P&gt;&lt;P&gt;&amp;nbsp; Generally, a stored process that you execute through the Information Delivery Portal has to have a special destination coded if the results are being sent to Excel instead of the browser. For help with this issue, Tech Support will be your best resource, they will need to look at the stored process code, particularly the destination that was coded. They will need to look for any references in the code to STPSRV_HEADER to make sure that it was coded correctly. Generally, you get an XML Parse error from any of the ODS destinations that generate XML. Your SAS log from the stored process should tell you which destination is being invoked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; If you are using TAGSETS.EXCELXP as the ODS destination, typically, you need to have an STPSRV_HEADER coded in your stored process that explicitly tells the Portal browser that you want to launch Excel when the stored process results come back. That type of XML parse error can sometimes be caused by not using an updated destination template on your server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Again, this is really something best worked on with Tech Support.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cynthia&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Jun 2015 18:51:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SAS-stored-Process-Report-download/m-p/197102#M49242</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2015-06-01T18:51:24Z</dc:date>
    </item>
  </channel>
</rss>

