on 08-21-2012 9:17 PM
Dears,
After solution manager update from stack 4 to stack 5 i have encountered a SYNTAX error. Does anyone familiar with this eror? I have checked but not much same type of error occured with solution manager 7.1 stack 5. Problem occurs when i start solman_setup and initial configuration "ERROR: Syntax error in program CL_WDR_NOTIFICATION===========CP . (termination: RABAX_STATE)" Below the details of st22 dump.
Kind Regards.
Category ABAP Programming Error
Runtime Errors SYNTAX_ERROR
ABAP Program SISE_POSTPROCESS==============CP
Application Component Not Assigned
Short text
Syntax error in program "SISE_POSTPROCESS==============CP ".
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_SISE_ACT_CUSTOM_NOTE=======CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"SISE_POSTPROCESS==============CP " in include
"SISE_POSTPROCESS==============CM000 " in
line 0:
"The specified type cannot be converted into the target variables."
" "
" "
" "
The include has been created and last changed by:
Created by: "DDIC "
Last changed by: "DDIC "
Error in the ABAP Application Program
The current ABAP program "CL_SISE_ACT_CUSTOM_NOTE=======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 "SISE_POSTPROCESS==============CP
".
You can also perform the syntax check from the ABAP Editor.
Error analysis
The following syntax error was found in the program
SISE_POSTPROCESS==============CP :
"The specified type cannot be converted into the target variables."
" "
" "
" "
SAP kernel....... 720
created (date)... "Jul 8 2012 23:15:28"
create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"
Database version. "SQL_Server_9.00 "
Patch level. 300
Patch text.. " "
Database............. "MSSQL 9.00.2047 or higher"
SAP database version. 720
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0, Windows NT 6.1, Windows NT 6.2"
Memory consumption
Roll.... 0
EM...... 20948960
Heap.... 0
Page.... 237568
MM Used. 19553568
MM Free. 1391824
User and Transaction
Client.............. 001
User................ "SOLMAN_ADMIN"
Language key........ "E"
Transaction......... " "
Transaction ID...... "82C7EBE14B9AF13FAA94E4115BA8F7BC"
EPP Whole Context ID.... "E4115BA8F7BC1EE1BAF8F05349672A94"
EPP Connection ID....... "E4115BA8F7BC1EE1BAF8EFF3F037EA94"
EPP Caller Counter...... 1
Program............. "CL_SISE_ACT_CUSTOM_NOTE=======CP"
Screen.............. "SAPMHTTP 0010"
Screen Line......... 2
Debugger Active..... "none"
Server-Side Connection Information
Information on Caller of "HTTP" Connection:
Plug-in Type.......... "HTTP"
Caller IP............. "10.44.1.41"
Caller Port........... 8000
Universal Resource ID. "/sap/bc/webdynpro/sap/wd_sise_main_app"
Program............. "CL_SISE_ACT_CUSTOM_NOTE=======CP"
Screen.............. "SAPMHTTP 0010"
Screen Line......... 2
Information on Caller ofr "HTTP" Connection:
Plug-in Type.......... "HTTP"
Caller IP............. "100.200.111.111"
Caller Port........... 8000
Universal Resource Id. "/sap/bc/webdynpro/sap/wd_sise_main_app"
Information on where terminated
Termination occurred in the ABAP program "CL_SISE_ACT_CUSTOM_NOTE=======CP" -
in "SHOW_ME".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 1
of the (Include) program "CL_SISE_ACT_CUSTOM_NOTE=======CM00D".
Hi,
please apply the sap note 1733824 Dump in CL_WDR_NOTIFICATION
and also check anyother correction instruction relevant for your release on this Note 1652693 - SAP Solution Manager - Basic functions of 7.1 SP5
Thanks
Jansi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
During initial_setup it asked you to download sap note and implement, this sap note has lots of notes dependency, and hope so you implemented all these notes in sp 04,
now I could say syntax error due to these only,
we faced kind of issue, found that some of the sap notes which are not relevant get implemented by the master note in solman_setup. So I directly gone to SNOTE and checked the objects which are inactive, not implemented properly, I re implement these notes.Deactivate the already implemented sap notes helped to solve these syntax errorsThis only the hint, which helped us.
But your case, I am nt sure, if you get dump for different programs, better contact SAP
Thanks
Jansi
Hello Jansi,
Thanks a lot. We had the same issue after implementing Solution Manager SP5. The snote 1733824 was implemented incorrectly during the master note implementation via solman_setup(SP4). And after the SP5 implemetation We re-implemented it and it resolved the issue.
Thanks,
Raja Sankar.
Hello all,
If the problem still persists, like me in SP7, I have another solution.
Feel free to revert this.
Kind regards,
#solman71today
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Shivani,
I was looking back at my notes, I hope I get it right, pls verify you can implement the following notes and pls update your results over here:
Note 1741470 - WD ABAP ALV error when context changes are dispatched
Note 1776414 - SPPF_PROCESS: Action is processed twice
Note 1820638 - Shared Memory Fehler in Web Dynpro ABAP Notification Service
Note 1621917 - WDA: Notification service dump with dialog menus
Kind regards,
#solman71today
Thanks! After reading an implementing the note 1733824, the transaction WORKCENTER worked perfectly !
Thanks again !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.