In Enterprise Guide code doesn't run one time and it runs again when close it and reopen.

[anlyar2050]

Using SAS Enterprise Guide 7.12 in SAS 9.4M2 environment. SAS is on linux and SAS EG 7.1 is on terminal server 2012R2. Here is the thing. Some times even when execute small code it doesn't give output at all when tries to stops it doesn't stop either it has to force kill the process. and again when reopen and execute same code it runs well. It happen even when run large project.  I checked every thing, server performance is good at that time. I am out of options. Can anyone suggest?

[anja]

Hi,

did you check event logs on OS and Metadata Server log to see if there are any errors or

warnings?

Is the Linux Serv available at all time or are there any connectivity issues? Any "freezes" on terminal

server side rather than SAS side.

What does the code you / your users submit do? Does it go "against" SAS datasets, or are you reading from DBMS, or .. etc.

Thanks

Anja

[anlyar2050]

Thanks for the reply.

I checked logs I didn't find any errors.

2017-01-19T13:49:24,586 INFO [17367171] 197786:sasinstall - Client connection 197786 for user v656505 closed.
2017-01-19T13:49:33,558 INFO [17367173] :v656505 - New client connection (4802) accepted from server port 8561 for user v656505. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::ffff:10.64.176.58]:57146 for APPNAME=SAS Enterprise Guide.
2017-01-19T13:49:33,558 INFO [17367173] :v656505 - Request made to cluster SASMeta - Logical Metadata Server (A56DWKW5.AW000001).
2017-01-19T13:49:33,558 INFO [17367173] :v656505 - Redirect client in cluster SASMeta - Logical Metadata Server (A56DWKW5.AW000001) to server SASMeta - Metadata Server (A56DWKW5.AY000001) at saspapp07:8561.
2017-01-19T13:49:44,591 INFO [17367212] :v656505 - New client connection (296173) accepted from server port 8561 for SAS token user v656505. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::ffff:10.64.177.9]:37646 for APPNAME=SAS Workspace Server.
2017-01-19T13:49:44,591 INFO [17367212] :v656505 - Request made to cluster SASMeta - Logical Metadata Server (A56DWKW5.AW000001).
2017-01-19T13:49:44,591 INFO [17367212] :v656505 - Redirect client in cluster SASMeta - Logical Metadata Server (A56DWKW5.AW000001) to server SASMeta - Metadata Server (A56DWKW5.AY000001) at saspapp07:8561.

There are no server connectivity issues, because it will runs good the next time(immediately) when EG reopens. Users query on teradata tables ( user usually won't code they uses query builder and joins in query builder) . But I tried with simple code proc contents on teradata table.

[anja]

Hi

are you working in an environment with clustered Metadata Servers?

The log that you sent, is that the time when the hang happened?

Thanks

Anja

[anlyar2050]

yes. Log is at time when it is hang.

[anja]

Since your Metadata Server is clustered, it could be that the connection is interrupted because a node goes down?

You should have log files for each metadata server in your environment as it is clustered.  Did you check all of them?

[anlyar2050]

It is not grid server it is only stand-alone server.

[anja]

Hi.

I must have misinterpreted your answer yesterday to my question if your metadata server is clustered.

The "Yes" refers to the log not to the clustered metadata server, correct?
My apologies.

As a next step, addressing this matter with Tech Support might be the best way to go.

Best

Anja