topic ERROR: Remote signon to HOST canceled. in New SAS User

ERROR: Remote signon to HOST canceled.

helannivas88 — Tue, 28 Jan 2020 20:26:05 GMT

Hi ,

%let host = xxxxxxxaa.machine.test.group;

options comamid=tcp remote=host;

signon;

NOTE: Remote signon to HOST commencing (SAS Release 9.04.01M4).

ERROR: A communication subsystem partner link setup request failure has occurred.

ERROR: The connection was refused.

ERROR: Remote signon to HOST canceled.

Can you please let me know the error message and any configuration changes required.

I have requirement to create a macro variable from Client session and pass those to the server as a session variable.I have tried the below SAS code . but ended up with the error

%let host = xxxxxxxxaa.machine.test.group;

options comamid=tcp remote=host;

signon;

%let rc1=HDSIV2;

%let rc2=MRTGIS;

%syslput _all_;

rsubmit host;

%put rc1=&rc1;

%put rc2=&rc2

endrsubmit;

Thanks in Advance!!!

Re: ERROR: Remote signon to HOST canceled.

SASKiwi — Tue, 28 Jan 2020 21:04:50 GMT

Has this ever worked or is this the first time you have tried to get it going?

Try adding a port number to your host definition. The default port is 7551. It could be different for you. Check the definition of your SAS/CONNECT server in SAS MAnagement Console.

%let host = xxxxxxxaa.machine.test.group 7551;

If that doesn't help check your SAS/CONNECT spawner is working on your SAS server. You can do this in SAS Environment Manager.

Re: ERROR: Remote signon to HOST canceled.

helannivas88 — Wed, 29 Jan 2020 14:48:19 GMT

Thanks @SASKiwi for your response.

In the Management Console, SASApp --> SASApp - Connect Server --> Options --> Remote Host and it has been given as the same host which I have been used in my program. I have checked the ConnectSpawner status on the host directly ,by running ./Connectspawner.sh status and its up and running .

Port has been defined in SMC as 7551 and SIGNON Types as Scriptless.

But still I'm getting the same error message.

Re: ERROR: Remote signon to HOST canceled.

SASKiwi — Wed, 29 Jan 2020 19:21:29 GMT

@helannivas88 - When we were getting SAS/CONNECT going we had to specify this:

options noconnectmetaconnection;

as we were using single sign-on to connect to SAS. Perhaps you could be too?