on 10-17-2014 8:44 AM
Hello Experts
I am having scenario I-Doc->PI->SFTP . We have done many scenarios like this but we are facing issue with one vendor. We able to LogOn to server using SFTP from FTP client (File Zill, WinSCP), via PI 7.31 command terminal or from local command line. But we are facing issue only PI receiver SFTP channel.
Below is SFTP receiver configuration(with all the tabs).
We are getting below error. We tried deleting existing channel and creating new one as well but no luck.
17.10.2014 10:50:26.515 | Error | Message could not be forwarded to the JCA adapter. Reason: 10: pwd failed. |
17.10.2014 10:50:26.516 | Error | MP: exception caught with cause javax.resource.ResourceException: 10: pwd failed. |
17.10.2014 10:50:26.520 | Error | Exception caught by adapter framework: 10: pwd failed. |
17.10.2014 10:50:26.521 | Error | Delivery of the message to the application using connection SFTP_http://sap.com/xi/XI/SFTP failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: 10: pwd failed. |
Please help me to resolve this.
Thanks,
Nishit.
Hello,
Thanks for reply.
@ Hareesh : I have change these parameters in my CCH but it doesn't help.
@ Diptee : yes port is correct and we are able to connect SFTP server using WinSCP.
@ Varun : We are using WinSCP to test SFTP connection. Please refer below log;
. 2014-10-20 12:30:51.720 --------------------------------------------------------------------------
. 2014-10-20 12:30:51.720 WinSCP Version 4.3.2 (Build 1201) (OS 6.1.7601 Service Pack 1)
. 2014-10-20 12:30:51.720 Login time: Monday, October 20, 2014 12:30:51 PM
. 2014-10-20 12:30:51.721 --------------------------------------------------------------------------
. 2014-10-20 12:30:51.721 Session name: PHD
. 2014-10-20 12:30:51.721 Host name: XXX.XXX.XXX.XXX (Port: 2222)
. 2014-10-20 12:30:51.721 User name: XXX (Password: No, Key file: Yes)
. 2014-10-20 12:30:51.721 Tunnel: No
. 2014-10-20 12:30:51.721 Transfer Protocol: SFTP (SCP)
. 2014-10-20 12:30:51.721 Ping type: -, Ping interval: 30 sec; Timeout: 15 sec
. 2014-10-20 12:30:51.721 Proxy: none
. 2014-10-20 12:30:51.721 SSH protocol version: 2; Compression: No
. 2014-10-20 12:30:51.721 Bypass authentication: No
. 2014-10-20 12:30:51.721 Try agent: Yes; Agent forwarding: No; TIS/CryptoCard: No; KI: Yes; GSSAPI: No
. 2014-10-20 12:30:51.721 Ciphers: aes,blowfish,3des,WARN,arcfour,des; Ssh2DES: No
. 2014-10-20 12:30:51.721 SSH Bugs: -,-,-,-,-,-,-,-,-
. 2014-10-20 12:30:51.721 SFTP Bugs: -,-
. 2014-10-20 12:30:51.721 Return code variable: Autodetect; Lookup user groups: Yes
. 2014-10-20 12:30:51.721 Shell: default
. 2014-10-20 12:30:51.721 EOL: 0, UTF: 2
. 2014-10-20 12:30:51.721 Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes
. 2014-10-20 12:30:51.721 LS: ls -la, Ign LS warn: Yes, Scp1 Comp: No
. 2014-10-20 12:30:51.721 Local directory: default, Remote directory: home, Update: No, Cache: Yes
. 2014-10-20 12:30:51.721 Cache directory changes: Yes, Permanent: Yes
. 2014-10-20 12:30:51.721 DST mode: 1
. 2014-10-20 12:30:51.721 --------------------------------------------------------------------------
. 2014-10-20 12:30:51.729 Looking up host "XXX.XXX.XXX.XXX"
. 2014-10-20 12:30:51.729 Connecting to XXX.XXX.XXX.XXX port 2222
. 2014-10-20 12:30:53.365 Server version: SSH-2.0-1.82 nuBridgesSSH: NCSftpServer
. 2014-10-20 12:30:53.365 We believe remote version has SSH-2 ignore bug
. 2014-10-20 12:30:53.365 Using SSH protocol version 2
. 2014-10-20 12:30:53.365 We claim version: SSH-2.0-WinSCP_release_4.3.2
. 2014-10-20 12:30:53.941 Doing Diffie-Hellman group exchange
. 2014-10-20 12:30:54.229 Doing Diffie-Hellman key exchange with hash SHA-1
. 2014-10-20 12:30:54.795 Host key fingerprint is:
. 2014-10-20 12:30:54.796 ssh-dss 1024 XX.XX.XX.XX
. 2014-10-20 12:30:54.796 Initialised AES-256 CBC client->server encryption
. 2014-10-20 12:30:54.796 Initialised HMAC-SHA1 client->server MAC algorithm
. 2014-10-20 12:30:54.796 Initialised AES-256 CBC server->client encryption
. 2014-10-20 12:30:54.796 Initialised HMAC-SHA1 server->client MAC algorithm
. 2014-10-20 12:30:55.528 Reading private key file "E:\privatekey.ppk"
! 2014-10-20 12:30:55.528 Using username "torrent_sftp".
. 2014-10-20 12:30:55.873 Offered public key
. 2014-10-20 12:30:56.205 Offer of public key accepted
! 2014-10-20 12:30:56.205 Authenticating with public key "imported-openssh-key"
. 2014-10-20 12:30:57.147 Access granted
. 2014-10-20 12:30:57.709 Opened channel for session
. 2014-10-20 12:30:58.372 Started a shell/command
. 2014-10-20 12:30:58.375 --------------------------------------------------------------------------
. 2014-10-20 12:30:58.375 Using SFTP protocol.
. 2014-10-20 12:30:58.375 Doing startup conversation with host.
> 2014-10-20 12:30:58.377 Type: SSH_FXP_INIT, Size: 5, Number: -1
< 2014-10-20 12:30:58.646 Type: SSH_FXP_VERSION, Size: 5, Number: -1
. 2014-10-20 12:30:58.646 SFTP version 3 negotiated.
. 2014-10-20 12:30:58.646 We believe the server has signed timestamps bug
. 2014-10-20 12:30:58.646 We will use UTF-8 strings for status messages only
. 2014-10-20 12:30:58.649 Getting current directory name.
. 2014-10-20 12:30:58.649 Getting real path for '.'
> 2014-10-20 12:30:58.649 Type: SSH_FXP_REALPATH, Size: 10, Number: 16
< 2014-10-20 12:30:58.940 Type: SSH_FXP_NAME, Size: 22, Number: 16
. 2014-10-20 12:30:58.940 Real path is '/'
. 2014-10-20 12:30:58.940 Listing directory "/".
> 2014-10-20 12:30:58.940 Type: SSH_FXP_OPENDIR, Size: 10, Number: 267
< 2014-10-20 12:30:59.210 Type: SSH_FXP_HANDLE, Size: 35, Number: 267
> 2014-10-20 12:30:59.210 Type: SSH_FXP_READDIR, Size: 35, Number: 524
< 2014-10-20 12:30:59.484 Type: SSH_FXP_NAME, Size: 384, Number: 524
> 2014-10-20 12:30:59.484 Type: SSH_FXP_READDIR, Size: 35, Number: 780
< 2014-10-20 12:30:59.759 Type: SSH_FXP_STATUS, Size: 31, Number: 780
< 2014-10-20 12:30:59.759 Status code: 1
> 2014-10-20 12:30:59.759 Type: SSH_FXP_CLOSE, Size: 35, Number: 1028
. 2014-10-20 12:30:59.759 Startup conversation with host finished.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Nishit,
Can you check the below threads
http://scn.sap.com/thread/3243632
http://scn.sap.com/thread/2000990
BR,
Diptee
Hello Nishit,
In that case why have you selected Password as the authentication method in your channel, shouldn't it be private key?
Please refer to this http://scn.sap.com/docs/DOC-31925
BR,
Diptee
Can you try adding the below additional properties in the channel?
1859563 - Channel broken fix and advanced paramters for ignoring error
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nishit,
Can you paste the log of Filezilla here.
Regards
Varun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.