topic Re: Conversation termination; status=1. in SAS Programming

Conversation termination; status=1.

margalits1 — Thu, 01 Feb 2024 09:54:21 GMT

Hello, could you please help me?

I get the following error after an sql command in SAS. I use WRDS data:

ERROR: Conversation termination; status=1.
ERROR: A link must be established by executing the SIGNON command before you can communicate with
WRDS.
ERROR: Remote submit to WRDS canceled.

I have already tried the following solutions (each apart):

1. Adding-

rsubmit;

-set CONNECTKEEPALIVE 15;

2. Setting the timeout in sasv9.cfg to max.

This is the command I am trying to run, Perhaps you might have any ideas how to alter it?

proc sql;

create table firms_list as

select * from comp2 c

where exists(

select * from firms_list a

where c.year between a.year and a.year+2 and c.gvkey = a.gvkey);

quit;

run;

Will appreciate any ideas how to solve this problem. Thank you in advance.

Re: Conversation termination; status=1.

rudfaden — Thu, 01 Feb 2024 12:07:42 GMT

Are you signed on to a remote server?

Re: Conversation termination; status=1.

Patrick — Thu, 01 Feb 2024 13:47:53 GMT

Have you already seen this problem note?

Problem Note 64599: "ERROR: Conversation termination; status=1" occurs when multiple remote SAS® sessions are running concurrently using SAS/CONNECT®

Re: Conversation termination; status=1.

margalits1 — Fri, 02 Feb 2024 09:54:02 GMT

Yes- the WRDS server

Re: Conversation termination; status=1.

margalits1 — Fri, 02 Feb 2024 13:27:37 GMT

Hi, I get a notice that this hotfix is already installed on Sas Deployment Manager .

I am not sure that it is relevant in the first place, since I am not trying to run *multiple* processes, but a single command.

Re: Conversation termination; status=1.

Patrick — Sat, 03 Feb 2024 01:59:32 GMT

@margalits1 wrote:

Hi, I get a notice that this hotfix is already installed on Sas Deployment Manager .

I am not sure that it is relevant in the first place, since I am not trying to run *multiple* processes, but a single command.

I guess you best contact SAS Tech Support directly with this issue.