MOPZ gives RABAX_STATE error

[former_member360410]

When I am trying to open the existing maintenance optimiser transaction

or trying to go inside a already created one I am receiving the

following error...

Completely unable to understand what is the problem....

Please help

"Error when processing your request

What has happened?

The URL

http://hssamums010.in.holcim.net:8000/sap/bc/webdynpro/sap/wda_mopz_plan was not called due to an error.

Note

The following error text was processed in the system HSD : Syntax error

in program /TMWFLOW/CL_MO_CONTEXT_SDSM===CP .

The error occurred on the application server HSSAMUMS010_HSD_00 and in

the work process 0 .

The termination type was: RABAX_STATE

The ABAP call stack was:

Method: GET_CRM_CONTAINER of program /TMWFLOW/CL_MO_CRM_FACTORY====CP

Method: GET_CRM_OBJECT of program /TMWFLOW/CL_MO_CRM_FACTORY====CP

Method: CONSTRUCTOR of program /TMWFLOW/CL_MO_CRM_ACCESS=====CP

Method: GET_CRM_INTERFACE of program /TMWFLOW/CL_MO_CRM_FACTORY====CP

Method: CONSTRUCTOR of program CL_MO_CRM_ADAPTER=============CP

Method: CONSTRUCTOR of program CL_MO_CONTROLLER==============CP

Method: HANDLEDEFAULT of program /1BCWDY/7WJL85BEG6RQW1UBNSP0==CP

Method: HANDLEDEFAULT of program /1BCWDY/7WJL85BEG6RQW1UBNSP0==CP

Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of

program /1BCWDY/7WJL85BEG6RQW1UBNSP0==CP

Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_IF_VIEW=====CP

What can I do?

If the termination type was RABAX_STATE, then you can find more

information on the cause of the termination in the system HSD in

transaction ST22.

If the termination type was ABORT_MESSAGE_STATE, then you can find more

information on the cause of the termination on the application server

HSSAMUMS010_HSD_00 in transaction SM21.

If the termination type was ERROR_MESSAGE_STATE, then you can search

for more information in the trace file for the work process 0 in

transaction ST11 on the application server HSSAMUMS010_HSD_00 . In some

situations, you may also need to analyze the trace files of other work

processes.

If you do not yet have a user ID, contact your system administrator.

Error code: ICF-IE-http -c: 200 -u: SOLMAN_ADMIN -l: E -s: HSD -i:

HSSAMUMS010_HSD_00 -w: 0 -d: 20111125 -t: 160207 -v: RABAX_STATE -e:

SYNTAX_ERROR

HTTP 500 - Internal Server Error

Your SAP Internet Communication Framework Team

"

Regards

Soumen.

[Paul_Babier]

Hello,

Was there a dump created in ST22 - as that will have much more relevemt information on the exact error.

RABAX_STATE error can be very generic and not tell much.

Also, were there error in SM21.

Your initial post is making refernce to ST22 and Sm21, but you have provided no information, even if it is to say there was no dump or logs at the time this error occured.

I suspect there would be, and that information can help lead to a solution.

Can you please advise if there were any Dumps in ST22 or logs entreis in SM21, and if so can you share them?

Regards,

Paul

[former_member360410]

Hi Paul,

The ST 22 shows some syntax error on some classes, according to I checked the syntax error, but ABAP editor says there are no sysntax error. all the objects are in activated postion .....Here are the error for your reference..

Short text

Syntax error in program "/TMWFLOW/CL_MO_CONTEXT_SDSM===CP ".

What happened?

Error in the ABAP Application Program

The current ABAP program "/TMWFLOW/CL_MO_CRM_FACTORY====CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program

"/TMWFLOW/CL_MO_CONTEXT_SDSM===CP " in include

"/TMWFLOW/CL_MO_CONTEXT_SDSM===CM004 " in

line 76:

"Incorrect nesting: Before the statement "ENDMETHOD", the structure int"

"roduced by "IF" must be concluded with "ENDIF". -"

" "

" "

The include has been created and last changed by:

Created by: "SAP "

Last changed by: "SOUMEN "

Error in the ABAP Application Program

The current ABAP program "/TMWFLOW/CL_MO_CRM_FACTORY====CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

What can you do?

Please eliminate the error by performing a syntax check

(or an extended program check) on the program "/TMWFLOW/CL_MO_CONTEXT_SDSM===CP

".

You can also perform the syntax check from the ABAP Editor.

If the problem persists, proceed as follows:

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Regards,

Soumen

[sunny_pahuja2]

Hi,

What is the version of solution manager ? Have you done any changes recently in the system ?

Thanks

Sunny

[former_member360410]

Solman 7.1. Latest updated SAP TAO support packs. ST-TAO 200 SP1 to SP6 and the relevant dependancies.

In short the system status is

Installed Software Components

Software Component Release Level Highest Supp. Pack. Software Component Description

SAP_ABA 701 0007 SAPKA70107 Cross-Application Component

