Exception: Parse error. Not well formed

@Splicer, sorry for having trouble with the module, I hope we can resolve this asap so that you get the benefits.

The message you're seeing makes me believe that your remote server is reponding with a HTML page instead of the requested XML response. Currently, Drupal doesn't allow access to malformed response, but with the applied patch you will be getting debugging information. Please apply that to the commin.inc and also turn debugging in the DRD settings on. You will then get additional information in watchdog. Please have a look there and let me know what's in there. We should then be able to identify the cause for the problem.

I've reassigned the issue to drd_server. However, could you please post the HTML response that you get on your drd in D7 as this is going to tell us what's going wrong.

I meant HTML output *on* the D7 server (which comes *from* the D6 server). So what you provided was already helpful: it's a page not found. As far as I know the XMLRPC is not throwing a 404 ever so it sounds as if the D7 server calls the xmlrpc.php on the D6 server and doesn't find the page. This could either happen because of a typo or because the D6 server is not reachable from the D7 server. Both sounds unlikely but I have no other idea.

To find out more I attach a modified xmlrpc.php file which you should put into your D6 Drupal directory. It will write some lines into the PHP error log when the xmlrpc.php is called. Please make sure that error logging is configured and turned on.

Looking forward to seeing what goes into the error log and hope it will help us to fix this problem for you.

Note: please rename the file to xmlrpc.php

As the file isn't big anyway we can copy the content here and you should copy and paste that into your xmlrpc.php:

<?php

//File for debugging purposes only

error_log('XMLRPC 1');
include_once './includes/bootstrap.inc';
error_log('XMLRPC 2');
drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL);
error_log('XMLRPC 3');
include_once './includes/xmlrpc.inc';
error_log('XMLRPC 4');
include_once './includes/xmlrpcs.inc';
error_log('XMLRPC 5');

xmlrpc_server(module_invoke_all('xmlrpc'));
error_log('XMLRPC 6');

Well, when you're calling xmlrpc.php directly and you still don't get any log entries that means that error logs in php.ini are not configured. Please have a look here http://us2.php.net/manual/en/errorfunc.configuration.php#ini.error-log first and make sure you're getting the log entries first. Then, we can look again into the scenario what happens when xmlrpc.php gets called by DRD.

PHP logging has nothing to do with error loggin in Drupal. From the config lines you're sharing here it looks as if your PHP error are logged in the system log, so you should refer to that to see if any reports are in there.

Or you change your PHP error logging to file by configuring something like this in php.ini:

error_log = "c:\temp\phperror.log"

Good! So here is another version of the xmlrpc.php which will help us to find out which module is screwing up:

<?php

//File for debugging purposes only

error_log('XMLRPC 1');
include_once './includes/bootstrap.inc';
error_log('XMLRPC 2');
drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL);
error_log('XMLRPC 3');
include_once './includes/xmlrpc.inc';
error_log('XMLRPC 4');
include_once './includes/xmlrpcs.inc';
error_log('XMLRPC 5');

  $hook = 'xmlrpc';
  $return = array();
  foreach (module_implements($hook) as $module) {
    error_log('XMLRPC 5: '. $module);
    $function = $module .'_'. $hook;
    $result = call_user_func_array($function, array());
    error_log('XMLRPC 5: '. $module .' ok');
    if (isset($result) && is_array($result)) {
      $return = array_merge_recursive($return, $result);
    }
    else if (isset($result)) {
      $return[] = $result;
    }
  }

xmlrpc_server($return);
error_log('XMLRPC 6');

Good, all modules working fine. Now let's analyze xmlrpc_server(), please replace your xmlrpc.php with this:

<?php

//File for debugging purposes only

error_log('XMLRPC 1');
include_once './includes/bootstrap.inc';
error_log('XMLRPC 2');
drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL);
error_log('XMLRPC 3');
include_once './includes/xmlrpc.inc';
error_log('XMLRPC 4');
include_once './includes/xmlrpcs.inc';
error_log('XMLRPC 5');

