How to resolve Joomla! HTTP 500 error after updates? Over the last week we, at Vevida, received quite a lot problem reports by customers who updated Joomla! to version 3.2.0. After logging on to their administrator back-end, they received an HTTP 500.0 error with error code
0x8007000d. Let’s investigate and resolve this Joomla! Administrator login HTTP 500 error.
Joomla HTTP 500.0 error #
Unfortunately this Joomla! HTTP 500 error has nothing important to tell, except Internal Server Error, The data is invalid. (0x8007000d) on IIS. So, nothing much… This basically means that somewhere the output breaks FastCgi and PHP output.Advertisement:
The information in this post is still valid, even for Joomla 3.6.4!
The given HTTP 500.0 error after logging on looks like:
An IIS Failed Request Tracing report looks like:
Here’s how to fix this HTTP 500.0 (The data is invalid. (0x8007000d)) error after a Joomla! update, for example to version 3.2.0:
How to fix the Joomla! HTTP 500 error after updates #
Luckily the error is quite easy to fix. If only I knew this earlier, it would have saved me some time :-) . This post certainly will save you time.
Follow the next steps:
- when you’ve tried to log on and the HTTP 500.0 error is displayed, add
?option=com_installer&view=databasein the address bar of your browser to the URL. The full URL then becomes
- after pressing the ENTER key on your keyboard, you’re automatically logged on to your Joomla! 3.2.0 administrator back-end.
- You’ll probably notice database errors. These database errors can be repaired in the back-end using the Fix-button, and this resolves the log on issue permanently
Curious to learn how to optimize Joomla with just 8 simple tips?
Tested and verified with Joomla 3.2.4, 3.3.6 and 3.6.4 #
This fix is still valid for Joomla 3.2.4, 3.3.6 and Joomla 3.6.4 updates.
Incorrect file permissions on log/error.php #
Turns out, at least on Windows Server IIS, PHP/FastCgiModule might throw this
0x8007000d error if file and directory permissions are improperly (incorrectly) configured. You have to correct that as well.
However, at the same time, after setting correct file permissions on
logs/error.php and logging in, Joomla complained about two database problems:
Database schema version (3.1.1) does not match CMS version (3.3.6-2014-09-30).
Database update version (None) does not match CMS version (3.3.6).