Deploy fails to login to destination server

Some things to check:

- is the System Service enabled on your remote server?
- under admin/build/services/settings on the remote server, is 'Use SessID' checked and 'Use Keys' unchecked?
- are there any messages in the watchdog log on the remote server? (admin/reports/dblog)

Let me know if that gets you anywhere.

The fact that you got "session opened for username" means a login was done successfully, since that doesn't happen otherwise. So... I'm not sure what is going on. Here's some shot in the dark ideas:

- What version of Services are you running on the remote server?
- What version of PHP is running on both the local and remote servers?

Having a tough time figuring out what might be going wrong since you're seeing the session opened message

Did you ever get this problem resolved?

when i check the dblog
it gave me this message

access denied 06/11/2009 - 17:02 services/xmlrpc Anonymous
access denied 06/11/2009 - 17:02 services/xmlrpc Anonymous
access denied 06/11/2009 - 17:02 services/xmlrpc Anonymous

i did type in the username and password

running PHP Version 5.2.6
Services 6.x-1.x-dev

- is the System Service enabled on your remote server? <- yes
- under admin/build/services/settings on the remote server, is 'Use SessID' checked and 'Use Keys' unchecked? <- yes

anyone could help out?

Check out this issue and see if it helps you, there are some issues with later releases of Services

http://drupal.org/node/468608

thanks it works, able to login.

I am having the same issue with some slight variations:

Deployment log details are:
Module—"login"
Description—"Remote user login"
Result—"Error"
Message—"Not Found"

The deployment process does not even start.
I have all the settings as specified in the instructions and in this thread.
My dblog has nothing showing there was even a connection attempt.
Deployment settings are also empty.

PHP on both machines is 5.2.10
Deploy Module - 6.x-1.x-dev
Services Module - 6.x-2.x-dev

What is the correct path for the deployment server? I have : http://MYSERVERIPADDRESS/services/xmlrpc

However, the site I am deploying to is called 'Drupal', so should it be the following instead: http://MYSERVERIPADDRESS/Drupal/services/xmlrpc ??

Niether works, so its not helping either way, just curious.

Do I need the services module on source server also ?
Is it worth rolling back the services module?

The issue on my side was indeed the destination server's URL. I was missing the "?q="

I changed mine to the following and fixed the connection issue : http://www.example.com/?q=services/xmlrpc

But, now my deployment states success on source server, but the changes do not propagate to destination server.
I started a new thread for this issue, http://drupal.org/node/526936. Not sure if they're related.

I am also seeing the problem described in #3. Any solutions?

Me too. Same problem as in #3.

Last two destination sever log entries read: http://.com/admin/reports/dblog

cache clear serv 2009-08-27 15:30 caches cleared Anonymous
user 2009-08-27 15:30 Session opened for admin. admin

While the deploy server log entry reads: http://.com//admin/build/deploy/logs/details/47

login Remote user login Error Parse error. Not well formed

So, it seems like server gets logged in correctly, but subsequent requests are malformed somehow (even losing the right userid)

I reproduced this with two entirely different drupal databases and configurations. I think I've tried everything in these issues and comments.

BTW, I'm not complaining. Just hoping this will help. And I'm willing to try experiments.

This module is a huge job! Thx!

-- Cronin

I also get an error with message "Parse error. Not well formed" when deploying some nodes (it does work for other nodes though).

Contrary to ztnews' report above it happens when deploying the node, not at deployment login.

BTW We ran into a similar issue here, but the error returned was "Invalid schema" (should have been "scheme", but the spelling error is in drupal_http_request in common.inc). We traced it to an action we have that re-directs the user after they log-in. What was happening was that the XMLRPC request was getting redirected after logging the user in, and then the URL the request was sent to somehow ended up being relative.

By disabling the redirect action on log-in, the problem was solved.

After reading #16 (thanx GuyPaddock!) I have been digging some further and I found that I had the same issue! We had a trigger which redirected the user after logon. Apparently, this breaks deploy. After disabling the trigger the deployment proceeded 1 step further (and encountered another problem, namely Duplicate User, http://drupal.org/node/671214). My advice would be: check the access log for strange POST uris after the initial xmlrpc call.

Hey all, I have been away from this queue of late but I'm glad to see a solution coming out that seems to answer the problems. I'll make sure and document it in the handbook. Leaving this open until then.

I added a troubleshooting page with this info on it. If anyone on this thread continues having problems please open a new issue.

http://drupal.org/node/679604

I was getting the error message when trying to deploy a single node:

"login Remote user login Error Parse error. Not well formed"

After doing some digging, turns out the devel module timer was being appended at the end of the response on the destination server, causing an XML error.

To fix this, you can disable the devel timer on destination server (or both) or in the Admin Menu, click "Disable developer modules".

Hope this helps anyone

Hi Folks,

On content deployment, my Deployment Log Details show:

Module: login; Description: Remote user login; Result: Error; Message: Operation timed out

I've read through the Deploy documentation and this thread and am still stuck.

I don't see any problem with my Drupal configuration. Server URL is accurate. Server username / password are accurate.

Stage and Live are on the same FreeBSD server. Drupal ver. is 6.17. Deploy and Server modules are up-to-date.

Can anyone offer suggestions, apart from the tips already mentioned in this thread?

Thanks - Mike

I ran into this issue using Drupal Commons distro.

Attempts to login to the remote site kept returning a vague error message: Remote user login Error

After some digging, the problem wound up being a distro-specific setting at admin/settings/commons : Make sure to uncheck "Force users to login".

Seems like there is a theme here where redirecting users ( pre or post login ) will definitely screw things up.

@mikesnp There seems to be some kind of connection problem between your sites. The error messages states "Operation timed out". Do you have any special firewall configuration that has to be taken into consideration?

Please open a new issue if your problem still exists. This issue have been a little bloated by so many other things.

This issue can also be caused by a redirected server URL (by the Locale module for example)

I explained it here : http://drupal.org/node/679604#comment-3749782

I have the same issue when using deployment module meaning I have the same error :

Description : Remote user login | Result : Error | Message : not found

but in my case, localhost is the destination server as I am trying instead to transfer nodes from remote server to my localhost.

I had no problem in the other way : From Localhost to Remote site, except duplicate users but I bypassed it by modifying manually users uuid so they can match and it has resolved that issue but I cannot figure out a way to do the reverse operation that is to deploy nodes from my remote site to the localhost. Am I missing something? XMLRPC services does not work on localhost? Is there any further settings I must do in order to make it work knowing that I am on Windows 7?

Thanks for your help

In case it helps, I posted a description of one possible cause of this error on the thread: http://drupal.org/node/1030060#comment-4721670

Make sure you are not sending headers from somewhere your modules which normally cause AHAh/JSON expressions to fail while parsing. Also be ensured that your code is not startng with blank lines...