SAP_BASIS 701 0007 SAPKB70107 SAP Basis Component

PI_BASIS 701 0006 SAPK-70106INPIBASIS Basis Plug-In

ST-PI 2008_1_700 0004 SAPKITLRD4 SAP Solution Tools Plug-In

CRMUIF 500 0003 SAPK-50003INCRMUIF CRMUIF for Solution Manager

SAP_BW 701 0006 SAPKW70106 SAP Business Warehouse

SAP_AP 700 0019 SAPKNA7019 SAP Application Platform

BBPCRM 500 0016 SAPKU50016 BBPCRM

BI_CONT 704 0004 SAPK-70404INBICONT Business Intelligence Content

CPRXRPM 400 0015 SAPK-40015INCPRXRPM SAP xRPM/cProjects/cFolders 4.00 (ABAP)

ST 400 0025 SAPKITL435 SAP Solution Manager Tool

ST-A/PI 01N_700SOL 0000 - Application Servicetools for SolMan 7.0-

ST-ETP 100 0000 - Extended tracability package

ST-ICO 150_700 0022 SAPK-1507MINSTPL SAP Solution Manager Implementation Cont

ST-SER 701_2010_1 0001 SAPKITLOS1 SAP Solution Manager Service Tools

ST-TAO 200 0006 SAPKITLEF6 SAP Test Acceleration and Optimization (Solution M

Regards,

[sunny_pahuja2]

Hi,

Have you executed solman_setup t-code successfully ?

Thanks

Sunny

[Former Member]

Hi,

solman 7.1 ?? you mean solman 7.0 EHP 1??

As per ST component your solman should be 7.01 SPS25.

So, have you checked this note? Note 1485385 - MOpz: Collective corrections 25

And as sunny suggested above, have you performed the Basic Configuration in solman_setup?? In particular u should install the central note, and if you already did check if there's a new version of the central note.

Cheers,

Diego.

[former_member360410]

Hi Diego and Sunny,

There is two part to it.....

The notes implemented in my system are as follows. and this has happened when I was told to update my SAP-TAO, which is acttually for SAP Tao client to work on 64 bit windows.

The thing were absolutely fine before I went for TAO. ..(Dont please aske me to revert back with backup - that is the easiest solution and probably then I would never post it on forum)

SoftwareComponent Support Pack ImportedOn Description

SAP_ABA 701 SAPKA70107 25.11.2011 ABA Support Package 0007 for 7.01

SAP_Basis 701 SAPKB70107 25.11.2011 Basis Support Package 0007 for 7.01

SAP_BW , 701 SAPKW70106 25.11.2011 BW Support Package 06 for 7.01

BBPCRM, 500 SAPKU50016 25.11.2011 Support Package 16 for SAP CRM 5.0

ST , 400 SAPKITL434 25.11.2011 ST 400: Patch 0024, CRT for SAPKU50016

ST , 400 SAPKITL435 25.11.2011 ST 400: Patch 0025, CRT for SAPKB70107

ST-SER , 701_2010_1 SAPKITLOS1 25.11.2011 ST-SER 701_2010_1: SP 0001

ST-TAO , 200 SAPKITLEF4 25.11.2011 ST-TAO 200: SP 0004

ST-TAO , 200 SAPKITLEF5 25.11.2011 ST-TAO 200: SP 0005

ST-TAO , 200 SAPKITLEF6 25.11.2011 ST-TAO 200: SP 0006

PI_Basis 701 SAPK-70105INPIBASIS 24.11.2011 PI_BASIS Support Package 05 for 7.01

PI_Basis 701 SAPK-70106INPIBASIS 24.11.2011 PI_BASIS Support Package 06 for 7.01

SAP_BW , 701 SAPKW70105 24.11.2011 BW Support Package 05 for 7.01

SAP_AP , 700 SAPKNA7017 24.11.2011 SAP_AP 700: Support Package 0017

SAP_AP , 700 SAPKNA7018 24.11.2011 SAP_AP 700: Support Package 0018

SAP_AP , 700 SAPKNA7019 24.11.2011 SAP_AP 700: Support Package 0019

ST-TAO , 200 SAPKITLEF1 23.11.2011 ST-TAO 200: SP 0001

ST-TAO , 200 SAPKITLEF2 23.11.2011 ST-TAO 200: SP 0002

ST-TAO , 200 SAPKITLEF3 23.11.2011 ST-TAO 200: SP 0003

Here are the details of the notes those are already implemented.

Note number Short text Appl. component Processing Status Implementation Stat.

1326953 BP_GEN: Form of addr and bus addr not transferred correctly SV-SMG-SUP In Process Completely implemented

1405878 SAP Solution Manager: Basic functions: SP22 to SP26 SV-SMG In Process Completely implemented

1438476 Partner inheritance for partner determination failing CRM-MD-INB In Process Completely implemented

1462334 POWL: POWL result table not updated on action BC-MUS-POW In Process Completely implemented

1464017 POWL Selection Modes for ALV BC-MUS-POW In Process Completely implemented

1465370 POWL: Selection Crietria issues BC-MUS-POW In Process Completely implemented

1468591 SAP Solution Manager: Basic functions: SP25 - SP27 SV-SMG In Process Completely implemented

1472079 POWL: Next button BC-MUS-POW In Process Completely implemented

1472659 POWL: Updates BC-MUS-POW In Process Completely implemented

1482211 Issue could not be created: MISSING_PARAMETER SV-SMG-SDG In Process Completely implemented

1485385 MOpz: Collective corrections 25 SV-SMG-MAI In Process Completely implemented

1491227 Adjustments to service content update from ST 700 SP 23 SV-SMG-SER In Process Completely implemented

1500053 POWL : Hierarchy Collapse On lead Selection BC-MUS-POW In Process Completely implemented

1503456 POWL: Corrections related to lead selection BC-MUS-POW In Process Completely implemented

1507671 SMSY: Installed product versions are overwritten SV-SMG-SYS In Process Completely implemented

1510178 Infocubes remain in loading mode after Housekeeping timeout SV-SMG-DIA In Process Completely implemented

1512053 POWL: Accessibility corrections BC-MUS-POW In Process Completely implemented

1513289 EWA Sessions for non Netweaver systems are not processed SV-SMG-OP In Process Completely implemented

1513485 SOLMAN_SETUP : Authorizations and access issues SV-SMG-INS In Process Completely implemented

1519709 SD: Invisible session link in Japanese log-on SV-SMG-SVD In Process Completely implemented

1523819 POWL: Selection criteria exceeds 45 char length BC-MUS-POW In Process Completely implemented

1526261 POWL: Admin query changed message and Restore Admin Settings BC-MUS-POW In Process Completely implemented

1529251 EarlyWatch Alert ALERTS are not sent to SAP SV-SMG-OP In Process Completely implemented

1529869 SOLMAN_SETUP: dump on click on 'Save' button SV-SMG-INS In Process Completely implemented

1534074 POWL Dump happens when fire POWL do_refresh event BC-MUS-POW In Process Completely implemented

1536589 POWL: selection getting disappeared after clicking Apply btn BC-MUS-POW In Process Completely implemented

1537309 System crash when you save a solution SV-SMG-OP In Process Completely implemented

1538765 POWL ->Add interface method to get detail comp BC-MUS-POW In Process Completely implemented

1538950 Random scheduling of background jobs in SOLMAN_SETUP SV-SMG-INS In Process Completely implemented

1540720 ICM parameters are not transferred by RZ70 BC-CCM-SLD In Process Completely implemented

1541306 POWL - Detail Component Is not updated Properly BC-MUS-POW In Process Completely implemented

1542016 Project authorization required in STWB_WORK SV-SMG-TWB-PLN In Process Completely implemented

1542831 BP_GEN does not add a system user to role employee SV-SMG-SUP In Process Completely implemented

1544202 Data missing in Incident Management BI Reporting SV-SMG-SUP-REP In Process Completely implemented

1546204 POWL - Category creation and deletion Issues BC-MUS-POW In Process Completely implemented

1546812 POWL - Dump when stardard query is made inactive BC-MUS-POW In Process Completely implemented

1548084 Closed sessions are displayed SV-SMG-SVD-SWB In Process Completely implemented

1548530 MOpz: Collective Correction 26 SV-SMG-MAI In Process Completely implemented

1559286 CCMS: Grey CCMS alert in email BC-CCM-MON In Process Completely implemented

1560168 Text contents lost on saving SV-SMG-SVD-SWB In Process Completely implemented

1560988 Errors when creating a solution via workcenter SV-SMG-SYS In Process Completely implemented

1573809 Prerequisite check fail for ST-A/PI SV-SMG-DIA-SRV-CHK In Process Completely implemented

1590226 MOpz Collective Correction 27 SV-SMG-MAI In Process Completely implemented

-

---

[Former Member]

Hi,

I guess the line 76 should appear as commented. Check correction instruction 920072 of note Note 1485385 - MOpz: Collective corrections 25.

Have you checked the PDF attached to the note??

Cheers,

Diego.

[former_member360410]

Hi Diego,

I do have checked the PDF, there is no deactivated part at any point on the class and associated objects. That is why I am really astonished. Shall I go for higher level of service pack for ST? But now that is also a problem for me as I can not approve them. For approvig I do need to open another ticket to SAP.

Regards,

Soumen

[Former Member]

Soumen,

It's really weird. One last thing I could say is to check RTCCTOOL -> Procedure after Add-on an Upgrade. I guess you already did. The point is, I checked in my solman and this part of the code is commented (SPS27).

Anyway, It's not recommended to change ST only, You'll lost the stack sync. Instead of call sap for approve a download, call them to solve this syntax error.

Good Luck,

Diego.