• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

database export broken

SteveHeflin

New Pleskian
Sometime after March 3rd 2016, a PSA update to version 12.5 broke the database export via phpMyAdmin. I see in another thread that somebody fixed it, but it didn't say how! Please reply with instructions on how to fix this latest update blunder.
 
Could you please be more specific? What exactly is broken? How it can be reproduced?
 
Further testing shows that failure is caused by attempting to change the "format-specific options". Select Export Method of Custom and output to a file, then uncheck the "Display comments" option, or, uncheck the "Enclose table and column names with backquotes" option. Either one of those changes will cause the output error. When the GO button is pressed, the output file will contain:
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET time_zone = "+00:00";

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;

<script></script><p>ERROR: Class 'Context' not found (ExportSql.class.php:1557)<br><br><a href='http://kb.odin.com/plesk-error/sear...rror&version=12.5.30&message=Class++not+found' target='_blank'>Search for related Knowledge Base articles</a></p>
 
Same problem.
We can not export DB with uncheck the "Enclose table and column names with backquotes" option.
If the option check, the export is not correct. Lot of errors with quotes.... We can not import Export DB in another DB.
 
I don't know if it's the same problem but we can not updated Plesk (12.5).
We have this message :

' Warning: XML answer is already sent (try to send '
' Warning: XML answer is already sent (try to send '
' Warning: XML answer is already sent (try to send '
' Warning: XML answer is already sent (try to send '
' Warning: XML answer is already sent (try to send '
...
 
There is bug with export/import in the current version of phpmyadmin. This issue has been discussed here many times. We are going to update phpmyadmin to latest 4.6.0 version in the one of nearest microupdates. You can use own Plesk database import/export feature instead of phpmyadmin.
 
Back
Top