SAS Connect issue.
in [SAS]
|
From: xlr82sas on 8 Feb 2010 16:34 On Feb 8, 11:02 am, nwes...(a)AMGEN.COM (Norman Weston) wrote: > Recently I have started experiencing issues with Remote Submit. I have > previously had not problems but the issue started about Mid Jan of this > year. > > I am running a Tunnel through PuTTy which hasn't changed and I am calling > tcipunix.scr script which also hasn't changed. > > It looks like the process is timing out when attempting to initiate a SAS > session and here is the error message I get (after turning on TRACE in the > tcipunix.scr): > > TRACE: Type 'sas -dmr -comamid tcp -device grlink -noterminal '; > TRACE: Type '-nosyntaxcheck' lf; > TRACE: Waitfor 'SESSION ESTABLISHED', > TRACE: 90.0 seconds: nosas; > ERROR: Cannot start remote process. > ERROR: Cannot start remote process. > Goodbye > ERROR: Script file interpretation terminated due to error. > NOTE: End of script file trace. > ERROR: A communication subsystem partner link setup request failure has > occurred. > ERROR: recv call failed, lost connection with client. > ERROR: Remote signon to SERVER cancelled. > > To my knowledge my PC SAS license hasn't changed, nor my permissions in > the Unix Environment. Any thoughts on what may be causing this? Hi Norman, This is probably not the issue, but I did get the same error a few months ago. I had changed nothing. IS decided to add a unix permissions group to all unix users. The pushed my unix groups beyond 16 groups. It caused a permissions problem that the tunnel would not return. It took me along time to figure out the problem.
From: Norman Weston on 8 Feb 2010 18:20 Thanks for the suggestion. I am familiar with the MAXGROUPS issue as related to EG and have verified that I only have 15 (below the 16 set on our system). So I am guessing that isn't the problem. Any other ideas?
From: Tom Abernathy on 8 Feb 2010 19:57 Maybe your unix system is sloooooow. Try making the timeout longer. Also try signing on manually and make sure the prompts from the unix system haven't changed. On Feb 8, 6:20 pm, nwes...(a)AMGEN.COM (Norman Weston) wrote: > Thanks for the suggestion. I am familiar with the MAXGROUPS issue as > related to EG and have verified that I only have 15 (below the 16 set on > our system). So I am guessing that isn't the problem. > > Any other ideas?
From: Jack Hamilton on 8 Feb 2010 23:54 What happens if you log in to Unix and issue the SAS startup command directly? -- Jack Hamilton jfh(a)alumni.stanford.org Caelum non animum mutant qui trans mare currunt. On Feb 8, 2010, at 11:02 am, Norman Weston wrote: > Recently I have started experiencing issues with Remote Submit. I have > previously had not problems but the issue started about Mid Jan of this > year. > > I am running a Tunnel through PuTTy which hasn't changed and I am calling > tcipunix.scr script which also hasn't changed. > > It looks like the process is timing out when attempting to initiate a SAS > session and here is the error message I get (after turning on TRACE in the > tcipunix.scr): > > TRACE: Type 'sas -dmr -comamid tcp -device grlink -noterminal '; > TRACE: Type '-nosyntaxcheck' lf; > TRACE: Waitfor 'SESSION ESTABLISHED', > TRACE: 90.0 seconds: nosas; > ERROR: Cannot start remote process. > ERROR: Cannot start remote process. > Goodbye > ERROR: Script file interpretation terminated due to error. > NOTE: End of script file trace. > ERROR: A communication subsystem partner link setup request failure has > occurred. > ERROR: recv call failed, lost connection with client. > ERROR: Remote signon to SERVER cancelled. > > To my knowledge my PC SAS license hasn't changed, nor my permissions in > the Unix Environment. Any thoughts on what may be causing this?
From: Norman Weston on 9 Feb 2010 11:55
I can work in Unix just fine. No problems. However there are certain legacy programs from the previous holder of this position that require remote submit and I don't relish the idea of re-coding all of that. |