$callbacks = module_invoke_all('xmlrpc');

  $xmlrpc_server = new stdClass();
  // Define built-in XML-RPC method names
  $defaults = array(
      'system.multicall' => 'xmlrpc_server_multicall',
    array(
      'system.methodSignature',
      'xmlrpc_server_method_signature',
      array('array', 'string'),
      'Returns an array describing the return type and required parameters of a method.'
    ),
    array(
      'system.getCapabilities',
      'xmlrpc_server_get_capabilities',
      array('struct'),
      'Returns a struct describing the XML-RPC specifications supported by this server.'
    ),
    array(
      'system.listMethods',
      'xmlrpc_server_list_methods',
      array('array'),
      'Returns an array of available methods on this server.'),
    array(
      'system.methodHelp',
      'xmlrpc_server_method_help',
      array('string', 'string'),
      'Returns a documentation string for the specified method.')
  );
  // We build an array of all method names by combining the built-ins
  // with those defined by modules implementing the _xmlrpc hook.
  // Built-in methods are overridable.
  foreach (array_merge($defaults, (array)$callbacks) as $key => $callback) {
    // we could check for is_array($callback)
    if (is_int($key)) {
      $method = $callback[0];
      $xmlrpc_server->callbacks[$method] = $callback[1];
      $xmlrpc_server->signatures[$method] = $callback[2];
      $xmlrpc_server->help[$method] = $callback[3];
    }
    else {
      $xmlrpc_server->callbacks[$key] = $callback;
      $xmlrpc_server->signatures[$key] = '';
      $xmlrpc_server->help[$key] = '';
    }
  }

  $data = file_get_contents('php://input');
  if (!$data) {
    die('XML-RPC server accepts POST requests only.');
  }

error_log('XMLRPC 5 data: '. print_r($data, TRUE));

  $xmlrpc_server->message = xmlrpc_message($data);

error_log('XMLRPC 5 message: '. print_r($xmlrpc_server->message, TRUE));

  if (!xmlrpc_message_parse($xmlrpc_server->message)) {
    xmlrpc_server_error(-32700, t('Parse error. Request not well formed.'));
  }
  if ($xmlrpc_server->message->messagetype != 'methodCall') {
    xmlrpc_server_error(-32600, t('Server error. Invalid XML-RPC. Request must be a methodCall.'));
  }
  if (!isset($xmlrpc_server->message->params)) {
    $xmlrpc_server->message->params = array();
  }
  xmlrpc_server_set($xmlrpc_server);
  $result = xmlrpc_server_call($xmlrpc_server, $xmlrpc_server->message->methodname, $xmlrpc_server->message->params);

  if (is_object($result) && !empty($result->is_error)) {
    xmlrpc_server_error($result);
  }
  // Encode the result
  $r = xmlrpc_value($result);
  // Create the XML
  $xml = '
<methodResponse>
  <params>
  <param>
    <value>'.
    xmlrpc_value_get_xml($r)
    .'</value>
  </param>
  </params>
</methodResponse>

';
  // Send it
  xmlrpc_server_output($xml);

error_log('XMLRPC 6');

So what all that means is that it's working fine. The fact that "XMLRPC 6" is not in the error log is because xml_server_output() calls exit and hence doesn't return to xmlrpc.php

Also, in #13 you wrote that thte log sequence is in the log 3 times which also means that xmlrpc.php has been called 3 times which only happens when DRD is getting reasonable response in approach 1 and 2.

So, I can't really tell what should be finally wrong and can just offer to have a look at your system if you were able to give me access to your system. But that would have to wait until tomorrow as it's already pretty late here.

If you were OK with this please send me a PM with the details.

@Splicer, what's the status of this, can you please give us an update of your situation?

I got the same problem with a self developed modul. Thx at first for the xmlrpc debugging snippet. It helps me really to come closer to the problem. I also use D6 and i can't give because I need a really working solution. So has someone else any ideas where the problem is? Is it maybe a webserver configuration problem or maybe a problem in the service modul? Any help is welcome.

I'm also getting this error. Guessing there's been no process with it? Can look into getting the maintainer access rights to the sites in question if that helps?

@willhowlett, I'd be glad to have a look into your sites if that's possible. Please contact me via PM or on Skype (jurgenhaas) and we'll find a way to debug and resolve your problem.

Jurgen has very kindly had a look at our sites.

In our case it turned out the error message was displaying because the DRD Server site did not have the update status module enabled (on our multisite installation we just keep it enabled on one site in order to keep an eye on module statuses - which is something I suspect many other admins do as well). Enabling it caused the error message to disappear, and everything seems to be working properly now.

Great module, sure to be a real time saver. Many thanks.

If there will be similar problems please open a separate ticket.