ODS Excel - Read Access Violation Program

[SergeLukas]

Greetings!

We're working on SAS server and recently encountered a weird issue. Our reports are written to Excel files using ODS EXCEL statement. All worked well for a while, but a couple of days ago it started crashing. When the program submits ODS EXCEL statement (with a valid FILE= destination) the log gets the message: "ERROR: An exception has been encountered" and then "ERROR: Read Access Violation Program" (see below). That happens to ODS EXCEL only, PROC EXPORT to Excel or ODS PDF/LISTING work fine. 

Is anyone familiar with that issue?

Thanks a lot!

 

 

[PaigeMiller]

Typically, when it says "Please contact technical support", that is what you should do.

[data_null__]

I'm guessing as you said it had worked and that you did not show log above, that you are out of memory.   Show entire log related to the PROC REPORT call.

I have had similar not related to memory but I was doing something crazy.  

[ballardw]

Proc Export and ODS Excel are entirely different beasts. Export moves data, that is all. ODS EXCEL has to deal with the data, table formatting of cells, merged cells, borders, images for procedure producing plots, and pagination (sheets in Excel).

As a minimum you should include the code that throws this error starting with the ODS Excel statement to the Ods Excel close. Better would be to include some example data.

Some of these exception errors happen when you use an option incorrectly or sometimes unexpected interaction of some options that the SAS developers never thought someone would use together. With the code we might have a chance of pointing to likely places such as many style overrides that possibly conflict.