[Bug]: Clicking the Export tab results in error on Windows Server 2019 and IIS 10.0
Describe the bug
When I click on the "Export" tab for the whole server or for a schema, I encounter an error. The call to "https://[server:port]/index.php?route=/server/export" return a 200 status code but the response HTML is only "Error".I am not anything logged in the PHP error log or IIS log that illuminates the cause of this issue.
How to Reproduce
- Log into phpMyAdmin
- Click on Export
- The error is encountered
Expected behavior
I expect to be able to click on the export button so that I can export MySQL schemas.
Screenshots
No response
Operating System
Windows
Web Server
IIS 10.0
Database Server
MySQL
Database version
8.4.2
PHP version
8.2.28
phpMyAdmin version
5.2.2
browser
Firefox 128.8.0
Additional context
Prior to upgrading to phpMyAdmin 5.2.2, I was runing version 5.2.1+ snapshot from December 17, 2024. If I switch back to using this version, the error is not encountered and I am able to successfully export schemas. If update to use the latest 5.2 or 6.0 snapshot, I encounter the same error.
For clarity, here is the exact version of phpMyAdmin that I know works: 5.2.2-dev+20241216.4c8dadfdaa.
Database version 8.4.0
I have some doubts about this, are you sure ? Is this MySQL ?
Yes, MySQL 8.4.2.
I get the same issue on FreeBSD
Web Server Apache 2.4.63
Database Server MariaDB
Database version 10.6.8
PHP version 8.1.32
phpMyAdmin version 5.2.2
@tvanhill How did you upgrade the phpMyAdmin? It fails when accessing the URL directly, or only when clicking on Export?
@tvanhill How did you upgrade the phpMyAdmin? It fails when accessing the URL directly, or only when clicking on Export?
I don't have 5.2.2 setup at the moment, but I believe either way resulted in the error.
To upgrade, I performed the following steps:
- Extracted the phpMyAdmin zip file to a new directory.
- Copied the config.in.php file from the old installation to the new installation to get all the site specific parameters.
- Verified there were not any path specific values that needed to be updated (there weren't).
- Pointed the IIS site to the new phpMyAdmin location and restarted the site.
For clarity, here is the exact version of phpMyAdmin that I know works: 5.2.2-dev+20241216.4c8dadfdaa.
Just for reference: https://github.com/phpmyadmin/phpmyadmin/compare/4c8dadfdaa...RELEASE_5_2_2
I got the same issue on Debian 12
Server: **** via TCP/IP Server type: MariaDB Server version: 10.11.11-MariaDB-0+deb12u1 - Debian 12 Protocol version: 10 Server charset: UTF-8 Unicode (utf8mb4) Web server nginx/1.22.1 Database client version: libmysql - mysqlnd 8.2.28 PHP extension: mysqli Documentation mbstring Documentation sodium Documentation PHP version: 8.2.28
I've tried phpMyAdmin-5.2.2-all-languages and phpMyAdmin-5.2+snapshot-all-languages
downgrading to phpMyAdmin-5.2.1 solves this issue.
I got the same issue on Debian 12
For reference, did you also try the Debian package: phpmyadmin ?
Exactly the same error - clicking to 'Export' (server, database, table...) returns a page with the source code:
ErrorEverything else works...
Server: Localhost via UNIX socket Server type: MariaDB Server connection: SSL is not being used Documentation Server version: 10.11.11-MariaDB-0+deb12u1 - Debian 12 Protocol version: 10 User: root@localhost Server charset: UTF-8 Unicode (utf8mb4) Web server Apache/2.4.62 (Debian) Database client version: libmysql - mysqlnd 8.2.28 PHP extension: mysqli Documentation mbstring Documentation sodium Documentation PHP version: 8.2.28 phpMyAdmin Version information: 5.2.2 (up to date)
Manual installation (not Debian package)
Installing on a fresh Debian 12 system on 2 independent servers (same hardware) = same error
I got the same issue on Debian 12
For reference, did you also try the Debian package: phpmyadmin ?
I have not, debian stable is 5.2.1 which should work, I haven't tried sid 5.2.2 but is on my checklist, will let you know.
Same issue with:
- 10.11.13-MariaDB - FreeBSD Ports
- PHP version: 8.2.29 and 8.2.28
- phpMyAdmin version 5.2.2
5.2.1 downgrade solves the 200 Error problem.
I think this could be a duplicate of #19744. Can somebody update the lines from https://github.com/phpmyadmin/phpmyadmin/commit/baf4b407b381eb3518f9ada95516173b5db7741b (only the two lines from first file - libraries/classes/Plugins/Export/ExportPdf.php) and report back?
@liviuconcioiu I confirm that those 2 lines fix the export issue on 5.2.2