Deploy fails to login to destination server

(Completed title)

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.

* System service enabled on remote server.
* Under admin/build/services/settings the settings are indeed as you outlined.
* On the remote server, the watchdog log reports "Session opened for username" (with correct username) followed by "cache clear serv" with message "caches cleared". Interestingly, in the details while both were from location http://example.com/services/xmlrpc, the session was opened by username while the latter is attributed to Guest. Don't know if that has any significance. Both list my originating IP address as the hostname.

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?

I put the use of Deploy on hold. I had hoped it would save me time during a hugely busy patch. When it didn't I didn't have time to troubleshoot/debug. Sorry. Still interested if I can get it working in future.

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.

OK, have made another attempt to get this working, with the latest versions of the modules available today. Here's the setup details:
Services on remote server: 6.x-2.x-dev (11 Jun 2009)
PHP on remote server: 5.2.6
PHP on local server: 5.2.6

Still getting the same problem.

Note that the remote server is www.example.com (not the actual URL obviously) and the local server is served (via MAMP Pro) at dev.example.com, which of course only resolves locally. I presume this would not be any problem but wanted to mention it in case that somehow casts light on the problem...

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.