Getting error while downloading xlsx file

Bug reports
1

Hi,

I am getting error when trying to export an Excel file. The xlsx file exported is corrupted.

MicrosoftTeams-image (3)
MicrosoftTeams-image (3)846×134 3.99 KB

Please help us to resolve this issue asap.

1 Like
2

please post troubleshooting info

3

{
"browser-info": {
"language": "en-US",
"platform": "Win32",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36",
"vendor": "Google Inc."
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "Java(TM) SE Runtime Environment",
"java.runtime.version": "11.0.5+10-LTS",
"java.vendor": "Oracle Corporation",
"java.vendor.url": "http://java.oracle.com/",
"java.version": "11.0.5",
"java.vm.name": "Java HotSpot(TM) 64-Bit Server VM",
"java.vm.version": "11.0.5+10-LTS",
"os.name": "Linux",
"os.version": "3.10.0-1062.9.1.el7.x86_64",
"user.language": "en",
"user.timezone": "Asia/Kolkata"
},
"metabase-info": {
"databases": [
"sqlserver",
"postgres",
"mysql",
"oracle",
"h2"
],
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "11.8"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.5.4"
}
},
"run-mode": "prod",
"version": {
"date": "2023-09-07",
"tag": "v0.47.1",
"branch": "release-x.47.x",
"hash": "bd278b9"
},
"settings": {
"report-timezone": "Asia/Calcutta"
}
}
}

4

Any luck solving this ? I'm having the exact same issue with the excel downloads since upgrading to v0.46.6.1

5

if the problem is that the file takes a lot of time and then it fails, we made a patch on 47.4

6

I'm frequently having hte same problem on v1.47.4. Normally it happens with tables with many rows/columns

7

Has there been any feedback on issues with exporting excel files that end in beiing corrupted?
My customer is on version 0.49.3 and still has the issue now and then.
Only solution is to restart the java application.
I've had the issue with this customer on different versions of Metabase where I initialy thought the update fixed it, but it was probably just the restart.

8

What is the error message that you are seeing?