Home » Blog

Windows Live Writer WordPress and the XMLRPC Issue

Submitted by on August 2, 2008 – 4:21 pm7 Comments

Sometimes when you try to set up a new blog account with the Windows Live Writer the installation process might be interrupted by an error message:


Invalid Server Response – The response to the blogger.getUsersBlogs method received from the weblog server was invalid: Invalid response document returned from XmlRpc server.

Unfortunately there is more than one reason for this error message and maybe you have to try them all.

Php problem

There is an error in the php modul. Open the xmlrpc.php in your wordpress root directory and enter this code on the first line:

$HTTP_RAW_POST_DATA = file_get_contents(“php://input”);


Htaccess problem

There is a conflict in the htaccess file, enter the following code somewhere in the htaccess file:

<Files xmlrpc.php>
SecFilterInheritance Off


PlugIn conflict

A plugin is causing a conflict. Try to deactivate all plugins and repeat the setup.


Lowercase vs. capital letters

WordPress runs on Apache and on apache lowercase matters. Login with your FTP program and check if the xmlrpc.php is written in lowercase if not upload again all files in the right format.

Note: It happens often after a WordPress update


XMLRPC activated?

With WordPress 2.6 there is the a new option (wordpress >> write) to deactivate the xmlprc api (standard: deactivated) Box must be checked

  • Windows Live Writer vs. WordPress
    If you are using WordPress and Windows Live Writer together and you are having problems, maybe these solutions from WordPress.org can help you. Image uploading fails Posting fails for some blogs that don’t use UTF-8, ISO-8859-1, or ......

  • WordPress: Invalid response from blogger.getUsersBlog
    Description: On blogs running PHP 5.2.2, trying to configure the blog in Writer gives the following error: Invalid Server Response – The response to the blogger.getUsersBlog method received from the weblog server was invalid. / ......

  • WordPress loves the Windows Live Writer
    Matt from WordPress.com about the Windows Live Writer: It’s a little known fact, but deep within the labyrinths of Microsoft there is a team of rogue ninjas making a fantastic Windows blogging client. If you compare the ......


  • naokii says:

    None of them can help for me. I’m using WHS PP1, PHP, MySQL, and WordPress.
    Yet another blog mentioned re-installing MySQL at all. I’ll try it tomorrow…

  • stephan says:

    Hi, which version du you use, the official latest release (Windows Live Instraller) or the CTP?

    Did you post your problem in the windows live forum?

  • Joseph Scott says:

    If XML-RPC is disabled, it returns an error indicating that (which includes instructions on how to turn it on). I’m not sure if WLW passes this error text back in the alert window.

  • Anirudh Goel says:

    Hi! Disabling the wp-visitors plugin settled my problem. Thanx.

  • Ajay says:

    There are currently three solutions to the issue of tags being stripped.

    I’ve listed them on http://techtites.com/2009/01/14/fix-the-windows-live-writer-and-wordpress-stripping-tags-issue/ along with a zip file with the fixed WordPress 2.7 files

  • Chris says:

    I’ve tried a ton of stuff – still can’t resolve it.

    1.) deactivated all plugins (no change)
    2.) removed all trailing/leading spaces from root dir PHP files (no change)

    3.) a.) tried a diff theme (issue went away)
    b.) removed all trailing/leading spaces from theme files
    c.) issue still returned upon going back to my theme)

    4.) added line to xmlrpc.php as directed here (no change)

    This is driving me nuts… obviously it’s my theme but what else should I be looking for? I’ve removed the leading/trailing spaces! :(

    Thanks in advance,

    - Chris

  • Sylvain says:

    Well, it looks like that even in 2010, there are still a lot of potential communication problems between Windows Live Writer (WLW) and a PHP based XML-RPC blog server.

    On my blog, I’ve recently posted an article on how to solve many of these problems by first identifying them precisely using either the log file of WLW and/or an HTML traffic capturing tool such as Fiddler. Beside the log file and Fiddler, this article also covers in detail some of the most common problems such a the presence of an UTF-8 BOM at the beginning of one of the PHP script files or the presence of extraneous characters at either the beginning (before the opening tag ) of one of those PHP script files.

    You can find this article there:


    In the second part (soon to be published), I will cover the problem of the presence of Warning and of Fatal PHP error messages in the XML-RPC response file. Fatal errors are usually the result of some kind of error in the PHP code but you can get a Warning error message simply by having a badly set php.ini file; so it’s often simply a local configuration problem of PHP.