Can't connect to my blog using Windows Live Writer RRS feed

  • Question

  • I have a wordpress blog (WP 2.7) hosted on my own server (http://programmersnotes.info/). I start WLW, select "other blogs", put my address there, login and password (100% correct!) and in a few seconds I get an error:

    An error occured while attempting to connect to your blog:
    Invalid Server Response - The response to the blogger.getUsersBlogs method received from the blog server was invalid:
    Invalid response document returned from XmlRpc server
    You must correct this error before proceeding.

    How to fix this?
    Tuesday, April 21, 2009 11:54 AM

All replies

  • This is usually a plugin that is printing out an error message or the hosting company inserting an advertisement.  Try disabling all of your plugins and doing it again, then enabling each one until you find the problem.  If that doesn't work, send me your Windows Live Writer log file, and I can see if I can find the problem from it.  Help | About | Show Log File

    -Brandon Turner [MSFT]
    Tuesday, April 21, 2009 5:06 PM
  • Hello Brandon,.
    I am using Wordpress 2.02 hosted by Yahoo Small Business.  I have two blogs in the same domain with different themes. My blog http://www.prosperingtimes.com/blog works well with WLW but the blog http://www.prosperingtimes.com/blog1  has a similar problem described by KonstantinMirin, the error message is worded differently.  Since both blogs use the same plugins why would one work and not the other. By the way, the Beta Version of WLW worked well for both blogs.

    This is the error I am getting:

    An error occurred while attempting to connect to your blog:

    Blog Server Error – Server Error -32700 Occurred parse error.not well formed.

    Thanks for any help you can provide


    Tuesday, May 26, 2009 9:43 PM
  • -32700 means someone hacked your blog. Wordpress is currently in denial about the current version being hackable. To bad...

    If you haven't made many changes to files on your server you can try something like this:

    Login via SSH and run this command:

    find ./ -iname "*.php" -mtime 1

    -mtime is asking the server to tell you what has been modified in the last day... if nothing pops up try a 2 or 3 until you get to the day the hack occurred on.

    Lately the files in question have been index.php having an include added and xml-rpc having a function added (which is causing you your problem)...

    You will also have 2 new users which will be hidden from you in the admin. You must delete them from your database and also their user_meta entries.
    You will also have 1 or more Options added to your wp_options as magpie RSS updates. There are real ones and fake ones... The fake ones will have eval(), exec() or javascript() tags...

    Tracking down how they are getting in hasn't been fun... just found this list of hackable plugins and version numbers:

    Download a fresh copy of wordpress and copy the index and xmlrpc files plus any that have been changed and turn up with the find command.

    Good luck

    Wednesday, June 3, 2009 7:08 AM