I have a customer unable to export to Excel. When they click the button to export the progress dialog displays, and then closes really quickly without doing anything else.

The following was in the %ATE%\ashlog.log
Not sure if this problem lies in A-Shell, or the PRTXLS perl script. Nothing related to perl has changed on this server for a very long time.

Hi Stephen,
Have you checked if Excel, by itself, is working fine?
Recently, in a customer, Excel wasn't able to open "normal" xls files when double-clicking the file (it was displaying a blank sheet) but, was ok if open the file from inside Excel, it was very weird and to fix that, I had to reinstall Excel.

I take the chance to wish everybody an absolutely GREAT 2016

They're actually using LibreOffice, but they are able to open documents without any problems.

Thanks for the suggestion, and wish you (and everyone) a great 2016.

Happy New Year to all -

The error message "...broken parent chain..." indicates some kind of corruption in the AUI table of controls. In this case, there seems to be only one control (probably the progress dialog itself), and yet it's parent control id is #5999, which is way out of bounds. Assuming this is ATE, it would be normal not to have any other GUI controls defined, since in the ATE case, APEX runs in a separate session, and although it is a GUI window, it doesn't use any of the AUI controls.

So I'm not sure what's special here.

Possible ideas for workarounds or further investigation:

1. Try updating your PRTXLS.SBX 1.1(175)

2. Try activating debug mode. (Check the "Debug" box in the Settings > Connection Properties > Printer dialog.) This will output a slew of messages to the ATE debug message window and local ashlog.log file which might help clarify something.

Well the user miss reported this. It wasn't that the export was actually failing, but that the data in the report wasn't getting exported. All that makes it into the spreadsheet is a customer header line.

I just released ATE 6.2.1422.5, upgrading from 6.1.1419.0, yesterday for this customer. I confirmed that this user exported the same report Monday afternoon and it was exporting the data. I'm guessing something in the improvements to PRTXLS are responsible for this.

I can get you a recipe for how to reproduce this if necessary, or just the report print file.

It's quite possible the "improvements" in PRTXLS are responsible. I don't suppose you know what version you had previously? (If so, I could probably retrieve a copy for the short term fix.)

But in any case, yes, please send me the report file and I should be able to reproduce/fix it here.

I have my release ATE directory under version control, so I have access to the previous version of PRTXLS that was in use.

I've emailed you a report file.

FYI, the problem was introduced in either 1.0(164) or 1.0(165). I should have a fix by tomorrow.

I believe it is fixed in PRTXLS.SBX 1.1(176)

From what I can tell it fixes it. I'll check with the customer in the morning.

Thank you, Jack

What?! The customer mis-reported something?!

Rule number #1 - never believe the end user!