Communication problems with BPC - CPIC-CALL: no data received

[Former Member]

Hi.

We'va a communication problems in our BW-BPC system, it seems more a basis issue than a BPC configuration problem, but itu2019s the only component affected.

Version details:

SAP BPC 7.5 NW installed in:

- SAP Netweaver 7.01

- Windows Server 2003

Since last week we've been getting an error when trying to open xml dynamic templates from the BPC clients. Seems that the communication between BPC .net server and bpc abap server is failing, but we don't realize what could be causing this.

Everything worked before last Friday. We're running some archiving test in the system, and SNC configuration for a different project (BO) so we assume one of this two processes could have affected the communications, but still didn't found who and how.

Here are the logs related:

DEV_RFC:

• Trace file opened at 20120306 104437 MET SAP-REL 701,0,117 RFC-VER nU 3 1200935

======> CPIC-CALL: 'ThSAPCMRCV'

no data received

ABAP Programm: SAPMSSY1 (Transaction: )

Called function module: RSDRP_EXECUTE_AT_QUERY_RFC

User: BPC_SYSADMIN (Client: 222)

Destination: NONE (handle: 1, 48680463, {4F549CF9-9F93-57D7-E100-0000AC1A5163})

SERVER> RFC Server Session (handle: 1, 48680463, {4F549CF9-9F93-57D7-E100-0000AC1A5163})

SERVER> Caller host:

SERVER> Caller transaction code: (Caller Program: SAPLRSDRP)

SERVER> Called function module: RSDRP_EXECUTE_AT_QUERY_RFC

Error RFCIO_ERROR_NO_DATA in abrfcpic.c : 3481

CPIC-CALL: 'ThSAPCMRCV'

no data received

Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1829

DEV_WP:

A Tue Mar 6 10:44:37 2012

A RFC 3476 CONVID 48680463

A * CMRC=0 DATA=1 STATUS=2 SAPRC=0 ThSAPCMRCV no data received

A RFC> ABAP Programm: SAPMSSY1 (Transaction: )

A RFC> User: BPC_SYSADMIN (Client: 222)

A RFC> Destination: NONE (handle: 1, 48680463, {4F549CF9-9F93-57D7-E100-0000AC1A5163})

A RFC> Called function module: RSDRP_EXECUTE_AT_QUERY_RFC

A RFC SERVER> RFC Server Session (handle: 1, 48680463, {4F549CF9-9F93-57D7-E100-0000AC1A5163})

A RFC SERVER> Caller host:

A RFC SERVER> Caller transaction code: (Caller Program: SAPLRSDRP)

A RFC SERVER> Called function module: RSDRP_EXECUTE_AT_QUERY_RFC

A *** ERROR => RFC ======> CPIC-CALL: 'ThSAPCMRCV'

no data received

http://abrfcio.c 8175

A *** ERROR => RFC Error RFCIO_ERROR_NO_DATA in abrfcpic.c : 3481

CPIC-CALL: 'ThSAPCMRCV'

no data received

http://abrfcio.c 8175

A RFC 3180 CONVID 48680463

A * CMRC=0 DATA=1 STATUS=2 SAPRC=0 comread no data received

A *** ERROR => RFC Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1829

http://abrfcio.c 8175

Any help would be really appreciated.

Thanks and regards!!

[Former Member]

Hi,

Please create and assign the relevant RFC destinations. Take help of your Basis Admin (if you're not Basis Admin)...

Regards,

Srihari

[Former Member]

Hi

Thanks for the comment, but BPC doesn't use any relevant RFC, just the MDX PARSER and it's created correctly.

No changes regarding RFCs where made that can be causing this problem.

As an update, we've been checking the system and found that in certain situations,

working with RSA1 system start to generate SYSTEM_CORE_DUMPED errors with

program SAPLRSAWB:

posición de cancelación

Termination occurred in the ABAP program "SAPLRSAWB" - in

"RSAWB_CHECKS_BEFORE_AWBSTART".

The main program was "RSAWBN_START ".

In the source code you have the termination point in line 17

of the (Include) program "LRSAWBU05".

Wi this log in the wp developer trace:

D *** ERROR => dySaveDataBindingValue: Abap-Field= >TEXT-SYS< not found
[dypbdatab.c 509]
D *** ERROR => dySaveDataBindingEntry: dySaveDataBindingValue() Rc=-1
Reference= >TEXT-SYS< [dypbdatab.c 429]
D *** ERROR => dySaveDataBinding: dySaveDataBindingEntry() Rc= -1
Reference=>TEXT-SYS< [dypbdatab.c 137]
Y *** ERROR => dyPbSaveDataBindingForField: dySaveDataBinding() Rc= 1
[dypropbag.c 641]
Y *** ERROR => ... Dynpro-Field= >DISPLAY_SY_SUBRC_TEXT< [dypropbag.c
642]
Y *** ERROR => ... Dynpro= >SAPLSTPDA_CARRIER< >0700< [dypropbag.c 643]
D *** ERROR => dySaveDataBindingValue: Abap-Field= >TEXT-SYS< not found
[dypbdatab.c 509]
D *** ERROR => dySaveDataBindingEntry: dySaveDataBindingValue() Rc=-1
Reference= >TEXT-SYS< [dypbdatab.c 429]
D *** ERROR => dySaveDataBinding: dySaveDataBindingEntry() Rc= -1
Reference=>TEXT-SYS< [dypbdatab.c 137]
Y *** ERROR => dyPbSaveDataBindingForField: dySaveDataBinding() Rc= 1
[dypropbag.c 641]
Y *** ERROR => ... Dynpro-Field= >DISPLAY_FREE_VAR_TEXT< [dypropbag.c
642]
Y *** ERROR => ... Dynpro= >SAPLSTPDA_CARRIER< >0700< [dypropbag.c 643]

This issue is happening to be more a system/database problem than a

communication one.

Regards.

Edited by: Armando Rodriguez Castro on Mar 6, 2012 4:37 PM

Edited by: Armando Rodriguez Castro on Mar 6, 2012 4:38 PM