Symptom
In this scenario, the following symptoms are present:
- Job E2E BI HOUSEKEEPING runs for very long periods
- In the Spool list of the job E2E BI HOUSEKEEPING it is possible to see entries with very long runtime and the following error:
Errors ( 519 ) occured during transfer! See SLG1 in BI client (object: BW_PROCES
-
In transaction SLG1, it is possible to see errors for the cubes presenting the previous symptom. The error shown in SLG1 is the following:
Error checking syntax (RC = E):
Error occurred when starting the parser: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' -
In SM59 under "TCP/IP connections", the RFC "MDX PARSER" will present the following error for a connection test:
Error Details timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456 Timeout dur
Error Details ERROR: timeout during allocate
Read more...
Environment
- SAP Solution Manager 7.1
- SAP Solution Manager 7.2
Product
Keywords
E2E BI HOUSEKEEPING , MDX PARSER , SM59 , Target Infocube , Source Infocube ,
0MSS_C02D , 0MSS_C02H , 0MSS_C01D , 0MSS_C01H , 0DBH_C01D , 0DBH_C01H ,
database analysis
Error checking syntax (RC = E):
Error occurred when starting the parser: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
Errors ( 519 ) occured during transfer! See SLG1 in BI client (object: BW_PROCES
Error Details timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456 Timeout dur
Error Details ERROR: timeout during allocate , KBA , SV-SMG-DIA-SRV-EFW , Extractor Framework , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.