Getting an Error while executing SAS

[anare]

Hi Team,

Am getting an error while executing SAS program in SAS Enterprise 7.12

Error :- "An Error occurred executing the workspace job "Weekly". The server is disconnected.

Any suggestion will be much appreciated.

Thanks and Regards,

Naresh

[Kurt_Bremser]

If it is happening in only one code or task, please supply that code.

[anare]

Thanks for the reply.

Its a very big code in SAS Enterprise Guide. Am executing this code from almost 1 year till now I dint get any such type error for this SAS Project.

If I open new project and starting building codes am not getting this error.

[anare]

In a SAS Project I have 3 programs built. However by executing 1st Task in the program only which has approx. 200 line of coding.

After executing this whole program am getting this error

[Kurt_Bremser]

200 lines of code can be posted as attachment (save to a .sas file).

[anare]

Sorry the information's are very confidential

But this code will be executed successfully in SAS Studio only in SAS EG am getting an error.

[Kurt_Bremser]

Then there's nothing we can do to help you. If you are not able to anonymize confidential parts of the code while keeping it's essence (so we can possibly repeat the problem), your only option is SAS technical support (they work under confidentiality rules).

[emrancaan]

Have you tried following ? May be it is to do with large sas log file.

If you submit a job that generates an abnormally large log, SAS Enterprise Guide might display the following error:

An error occurred executing the workspace job "job_name". The server is disconnected.

If SAS Enterprise Guide logging is enabled, the following error is logged.

ERROR SAS.Shared.Exceptions.ServerExceptionHelper [(null)] - MapException() - Mapping error for:
System.Runtime.InteropServices.COMException (0x80010108): The object invoked has disconnected from its clients.
(Exception from HRESULT: 0x80010108 (RPC_E_DISCONNECTED))

Workaround

If the job in question generates the error soon after being submitted, try redirecting the streamed SAS log by adding the following code to the top of the program and submit the program again.

proc printto log="c:\path-on-server\EG.log"; run;

Then, check the SAS log to verify that the program has completed. If it did complete, then redirecting the log is the only current workaround.