Blogdesk:XML Parsing Error: Invalid procedure call or arg

mattwardman · Post by **mattwardman** » 20.06.2007 11:50

I've been quite happily running with Blogdesk for 400 postings.

Last night I got an error when trying to do anything that involves BD talking to wordpress (e.g., post, refresh categories):

“XML Parsing Error: Invalid procedure call or argument” when working with this blog.

It is working successfully with a number of other blogs, which implies the problem is with Wordpress - however the configs are pretty much identical.

The versions are Wordpress 2.1.2 and Blogdesk 2.6 Build 600. Blogdesk is set to "pre-2.2".

I have gone so far as to deinstall all the plugins - and the error still occurs.

Can anyone point me to the area of Wordpress I should be looking at, and/or any logfiles etc in Blogdesk?

The URL: www.mattwardman.com/blog/

Cheers. Matt

Johannes · Post by **Johannes** » 20.06.2007 12:05

First of all: try if other weblog clients (like Qumana or BlogJet) can access your blog - this will help us narrow down the cause of the problem.

mattwardman · Post by **mattwardman** » 20.06.2007 12:35

Thanks. Will do. In the meantime this is a debug.txt file extracted from the broken blog.

An "Edit Past Posts" requests to the broken blog fails with the same error.

A request to a working blog gives an XML category list.

- Debug.txt file from Get Categories request to broken blog:

********************************************************************************
Time: 20.06.2007 - 11:23
System: MetaweblogAPI,WordPress (< 2.2)
Method: metaWeblog.getCategories
RPC: www.mattwardman.com/blog/xmlrpc.php
Version: 2.6.600
********************************************************************************
<Start Sending XML Section Removed>

--- START RECEIVED ---
XML-RPC server accepts POST requests only.
--- END RECEIVED ---

--- START ERROR ---
XML Parsing Error: Invalid procedure call or argument
--- END ERROR ---

mattwardman · Post by **mattwardman** » 20.06.2007 12:48

Attempting to set up the blog with Blogjet also results in a:

Matt

mattwardman · Post by **mattwardman** » 20.06.2007 12:59

May have a solution.

I grabbed the xmlrpc.php from an installation of Wordpress 2.2 to replace the existing (corrupted?) version and it seems to be talking now, even though I have not changed the version set in Blogdesk.

The file sizes are: old one 37.6k, new one 53.7k

Matt

mattwardman · Post by **mattwardman** » 20.06.2007 13:07

It also reports to Blogjet now too.

That can probably be taken as solved, unless I post here again.

I know enough to tinker.

For future visitors:

Problem

Blogdesk talking to Wordpress 2.1.2. Receives "XML Parsing Error: Invalid procedure call or argument” when working with this blog" error.

Solution

Rename xmlrpc.php file in Wordpress root directory to xmlrpc-old.php as backup. Replace with equivalent file from Wordpress 2.2.

Johannes · Post by **Johannes** » 20.06.2007 13:51

mattwardman wrote: Rename xmlrpc.php file in Wordpress root directory to xmlrpc-old.php as backup. Replace with equivalent file from Wordpress 2.2.

Better yet: update WordPress to the current version :-)

mattwardman · Post by **mattwardman** » 20.06.2007 17:52

I've thought about updating, but it's quite a big blog with several dozen plugins.

Never done an update before, so I'll try first on one that I can afford to lose.

Matt

joseph · Post by **joseph** » 11.03.2008 01:02

Hi Johannes - I have this error with a WP 2.3.3 installation. I've tried renaming the file to blogdesk.php, and re-uploading it, but still get this error. I used the same install files for four WP installations on one day, and only this one fails to work!

Thanks in advance for any suggestions,
Joseph

Johannes · Post by **Johannes** » 11.03.2008 01:08

My first question (as usual): does it work with other weblog clients (like Qumana or BlogJet)?

joseph · Post by **joseph** » 12.03.2008 00:44

Hi - sorry for the delay, but I had to wait for a faster connection to download and try Blogjet.

No, it doesn't work in Blogjet either. It gives an error saying 'Could not connect to server'. I have changed the password, so that's definitely not the problem...

What problem could there be with my site that would give a problem like this?

Thanks in advance!
Joseph