[psamman]

Hello,

I just updated My 6.9.1 Gateway to SP7 and installed XSR 2.1.0 in DMZ. I also installed a new license with SFTP option.
On statup I get error messages : Init(3) XSR initialization error for FTP/SFTP/ODT
And then : Protocol not allowed or invalid.

No more details. in the log.

Does this ring someone's bell?

[Tony]

We've had this issue accompany a binding error on a low port when we didn't have access to the port as the user running the software. If you've configured SFTP on a low por (22) you might try configuring it to run on a high port (like 6322) to see if that helps?

Hello,

I just updated My 6.9.1 Gateway to SP7 and installed XSR 2.1.0 in DMZ. I also installed a new license with SFTP option.
On statup I get error messages : Init(3) XSR initialization error for FTP/SFTP/ODT
And then : Protocol not allowed or invalid.

No more details. in the log.

Does this ring someone's bell?

[psamman]

We've had this issue accompany a binding error on a low port when we didn't have access to the port as the user running the software. If you've configured SFTP on a low por (22) you might try configuring it to run on a high port (like 6322) to see if that helps?

I actually configured 2222 as sshd was already running on our DMZ server.
This turned out to be an issue with the new XSR Java home variable (p_xsr_java_home). I replaced the old (p_xsr_master_java_home) one with this new one as indicated in the prerequisites in SP7.
Bad idea. The new variable makes sense to Gateway v6.11 (Synchrony), but none to v6.9.1.
So if you have v6.9.1 and install SP6/SP7, don't do as what the .txt that comes with it says! Update your old variable to Java 5, don't use the new one.

This pb. was confirmed by support, and will be "fixed" in future releases.

[Tony]

I actually configured 2222 as sshd was already running on our DMZ server.
This turned out to be an issue with the new XSR Java home variable (p_xsr_java_home). I replaced the old (p_xsr_master_java_home) one with this new one as indicated in the prerequisites in SP7.
Bad idea. The new variable makes sense to Gateway v6.11 (Synchrony), but none to v6.9.1.
So if you have v6.9.1 and install SP6/SP7, don't do as what the .txt that comes with it says! Update your old variable to Java 5, don't use the new one.

This pb. was confirmed by support, and will be "fixed" in future releases.

That's a fun one to have to learn the hard way I didn't even see that click. When I just upgraded an instance of gateway from 6.9.1 SP6 to 6.11.4 we actually went back to the previous version of XSR, not the one we installed for SP6 on 6.9.1. Nice fix.