Hi,
we had created workflow WS93600011 in our development server. Till Friday 10.07.2009 it was working fine. We did some small change and activated the workflow. Till that time we were able to open the workflow template. On 13.06.2009 when we tried to open the workflow then it was giving dump, so accordingly we checked is this the problem with only 1 workflow template or all the workflow templates and we found that this is the problem with only 1 workflow template not all. So accordingly we did some analysis and I tried to check whether any SAP OSS Notes needs to be implemented but all the notes are already in place.
Please see below the what dump says...
Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED_NO
Except. CX_SY_REF_IS_INITIAL
Date and Time 07/20/2009 13:30:44
Short text
Access via 'NULL' object reference not possible.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_WFD_TASK_PROXY=============CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
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.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not caught in procedure "CONSTRUCTOR" "(METHOD)", nor was it propagated by a RAISING clause. Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated. The reason for the exception is: You attempted to use a 'NULL' object reference (points to 'nothing') access a component. An object reference must point to an object (an instance of a class) before it can be used to access components. Either the reference was never set or it was set to 'NULL' using the CLEAR statement.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to find an interim solution in an SAP Note. If you have access to SAP Notes, carry out a search with the following keywords:
"OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"
"CL_WFD_TASK_PROXY=============CP" or "CL_WFD_TASK_PROXY=============CM001"
"CONSTRUCTOR"
If you cannot solve the problem yourself and want to send an error notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File (Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21. Restrict the time interval to 10 minutes before and five minutes after the short dump. Then choose "System->List->Save->Local File (Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP program: The source code of the program In the editor, choose "Utilities->More Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which actions and input led to the error.
The exception must either be prevented, caught within proedure
"CONSTRUCTOR" "(METHOD)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 701
Application server... "ydedb"
Network address...... "9.57.177.109"
Operating system..... "AIX"
Release.............. "6.1"
Hardware type........ "00C15EAF4C00"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 4
Shortdump setting.... "full"
Database server... "ydedb"
Database type..... "DB6"
Database name..... "YDE"
Database user ID.. "SAPYDE"
Terminal.......... "IBM-BE014934612"
Char.set.... "C"
SAP kernel....... 701
created (date)... "Mar 30 2009 21:48:51"
create on........ "AIX 2 5 00CB5A5B4C00"
Database version. "DB6_81 "
Patch level. 37
Patch text.. " "
Database............. "DB6 08.02.*, DB6 09.*"
SAP database version. 701
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 16192
EM...... 8379696
Heap.... 0
Page.... 73728
MM Used. 3730104
MM Free. 457144
User and Transaction
Client.............. 210
User................ 013319744
Language key........ "E"
Transaction......... "PFTC "
Transactions ID..... "4A62BD9572AD004BE10080000939B16D"
Program............. "CL_WFD_TASK_PROXY=============CP"
Screen.............. "SAPLRHWS 1001"
Screen line......... 19
Information on where terminated
Termination occurred in the ABAP program "CL_WFD_TASK_PROXY=============CP" -
in "CONSTRUCTOR".
The main program was "SAPLRHW4 ".
In the source code you have the termination point in line 91
of the (Include) program "CL_WFD_TASK_PROXY=============CM001".
The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
procedure "CONSTRUCTOR" "(METHOD)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "CL_WFD_TASK_PROXY=============CP "; its source
code begins in line
1 of the (Include program "CL_WFD_TASK_PROXY=============CM001 ".
Source Code Extract
Line SourceCde
61 a_task = l_task.
62 ENDIF.
63 *-- load task
64 IF in_task IS NOT INITIAL.
65 a_task = in_task.
66 ENDIF.
67 CALL METHOD deserialize
68 EXPORTING
69 in_display = in_display
70 EXCEPTIONS
71 task_not_exists = 1
72 task_already_locked = 2
73 OTHERS = 3.
74 IF sy-subrc = 2.
75 *---- we couldn't lock in update mode -> create a proxy in display
76 *---- mode
77 CALL METHOD deserialize
78 EXPORTING
79 in_display = 'X'
80 EXCEPTIONS
81 task_not_exists = 1
82 task_already_locked = 2
83 OTHERS = 3.
84 ENDIF.
85 IF sy-subrc <> 0.
86 RAISE task_not_found.
87 ENDIF.
88 ENDIF.
89 * create before image on the container
90 TRY.
>>>>> CALL METHOD a_container->create_before_image
92 EXPORTING
93 include_extensions = 'X'.
94 CATCH cx_swf_cnt_container .
95 ENDTRY.
96
97 ENDMETHOD. "constructor
If any body is having any idea to resolve this issue then please let me know. We are into the last stage of the development.
Thanks in advance for replying this issue.
Best Regards,
Prashant Raichurkar