topic Re: Error in SAS Jobs in Administration and Deployment

Error in SAS Jobs

SundeepK — Mon, 20 Jun 2016 09:39:17 GMT

Hi All,

We have scheduled Data Integration studio jobs in SMC and they are running daily well. Suddenly today jobs failed due to below error:

ERROR: The Bridge Protocol Engine Socket Access Method was unable to connect to host metadata, port 8561.
ERROR: The TCP/IP tcpSockConnect() support routine failed with error 10060 (The connection has timed out.).

When I checked SAS services, they are up and running fine. And, if I run manually it is working fine.

Could anyone pls guide me what does the above error means?

Thanks for your help in advance..!

Regards,

Sundeep

Re: Error in SAS Jobs

Kurt_Bremser — Mon, 20 Jun 2016 10:07:29 GMT

The environment where your batch runs seems to be different from the one where you are doing your manual tests.

Maybe something happened to (personal) firewall settings?

And please supply some information about your SAS landscape (server operating system(s), client access, affected userID's etc.)

Re: Error in SAS Jobs

RahulG — Mon, 20 Jun 2016 10:12:36 GMT

See the resolution in the below link.

http://support.sas.com/kb/14/819.html

Do check if your job uses Transpose transformation. It might be trying to UPDATE TABLE METADATA and causing issue.

Re: Error in SAS Jobs

SundeepK — Mon, 20 Jun 2016 10:22:02 GMT

Hi,

Thanks for your prompt reply..!

Server OS: Windows Server 2008 R2

client: DI studio

User ID: sasdemo

After the execution of jobs, logs will be generated in particular folder. Last week, we had the similar problem. And, the following day jobs went well.

That error will occur twice in a week. There is no change in firewall setting.

Regards,

Sundeep

Re: Error in SAS Jobs

RahulG — Mon, 20 Jun 2016 10:30:56 GMT

Is it happening for all jobs or for particular one job?

Re: Error in SAS Jobs

Kurt_Bremser — Mon, 20 Jun 2016 10:31:17 GMT

Do all jobs fail at a given time, or just some of the jobs?

You might have a condition where the server becomes congested because of a load of jobs running in parallel, and the metadata server therefore being too slow to respond.

Re: Error in SAS Jobs

SundeepK — Mon, 20 Jun 2016 11:35:08 GMT

Hi Kurt,

Jobs are running in a sequential order. Assume jobs are scheduled in the below manner:

a-->b--->c--->d-->e-->f-->g

At point 'e', the job is getting failed.

Re: Error in SAS Jobs

Kurt_Bremser — Mon, 20 Jun 2016 11:39:24 GMT

Is this behaviour repeatable?

And do jobs "a" to "d" need to be finished before "e" starts?

Re: Error in SAS Jobs

SundeepK — Mon, 20 Jun 2016 12:38:30 GMT

Yes

##- Please type your reply above this line. Simple formatting, no
attachments. -##

Re: Error in SAS Jobs

Kurt_Bremser — Mon, 20 Jun 2016 12:56:04 GMT

Hmm. Could you post the complete log of the step that fails?

Re: Error in SAS Jobs

RahulG — Tue, 21 Jun 2016 04:04:32 GMT

I think this problem is related to the particular job e.

As I said earlier job e is trying to update table metadata. Check with developer of this job.

Re: Error in SAS Jobs

SundeepK — Thu, 23 Jun 2016 04:05:12 GMT

ERROR: SQL View WORK.WSFQC2D2 could not be processed because at least one of the data sets, or views, referenced directly (or
indirectly) by it could not be located, or opened successfully.

Re: Error in SAS Jobs

Kurt_Bremser — Thu, 23 Jun 2016 04:43:52 GMT

This is not the complete log, just the ERROR messages. We need to see the code that caused the messages.

Re: Error in SAS Jobs

LinusH — Thu, 23 Jun 2016 05:17:47 GMT

Complete means including the SAS code.