RRMX doesn't start a BEx, I would like to have BEx (3.5)

Question

Hi all,
in our company, the roll out of SAP GUI 7.2 with 3.5 Add-On has started (but different patch levels; some have patch level 5, others became patch level 6). The upgraded GUIs had been SAP GUI 6.4 and 7.1. Our BI System is an SAP NetWeaver BW 7.00 with SAPKW70026, SAPKB70024 and kernel 700 patch 297. We are still using 3.5 Queries/Workbooks.
After installing SAP GUI 7.2 on the customer's client, they want to start their queries/workbooks via the user menu in sap gui. Without access, but different behaviour:
- sometimes we get the error code "run-time error 9. subscript out of range"
- sometimes the user gets the logon menu and has to choose the system
Trying to use the transaction rrmx, different behaviour appears depending on the configuration in TA rrmx_cust:
- start relevant version for workbook opened
  starts bex 7; sometimes with logon menu to choose the system
- always start sap 3.x version of BEx Analyzer
  no BEx will start. Only the message xxx bytes transferred, codepage 1160 apperas in the status bar.
- always start sap netweaver version of bex analyzer
  starts bex 7
Which setting must be made or changed to start the bex 3.5 version without getting an error (and without getting the logon-window)?
Thank you for your help.

Answer 1

Dear Arvind,
thank you for your help.
I checked the mentioned notes, found and checked some more notes:
- 1498947
- 1471630
- 1543671
A summary of the hints in the notes and our system configuration:
backend
- note: SAPKW70025; system: SAPKW70026
- note: SAPKB70014; system SAPKB70024
- note: kernel 7.00 patch 129; kernel 7.00 patch 297
- note: profil "default": login/accept_sso2_ticket = 1; login/accept_sso2_ticket = 2
  system: profil "instance": login/accept_sso2_ticket = 1; login/accept_sso2_ticket = 2
- note: SAPLOCALHOSTFULL full qualified; system: SAPLOCALHOSTFULL full qualified
frontend:
- system: sap gui 7.2 with 3.5 components, front end patch 5
- note: frontend support package 200 bi720sp2_200-10004472.exe; system frontend support package 402 bi720sp04p_402-20006596.exe
  --> bi components: 7.20 patch 402
  --> bw 3.5 components: 3.50 patch 0
Unfortunately, the problem still occurs.
Our SAP basis implemented the login/... parameters in the instance profile, not in the default profile. Can this be the problem (is there a fix query on default??).
Regards,
Dieter