I suspect this is a problem related to a change in the BIRT libraries and I think there's a recent defect opened for it - SW00558353
If you're able to open the xls file in a text editor do you find that it's actually in xml format?
Yes, it's within XML format. is there a hotfix available for this issue ?
Not that I can see and, as the defect is still open, you'll need to open a support case if you need a fix sooner rather than later.
I have confirmed this behavior on our updated Mid Tier as well.
This has to be raised with BMC but I think this happens due to Excel security feature as it treats these reports are from unknown source and not safe to open.
You can try one thing, Once the report is downloaded,
Right click on the file and choose Properties
On the General tab, click Unblock
and try to open it now.
this doesnt work. The downloaded .xls file has 11MB which is a hell lot. Normally when I download the same data on our PROD machine (its still on v 8.1.02) it is around 1MB size. The .xls file when I open it within Notepadd++, it's a XML file. Not real Excel file.
Anyway, this is the general settings on the file. There is no option to Unblock or so.
Anyway, such workaround could not be usable, cause the XLS reports are created within our systems by too many support staff and also customers create their own reports. So once they run the report and want to export to XLS, it must work the same way as in v 8.1.
The workaround mentioned in my earlier post was just to check if this is happening because of Excel. Anyways, did you check below post?
Looks like JAVA_OPTS has some additional parameters. Can you try that as well?
Ganesh, that parameter mentioned in that Thread solved the 1st issue. This means, without that parameter, the report was not able to be generated. I've got a java error. After adding that JAVA_OPTS parameter, it started working to be able to export the results, but it reports everything DOC, XLS, PDF with XML format, so not Excel or Doc format, therefore the reports are not usable. Below, Jason has confirmed the same behaviour in their environment.
In that case, open ticket with BMC and keep us updated on the resolution.