Fix for WordPress XMLRPC 500 Internal Server Error

One of my WordPress-based sites ( was not working when I tried to publish posts containing images from Windows Live Writer.  I was getting a 500 Internal Server Error.

I was able to fix the problem by making a small change to the database.

The Error Message

I enabled Failed Request Tracing in IIS7 to find out what was happening server-side to cause the HTTP 500 error.  I discovered that the PHP script was trying to insert a row into the wp_posts table with a value of -1 in the post_parent column:

WordPress database error Out of range value for column ‘post_parent’ at row 1 for query INSERT INTO `wp_posts` (`post_author`,`post_date`,`post_date_gmt`, `post_content`, `post_content_filtered`, `post_title`, `post_excerpt`, `post_status`, `post_type`, `comment_status`,`ping_status`, `post_password`, `post_name`, `to_ping`, `pinged`, `post_modified`, `post_modified_gmt`, `post_parent`,`menu_order`,`post_mime_type`,`guid`) VALUES (‘1′,’2009-07-15 14:37:14′,’2009-07-15 17:37:14′,”,”,’2827426439_7b744abd30_m.jpg’, ”, ‘inherit’, ‘attachment’,’open’,’open’, ”, ‘2827426439_7b744abd30_m-jpg’,”,”,’2009-07-15 14:37:14′,’2009-07-15 17:37:14′,’-1′, ‘0’, ‘image/jpeg’, ‘’) made by wp_xmlrpc_server->wp_xmlrpc_server, IXR_Server->IXR_Server, IXR_Server->serve, IXR_Server->call, wp_xmlrpc_server->mw_newMediaObject, wp_insert_attachment
ErrorCode 5

Apparently the database didn’t like that…  I investigated further and discovered that the post_parent column in my database was set to BIGINT UNSIGNED.  In other words, that database column could not hold the value -1 (unsigned integers are zero or higher).

Some Sanity Checking

I checked several other WordPress databases that I control and found that post_parent column is not UNSIGNED in any of my other WP databases.

So why the difference?  All my other databases were created with earlier versions of WordPress and upgraded.  The database in question, however, had been created with the latest WordPress release (2.8 at the time).  So I popped open the PHP file that defines the database (schema.php) and discovered:

post_parent bigint(20) unsigned NOT NULL default ‘0’,

What’s Going On Here?

When the XMLRPC script uploads an image (called an attachment in WordPress), it uploads it with a post_parent of -1.  Then after the post is created, the script updates attachments with post_parent=-1 with the actual ID of the freshly created post.

My guess is that a developer on the project decided to update the schema to UNSIGNED because posts do not have negative values for IDs and the post_parent column references a post ID.  Obviously that developer did not realize the special use case in xmlrpc.php.

How Do I Fix This?

Fortunately the workaround is easy.  Just run the following database query to change the data type on the post_parent column:

ALTER TABLE wp_posts CHANGE post_parent post_parent BIGINT;

If you don’t know how to run queries against your MySQL database, well, this is a good time to learn.  I did it at the command line on my 64-bit Windows server:

cd "C:\Program Files (x86)\MySQL\MySQL Server 5.1\bin\"

mysql.exe –u root -p
Enter password: ***********************

Welcome to the MySQL monitor.  Commands end with ; or \g.

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the buffer.

mysql> use crowdspace
Database changed
mysql> ALTER TABLE wp_posts CHANGE post_parent post_parent BIGINT;

The process is similar on a Linux box.  I’m going to go out on a limb here and assume that you can figure out how to run mysql on Linux if you’re running your own Linux server.

If you’re using a shared web hosting service, you should be able to use a web interface such as phpMyAdmin to run this command.

That’s all it took to fix the problem for me.  Happy blogging!

21 thoughts on “Fix for WordPress XMLRPC 500 Internal Server Error

  1. Nice! This worked for me on IIS 7 using WordPress 2.8.1.

    I am able to post updates to my blog articles with images using live writer (and no FTP).


  2. Hi,

    I had encountered the same error and the SQL query sorted out the issue in a minute. Some other reasons for this issue were stated as Server running Php 4, but my server had Php 5 version and I ran this query from my WP Admin using the Wp-dbmanager plugin by Lester Chan, and it straight away sorted this out.

    Thanks for taking the time to figure this out.

  3. Did this rebreak for anyone with 2.9? I see that it was supposedly fixed in 2.9



  4. After talking with my internet company for a half hour and being on hold, i found your help and solved it. Thanks! (They had no clue what to do…)

  5. which’s a good list. and keep in mind if you are employing a wordpress weblog like several of are these days there are some excellent plugins to take care of that lot. my favourite seo plugin is seo platimum

  6. Awesome work! I started getting the 500 error randomly while editing the site on a slow Fatcow server. So I moved it to BlueHost, but on database import, the error came back!

    So I manually edited the site location options and ran your query, and it works!

    I did also have to activate another theme to get it running.

  7. Ok, this fix doesn’t work for me either. First of I don’t have mysql on my computer (windows 7, 86), so how can I “cd” to something that doesn’t exist?

    If you will teach, teach to illiterates too. Either do a good job or don’t do at all.

    – where is the database we need to edit? In our computer or on the computer of the server where wordpress is hosted?
    – how do we even find that?
    – if you will say Putty or Telnet, have the taste to add instructions to younger people who have no idea where and what they are and yes tries to fix the issue without spending a fortune calling a technician.

Comments are closed.