BusinessObjects Board

Error number <50664>

dataservices performance
#1

We’ve been randomly getting a lot of the following error sequence lately:

Error number <50664> occurred. There is no additional description.
Cannot close pipe, due to error .
The data flow <DF_FinRecordCategory_SAP> process could not communicate with the job process.

And then it dies. I haven’t been able to find anything online about this. Anyone know?

craiggsmith (BOB member since 2009-06-01)

#2

Can you post the error message from error log fully?

ganeshxp :us: (BOB member since 2008-07-17)

#3

Sure; FWIW it’s from a RapidMart.

(14.0) 05-07-13 00:57:25 (W) (5672:9504) INZ-050664: |Dataflow DF_FinRecordType_SAP
Error number <50664> occurred. There is no additional description. Notify Customer Support. Message parameters are: <31> .
(14.0) 05-07-13 00:57:25 (E) (5672:9504) SYS-050605: |Dataflow DF_FinRecordType_SAP
Cannot close pipe, due to error .
(14.0) 05-07-13 00:57:25 (E) (5672:9504) RUN-050408: |Dataflow DF_FinRecordType_SAP
The data flow <DF_FinRecordType_SAP> process could not communicate with the job process. For details, see previously logged
error <50605>.
(14.0) 05-07-13 00:57:25 (E) (9704:4956) RUN-050406: |Session Job_Dims_Common_GL|Work flow WF_Load_Common_GL_DIMS_SAP|Work flow C_FinRecordType_SAP|Data flow DF_FinRecordType_SAP
Data flow <DF_FinRecordType_SAP> received a bad system message. Message text from the child process is < >. The process
executing data flow <DF_FinRecordType_SAP> has died abnormally. For NT, check errorlog.txt. For HPUX, check stack_trace.txt.
Also, notify Technical Support.
(14.0) 05-07-13 00:57:25 (9704:4956) RUN-050409: |Session Job_Dims_Common_GL|Work flow WF_Load_Common_GL_DIMS_SAP|Work flow C_FinRecordType_SAP

craiggsmith (BOB member since 2009-06-01)

#4

It sounds like a different error in which the Dataflow has spawned a process and it eventually loses the ability to communicate with that child process.

The usual solutions:

  1. Disable the “Run as a separate process” options
  2. Find a way to make the Dataflow run faster so it doesn’t take so long. Often this can be done by simplifying what the Dataflow does or perhaps splitting the Dataflow into multiple Dataflows.
  3. Avoid operations that accumulate large amounts of data on the job server. This means you need to eliminate or push down to the database operations such as DISTINCT, ORDER BY, GROUP BY, etc.

eganjp :us: (BOB member since 2007-09-12)

#5

Thanks, I’ll look at those options; I don’t think we have “run as separate process” set anywhere.

We are looking at upgrading to 4.0 SP3 Patch 3 (we’re on patch 0); we ran everything today with no failures but since this is sporadic that’s not conclusive.

craiggsmith (BOB member since 2009-06-01)

#6

I hope you are trying to fetch data from SAP and using some file transfer method. Sometimes, if it is a high record count extraction, by the time the abap flow is done execution and the output is written into .dat file, the process which started this abap is not longer available. There could be many reasons like loss of connectivity between app server and the sap app server, could something cause the process to stop. This type of issues are not encountered regularly and cant be re-created. Network admins will have to answer your queries.

SantoshNirmala :india: (BOB member since 2006-03-15)

#7

Thanks, good to know. Yes, we are data transfer via files though.

We upgraded to 4.0 SP3 Patch 3 and it seems to have helped, but we’ll have to do more testing.

Edit: Had another error last night. This one had a new piece of information in the log that we haven’t seen before:

Cannot close pipe, due to error <Overlapped I/O operation is in progress.>.

craiggsmith (BOB member since 2009-06-01)

#8

Update: I submitted a ticket to SAP and they felt that it had something to do with our ABAP program calls to SAP and suggested we look at the SAP logs. We found corresponding errors that indicated the CPIC buffer was filling up, which is what is used to communicate with external systems, and subsequent connection errors to the data services server. However, we increased the buffer size but still got an error this weekend, and they couldn’t find any errors at that time. So still looking.

craiggsmith (BOB member since 2009-06-01)

#9

We increased the CPIC timeout setting from 20s to 60s and that seems to have solved our problem.

craiggsmith (BOB member since 2009-06-01)

#10

I hit the same problem too. Can you tell me where to set the CPIC time?

wingyanw (BOB member since 2014-01-08)

#11

Please go through below link for setting the CPIC time.
http://wiki.scn.sap.com/wiki/display/ABAPConn/CPIC+Return+Code+679+-+Transaction+Program+not+Registered

pnr6kor (BOB member since 2014-05-14)