Parse error. Not well formed.

I am also having this issue, and have reviewed both of the nodes referenced above. I do not have a date field in my node type, and I don't want to hack core...

I am running the same version of deploy, but Drupal core 6.20 instead of the OP's 2.19.

My error log details are identical, one line.

I see the error on multiple types of node pages, with different fields (some with images, some simply content, etc...)

Just noticed that when I submitted the module-enable form for all of the services on the destination server, none of them were selected. I also uploaded into the /modules directory on accident instead of the sites/all/modules dir (I don't think it technically matters for this, but still a bonehead move). I will fix these issues and report back if it helps.

Well, unfortunately resolving these issues didn't remove the error. Still getting a "Parse Error, Not Well Formed"

Any chance it has to do with special characters in the login? I'm using a generated password that has loads of special chars in it....are you?

Well, count my instance of this error in the bonehead category. I tried to follow the install instructions exactly, but it seems that I took some liberty at step five for the deployment server. I had only entered the base address for my live site. Instead, following the following step as written solved my problem.

5. Enter 'Live Server' for the Name and 'http://your-destination-site.example.com/services/xmlrpc' for the URL field. (Replace "your-destination-site.example.com" with the domain that you will be using for your actual destination server.) Save the server information.

Hopefully this helps someone else who makes the same mistake.

Thanks for the cool module.

Did you ever worked it out? I'm having the same problem

Any time you get a response like this it basically means there was a fatal error on the destination server. Check your error logs there.

As katbailey says, it's probably a problem on the destination side. Could we see some more extensive logs from there?

In case this helps anyone who comes across this support thread, here is how we addressed this error. After digging through the code and printing out lots of dpm()s, we discovered that the session ID was not being returned from the destination site when Deploy was attempting to login. Through process of elimination, we determined that this issue was caused by a small syntax error in a custom module: a blank line above the opening <?php tag.

My hunch is that this line break was causing Drupal to send the HTTP headers too early, before the session was set. Whether or not that is the specific cause of the issue in our case, removing that line (and removing a stray $nid =0; that was in the module but not in any functions and was leftover from early development) fixed the issue.

This is a rather specific case that probably isn't the cause of this error message for most sites, but thought I'd post it here in case it happens to help someone.

To help version 6.x-1.x move forward, please see this issue: #526936: Find best way to proceeding with 6.x-1.x and more specifically this comment: http://drupal.org/node/526936#comment-4931548

I encountered the very same problem. In our case, the problem went away after simply disabling the Devel module. Might be a way to fix this for some.