How to fix Joomla! HTTP 500 error after updates? Over the last week we, at Vevida, received quite some 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.

The information in this post is still valid, even for Joomla 3.6.4 and up!

What is the Joomla! HTTP Error 500?

Unfortunately this Joomla! HTTP Error 500: Internal Server Error has nothing important to tell, except Internal Server Error, The data is invalid. (0x8007000d) on IIS.

That’s not much…

It basically means that somewhere the output breaks FastCgi and PHP output.

The given HTTP 500.0 error, after logging on, looks like:

An IIS Failed Request Tracing report looks like:

How to fix a Joomla! HTTP Error 500 after Joomla! updates

Often, you can fix this HTTP error 500 in Joomla pretty easy. If only I knew this earlier, it would have saved me some time 🙂 . This post certainly will save you time.

Follow the next steps:

  1. when you’ve tried to log on and the HTTP 500.0 error is displayed, add ?option=com_installer&view=database in the address bar of your browser to the URL. The full URL then becomes http://www.example.com/administrator/index.php?option=com_installer&view=database.
  2. after pressing the ENTER key on your keyboard, you’re automatically logged on to your Joomla! Administrator back-end.
  3. You’ll probably notice database errors. These database errors can be repaired easily using the Fix-button. This resolves the log on issue permanently.
This may interest you:   Umbraco: Route example.com to www.example.com

Curious to learn how to improve Joomla! performance with just 8 simple tips?

HTTP 500 fix tested and verified with Joomla 3.2.4, 3.3.6 and 3.6.4

This fix for HTTP 500 errors during log-on to Joomla administrator 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 an 0x8007000d error, if file and directory permissions are improperly (incorrectly) configured. You must correct the file permissoins as well!

However, at the same time, after setting correct file permissions on logs/error.php and logging on, 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).


Did this post help you solve a problem? Want to say thanks?

Did you find this post interesting? Did it help you solve a problem? If I’ve helped you out and you want to thank me, then why not buy me a coffee?

A small donation of only $5 helps out a lot in the development, research and hosting of this blog.

If I’ve helped you out and you want to thank me, why not buy me a coffee?

Thank you for your support.