topic How to clean log is SAS EG rather than close and open the program again in SAS Programming

How to clean log is SAS EG rather than close and open the program again

Phil_NZ — Thu, 18 Feb 2021 21:54:20 GMT

Hi all,

Normally when I face this error from SAS EG, I normally turn off SAS EG then turn on again.

Error: Integration technologies failed to retrieve the log. [Error] Request failed due to an exception.

From my nice understanding, it is just the log problem itself, I am wondering is there anyway to deal with this problem rather than close and open the SAS EG again (because when I turn off SAS EG and open it again, this error disappears)?

Warm regards.

Re: How to clean log is SAS EG rather than close and open the program again

ChrisNZ — Fri, 19 Feb 2021 01:35:54 GMT

I've never seen this.

It should never happen.

Your best bet is tech support.

Re: How to clean log is SAS EG rather than close and open the program again

Garnett — Mon, 22 May 2023 16:52:02 GMT

I get this message while running SAS EG. No subsequent action is possible until SAS restarts. Other program files work as expected.

Re: How to clean log is SAS EG rather than close and open the program again

SASKiwi — Mon, 22 May 2023 20:47:46 GMT

Are you wanting to fix this problem or are you just commenting on the original post?

Re: How to clean log is SAS EG rather than close and open the program again

Garnett — Thu, 25 May 2023 14:39:43 GMT

This solution from Bill at SAS Tech Support fixed the issue:

---------------------------------------------------------------------------------------------------------

For this one program, add PROC PRINTTO code to write the log to disk to see if that avoids the issue for this particular case.

Example code:

proc printto log=" within quotes specify the directory and filename to write the log to disk on the SAS server";

run;

Your proc iml code goes next...

Re: How to clean log is SAS EG rather than close and open the program again

thaismartins — Tue, 19 Aug 2025 19:31:50 GMT

Hi, were you able to resolve this log error?

I'm having the same issue, and SAS support couldn't resolve it. Disconnecting SASApp makes it disappear, but this is a problem because it doesn't release the execution logs.