Summary
Symptom
If these steps are not successful, try to start the MDX parser as a local RFC server. Carry out the following steps for the Windows platform:
The MDX execution terminates with error message BRAINOLAPAPI 011:
Error occurred when starting the parser: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
Error occurred when starting the parser: timeout during allocate / CPIC-CALL: 'ThSAPCMRCV'
A connection test of the Remote Function Call (RFC) destination MDX PARSER in transaction SM59 is unsuccessful.
The system may also issue this error message in SAP BusinessObjects Interactive Analysis (WebI) if data from a multidimensional data source should be read via a universe.
Other termsThe system may also issue this error message in SAP BusinessObjects Interactive Analysis (WebI) if data from a multidimensional data source should be read via a universe.
011(BRAINOLAPAPI), BRAINOLAPAPI011, BRAINOLAPAPI 011, MDX PARSER, data refresh, BOBJ, Business Objects, Universe Designer, Web Intelligence, WebI
Reason and Prerequisites
The MDX parser is an executable program that is installed with the kernel. The file name is mdxsvr.exe.
The communication between ABAP and MDX parser is carried out in binary format and the MDX parser works internally with UTF-8. Therefore, there is no special UNICODE version of the MDX parser and so the current NON-UNICODE RFC library is required.
SolutionThe communication between ABAP and MDX parser is carried out in binary format and the MDX parser works internally with UTF-8. Therefore, there is no special UNICODE version of the MDX parser and so the current NON-UNICODE RFC library is required.
Carry out the following steps:
- Read SAP Note 581509. This SAP Note contains general information about the "timeout during allocate" error message.
- Implement the current version of librfc32.dll (not librfc32u.dll) on ALL application servers. You can download the current librfc32.dll file from SAP Service Marketplace:
http://service.sap.com
-> SAP Support Portal
-> Software Download
-> Download
-> Support Packages and Patches
-> Entry by Application Group
-> SAP NetWeaver
-> SAP NetWeaver
-> SAP NW 2004s
-> Entry by Component
-> Application Server ABAP
-> .. .
To determine the most current version of librfc32. dll, see Note 413708.
- The file librfc32.dll can be installed several times. Replace all versions. Note 336693 describes how to replace this DLL on the Windows platform.
- If file librfc32.dll is not contained in the same directory as mdxsvr.exe, it must be in one of the search path directories (environment variable PATH). The MDX parser (program mdxsvr) is located in a directory of the application server: /usr/sap/<SID>/sys/exe. To check whether the newly installed librfc32.dll is contained in the path, carry out the following steps on the Windows platform:
- Use the command CMD to open a command line.
- Execute the command SET.
- Check whether the environment variable PATH contains a directory that contains librfc32.dll (for example, <Windows>\System32).
- In transaction SM59, check whether the setting "Communication Type with Target System" ("MDMP & Unicode" tab) is set to "Non-Unicode" for the RFC destination MDX PARSER.
If these steps are not successful, try to start the MDX parser as a local RFC server. Carry out the following steps for the Windows platform:
- Use the command CMD to open a command line.
- Switch to the directory that contains mdxsvr.exe (/usr/sap/<SID>/sys/exe).
- Start the MDX parser as a server using the following command: mdxsvr -amdxparser -g<host> -x<gateway> -t (replace <host> and <gateway> accordingly).
If the program can be started successfully, the functions should not be impaired.
If a test of the RFC destination still results in an error, enter the complete path for the file mdxsvr.exe in the "Program" field (for example, j:\usr\sap\BWP\SYS\exe\run\mdxsvr). Then check whether the test still results in an error. If the test is successful this time, it indicates that a PATH variable is incomplete.
Important: If there should be error messages with regard to the MDX parser from BW 7.30 on (for example, in the system log), even though the statement can be parsed successfully, refer to the SAP Notes 1572695 and 1666816.
If a test of the RFC destination still results in an error, enter the complete path for the file mdxsvr.exe in the "Program" field (for example, j:\usr\sap\BWP\SYS\exe\run\mdxsvr). Then check whether the test still results in an error. If the test is successful this time, it indicates that a PATH variable is incomplete.
Important: If there should be error messages with regard to the MDX parser from BW 7.30 on (for example, in the system log), even though the statement can be parsed successfully, refer to the SAP Notes 1572695 and 1666816.
Header Data
| Release Status: | Released for Customer |
| Released on: | 13.02.2012 08:51:49 |
| Master Language: | German |
| Priority: | Recommendations/additional info |
| Category: | Installation information |
| Primary Component: | BW-BEX-OT-MDX MDX,OLAP-BAPI,OLE DB for OLAP |
| Secondary Components: | FIN-SEM-CPM Corporate Performance Monitor |
| FIN-SEM-CPM-BSC Balanced Scorecard | |
| BW-EI-RTR Retraction | |
| BW-EI-APD Analysis Process Designer | |
| BI-BIP-IK Integration; Integration kits for SAP, Baan, PeopleSoft, Sie | |
| BI-RA-WBI Web Intelligence | |
| BI-RA-WBI-JRP Web Intelligence applet Java report panel, query panel | |
| BI-BIP-IDT Information design tool | |
| BI-BIP-UDT Universe Design Tool | |
| BI-BIP-CS Connection Server |
Affected Releases
Release-Independent
Related Notes
No comments:
Post a Comment