Database errors are quite annoying especially in the middle of a database update.

One such problem is phpMyAdmin error code 200 when modifying the databases.

At Bobcares, we help server owners resolve these database errors as part of our Server Management Services.

Today, let’s discuss the main reasons for this error and how we fix them.

phpMyAdmin error code 200 – Where do you see this?

Customers usually get this error when they try to manage databases from the phpMyAdmin(PMA) panel. They see this error while creating a new table, modifying a large table, etc.

And, the complete error message looks like this.

Error in processing request
Error code: 200
Error text: OK

phpMyAdmin error code 200 – Reasons & Solutions

Usually, this error may disappear once the customer restart the MySQL service or the whole server. But, this is not permanent. The same error can occur again at any point of time.

So, let’s see how our Dedicated Engineers fix this issue permanently.

1)  Memory limit

One of the main reasons for this error is the memory limit set on the server. Some PHP apps such as phpMyAdmin require lot of memory to run. So, the default memory allocated on the server isn’t enough.

We’ve seen instances where customers see this error when they try to upload large tables via phpMyAdmin interface. For example, the plesk server shows below error in the server log.

14-Feb-2019 08:25:19] PHP Fatal error: Allowed memory size of 279212646 bytes exhausted (tried to allocate 401128 bytes) in /opt/psa/admin/htdocs/domains/databases/phpMyAdmin/libraries/xxxxx on line xxxx

How we fix?

In such cases, our Support Engineers increase the memory_limit on the server so that the phpMyAdmin can function.

For example, we add the following code in php.ini file to increase the memory_limit to 512 MB.

memory_limit = 512M

In addition to that, we ensure that max_input_vars parameter is also set to an optimum value. Similarly, on Plesk servers, we modify the memory_limit value in Plesk PHP configuration file /usr/local/psa/admin/conf/php.ini and restart the plesk service.

In some cases, we can specifically increase the PHP settings exclusively for phpMyAdmin. For example, on WAMP’s phpMyAdmin, we allocate more memory to phpMyAdmin from \wamp\alias\phpmyadmin.conf.

php_admin_value memory_limit 512M

Be careful while setting the PHP memory limit on the server. Higher memory limits on the server gives a favorable environment for the attackers. We’ve seen customers setting memory_limit to -1 in php.ini. This sets memory limit to infinity which is a high security risk. So, our Server Experts always ensure that the PHP parameters on the server are set to optimum values.

2) Issues with language files

This problem can happen at times. We’ve seen instances where customer report this error when they try to view the table structure from phpMyAdmin panel.

Error in Processing Request Error code: 200 Error text: OK

This is actually a bug in the language files of phpMyAdmin. We’ve seen instances where customers see this error when they use other languages like Italian, French other than English.

How we fix?

In such cases, our Support Engineers change the language of the phpMyAdmin interface. We usually change the phpMyAdmin language my modifying the below parameter in config.inc.php file.

$cfg['Lang'] = '';

Alternatively, we can change the language from phpMyAdmin interface using the below steps.

• Click on the Server name.
• Go to Appearance settings.
• Change the language from drop down box.

How change language in phpMyAdmin?

Last but not the least, multiple sessions of phpMyAdmin running under the same user can also create this error. In such cases, our Support Experts request the customers to kill all the sessions of phpMyAdmin panel with the user and access it once again.

[Need a database expert to fix the error with your phpMyAdmin panel? We can help you here.]

Conclusion

In short, phpMyAdmin error code 200 usually occurs when customers try to modify the database from phpMyAdmin panel. This can be due to memory limits on the server, multiple sessions of the same user, etc. Today, we’ve discussed the main reasons for this error and how our Dedicated Engineers fix them.