topic Re: xlsx file: error message when opening the file in ODS and Base Reporting

xlsx file: error message when opening the file

xxformat_com — Sat, 17 Nov 2018 22:38:33 GMT

I'm creating an Excel file with ods Excel. I don't have any warning, error or critical note in the log.

But when I open it, I get error messages: see pictures as attached files.

When I try to open the log listing repairs I see:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"><logFileName>error153160_01.xml</logFileName><summary>Errors were detected in file 'C:\Users\xxformat\Documents\SASUniversityEdition\myfolders\client\ruiz\result\20181113\201811_.xlsx'</summary><repairedRecords><repairedRecord>Repaired Records: Cell information from /xl/worksheets/sheet1.xml part</repairedRecord></repairedRecords></recoveryLog>

Have you already experienced something similar?

Best Regards,

I'm using

9.04.01M5P091317) SAS Studio 3.7 on Windows 10.

Re: xlsx file: error message when opening the file

Tom — Sun, 18 Nov 2018 00:18:31 GMT

Show the code that actually made the file or better the log.

Usually I have seen errors when trying to open Excel files it is because the ODS statements ran but the step that was supposed to make the actual data never ran.

Re: xlsx file: error message when opening the file

Reeza — Sun, 18 Nov 2018 00:43:03 GMT

I’ve seen this and it’s a bad error. It usually means you made a mistake in the code somewhere.

Re: xlsx file: error message when opening the file

Cynthia_sas — Sun, 18 Nov 2018 14:56:26 GMT

Hi:
Most of the time when I've gotten this error, it's because I am using ODS style= overrides and I've made a mistake in specifying something incorrectly, so the generated XML is bad. Seeing the exact code you ran and your log messages will be the most helpful.
Cynthia

Re: xlsx file: error message when opening the file

xxformat_com — Wed, 21 Nov 2018 10:14:39 GMT

Hi, Thanks for your feedback. In the end I had to change my data selection to be displayed in the Excel file to meet my client needs and don't get anymore the message. So I can only see 2 reasons for the issue : 1/ too many records in the dataset created with proc sql 2/ specific values in the data which could cause the problem.