Expand / Collapse Navigation
 |
Interpel PeSIT HS E error "304, Requester identification not allowed (security)" |
 May 27 2009, 07:57 AM
Post
#1
|
|
|
Visitor  Group: Members Posts: 2 Joined: 26-May 09 Member No.: 534  |
I have installed InterPel 6.6.3 on 2 Windows machines
On each machine, I have configured local site, remote site, applications. When I try a transfer with PeSIT HS E protocol, I get an error.  The sender side GUI log shows: SUP006I 26.05.2009 16:40:14 AOFR14389(1) connection in requester mode refused: reason="166, Connection failure" / prot.diag="304, Requester identification not allowed (security)". The receiver side GUI log shows: SUP004I 26.05.2009 16:40:16 (23) connection in server mode refused: reason="14, Invalid remote identifier". I can't see where the problem is.  Any help would be appreciated, thank you. |
 |
 
|
|
May 27 2009, 10:44 AM
Post
#2
|
|
|
Visitor Group: Members Posts: 2 Joined: 26-May 09 Member No.: 534 |
QUOTE (Emmanuel @ May 27 2009, 07:57 AM)  I have installed InterPel 6.6.3 on 2 Windows machines On each machine, I have configured local site, remote site, applications. When I try a transfer with PeSIT HS E protocol, I get an error. The sender side GUI log shows: SUP006I 26.05.2009 16:40:14 AOFR14389(1) connection in requester mode refused: reason="166, Connection failure" / prot.diag="304, Requester identification not allowed (security)". The receiver side GUI log shows: SUP004I 26.05.2009 16:40:16 (23) connection in server mode refused: reason="14, Invalid remote identifier". I can't see where the problem is. Any help would be appreciated, thank you. OK, support axway has answered: "invalid remote identifier" refers to the protocol identifier, it must be set to the alias name. |
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
|
Lo-Fi Version | Time is now: 30th July 2010 - 01:10 PM |
Skin designed by IPB Forum Skins