Workflow - runtime error
Hi all,
I am creating workflow for material master. When i save and excute in SWDD system shows the following error.
Runtime Errors MESSAGE_TYPE_X
Date and Time 01.10.2009 13:20:51
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Unable to read RFC destination WORKFLOW_LOCAL_300
Long text of error message:
Technical information about the message:
Message class....... "SWF_RUN"
Number.............. 617
Variable 1.......... "WORKFLOW_LOCAL_300"
Variable 2.......... "RFC_READ_DESTINATION_TYPE"
Variable 3.......... "DESTINATION_NOT_EXIST"
Variable 4.......... " "
Trigger Location of Runtime Error
Program CL_SWF_RUN_WIM_LOCAL==========CP
Include CL_SWF_RUN_WIM_LOCAL==========CM088
Row 10
Module type (METHOD)
Module Name IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
Source Code Extract
Line SourceCde
1 METHOD if_swf_run_wim_utl_internal~get_system_user .
2 DATA: l_excp TYPE REF TO cx_swf_run_wim.
3
4 TRY.
5 IF me->m_int_state-system_user IS INITIAL.
6 me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
7 ENDIF.
8 re_user = me->m_int_state-system_user.
Can any one please give me solution for this issue.
Thanks in advance,
Babu
I thought correctly
The RFC destination is the most important one for using workflows in any system.
Ask someone with SAP_ALL SAP_NEW profiles to execute that action automatically. Or do it yourself if you have it.
And you have to check the Sapna Modi Blog, because every action is explained in detail.
Kind regards, Rob Dielemans
Similar Messages
-
Workflow runtime error because of terminating event
Hi all,
In one of the workflow template, in one step, the Standard Task is having Terminating Event.
At the runtime, at the particular step, when it was in process, the terminating event is triggered. The step got completed,
But the workflow is not proceeding.
When I viewed the workflow log, In the perticular step after receiving the terminating event, the follwoing error is shown
" Workitem XXXXXX is locked by the user YYY(Enqueue error)".
The workitem number mentioned in the error is parent workitem number, not one of the particular step.
I know that there is a setting in SWU3 to schedule a job for errored out workitems. That job is already scheduled and it has tried two times and it stopped.
Now do I have to restart the workflow again or the issue can be resolved in the workitem in progress.
Thanks,
Sarayoodharan.Kthe terminating event is triggered. The step got completed,
But the workflow is not proceeding.
When I viewed the workflow log, In the perticular step after receiving the terminating event, the follwoing error is shown
" Workitem XXXXXX is locked by the user YYY(Enqueue error)".
Can you please let us know how you are trying to trigger the terminating event,I mean are you trying to trigger the terminating Programatically, then you might be using a FM to rasie the terminating event, by looking at the error it is clear that the event is triggered and the workitem got completed but the lock on the workitem is not released , you can release it by using the COMMIT WORK statement
You have to write the commit work statement after raising the even or make sure that someor the other way the commit work is executed, this is beacuse once the commit work statement is executed all Locks are released.. -
Workflow will not manually start - getting Server Error in '/' Application - Runtime Error
I've tested so far in three site collections and I am not able to manually start a workflow. I am getting the below error
Runtime Error
Description: An application error occurred on the server. The current custom error
settings for this application prevent the details of the application error from
being viewed remotely (for security reasons). It could, however, be viewed by
browsers running on the local server machine.
Details: To enable
the details of this specific error message to be viewable on remote machines,
please create a <customErrors> tag within a "web.config" configuration
file located in the root directory of the current web application. This
<customErrors> tag should then have its "mode" attribute set to "Off".
So, I jumped on the server and checked the logs and this is what I am getting below:
Application error when access /_layouts/15/Workflow.aspx, Error=Method 'StartWorkflowOnListItem' in type 'Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider' from assembly 'Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c' does not have an implementation. at Microsoft.SharePoint.WorkflowServices.FabricSolutionProviderFactory.<.cctor>b__3(WorkflowServicesContext context) at Microsoft.SharePoint.WorkflowServices.FabricSolutionProviderFactory.GetProvider[T](WorkflowServicesContext
context) at Microsoft.SharePoint.WorkflowServices.WorkflowServicesManager.GetProvider[T]() at Microsoft.SharePoint.WorkflowServices.WorkflowServicesManager.GetWorkflowInstanceService()
at Microsoft.SharePoint.WorkflowService...
I would love some help if anybody has any suggestions.Hi,
THis is a upgrade issue. Please check below
https://social.technet.microsoft.com/Forums/windowsserver/en-US/b189e4b8-bb9e-4ade-a3d5-cd2e0f90e93f/workflow-not-working-after-installing-service-pack-1-and-patches?forum=sharepointadmin
Please remember to click 'Mark as Answer' on the answer if it helps you -
Runtime error during PO workflow execution
Hi,
We have a custom workflow and today i received a runtime error while i was executing the approval process for the purchase order.
In our workflow a work item is going to be sent to the proper approver, and inside this item, there are several possibilites for the approver: approve, reject, etc.
Until this item, everything is fine, but when i decide to approve the PO, the system gives me an error: "Runtime Errors: GETWA_NOT_ASSIGNED".
I did not do any changes on the workflow in the last few days (and i don't think so anybody else did any modification on it) and i don't know what should be the problem.
If you have any idea for the solution, please let me know!
Thanks in advance for your help!
Best Regards,
AttilaHello,
Searching for GETWA_NOT_ASSIGNED in OSS brings up 2467 notes - see which one applies to you and your version.
regards
Rick Bakker
Hanabi Technology -
ABAP runtime error in FBV2 Change parked document using workflow
Hi,
When selecting screen template variant in tcode FBV2 change parked document, I get abap runtime error DYNPRO_NOT_FOUND
Tcode- FBV2
Program- SAPLF040
Screen- SAPLF040 0310
Main Program - SAPMF05V
Information on were terminated.
Program SAPLF040 - in " %_CTL_END "
In the source code you have the termination point in line 50 of the (Include) program " <SYSINI> "
How can we solve this error. We are on ECC6 with release 600.
Thanks,
MarkHi Mark,
We have this same issue in transaction F-65
I believe that when a new screen template is configured, a new screen is generated within function group F040. A later action (applying a hotpack??) has removed this screen, but the config (in table T021D) still points the processing to the screen even though it has been removed.
Did you find a solution? We want to get the screen back as it is still valid to use this screen template in the business
Thanks
Ben -
Runtime error in distribution FM 'CVV5_EVENT_START_DISTRIBUTION'
Dear All,
I am facing an issue in document distribution. Business scenario: PR is created with a doument. PR goes through a release strategy which is designed through a Workflow. When PR is finally approved, Documnet distribution happens. Business object DRAW is called with event CHANGED and hence this FM CVV5_EVENT_START_DISTRIBUTION is called. However this results in a runtime error due to exception 'NO_RELATION_EXIST'. I am not able to debug and find if any necessary parameter is getting missed and i do not have too much information on DMS.
Can somebody guide me in resolving this issue. If any other information is needed then please post it.
Thanking you in advance.
Regards,
SaudThnaks a lot. That note is explicitly for this problem. I will take it forward now. Will revert back in case of any issue. Thanks again.
Regards,
Saud -
Portal Runtime Error when opening Webflow workitem in UWL
Hi,
I have recently configured the UWL to pick up workitems from SAP workflow on a background system. The workitems are appearing OK in the Task folder. However, when I try to open a workitem by double-clicking on it, I get the following error:
Portal Runtime Error
An Exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 05:33_30/09/10_0010_24209150
Refer to the log file for details about this exception.
NB. This only seems to happen for items that would be shown via the SAP GUI (E.g. a Confirming a task completion or user decision). The workitem runs OK if it is for a task that is visualised as a Web Dynpro app and specified in transaction SWFVISU.
I have not configured Delta Refresh options in the Workflow Administrator so do not know if this is a possible reason (I assumed that this would not cause a problem and would simply mean that refreshes only occur once every 60 seconds). Any help would be greatly appreciated. I am fairly new to Portal & UWL I would also be grateful if someone could tell where I can find the relevant log files referenced in the original error.
Regards
SimonHey Simon,
Welcome to UWL :). Portal Runtime Errors in UWL don't always signify that there is a UWL issue. This could be a permissions problem, etc. I'm not sure what version of the portal that you are using. But here is a little trick for you when checking logs...you can enter in the following: irj/servlet/prt/portal/prtroot/com.sap.portal.runtime.admin.logviewer.default
and check the log file with the id that was given in the error.
Exception ID: 05:33_30/09/10_0010_24209150 is your exception id. Search for the log files in the default trace and see what the exact error message is. If you can post this here it would be great.
The log files can be found in the following location:
/usr/sap/<SID>/JC<InstanceNumber>/j2ee/cluster/
server<number>/log
or by entering the URL that I mentioned above.
Please let me know in the next reply what the portal version is:
You can get this information by doing the following:
a. log on to the portal
b. backspace out the irj/portal section of the URL
c. click enter.
d. You are now at the J2EE administration page.
e. Next, click on the system information link
f. Please click on the all components link
g. Please attach this information to the message.
I am interested mostly in the UWLJWF component but if you can attach the full software component info to this post that would be great...
Please note, that note number 1133821 is an important note that is needed in the UWL. Did you maintain your RFC destination accordingly?
Here is some additional information to help you too since you are new to UWL:
[UWL Wiki|https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq]
[UWL Forums|SAP Enterprise Portal: Application Integration;
[Business Task Management|http://help.sap.com/saphelp_nw70/helpdata/en/9e/ccf62fff3e4a45a634e592dabb45d5/frameset.htm]
[Using Universal Worklist|http://help.sap.com/saphelp_nw04s/helpdata/en/57/c223be82104792a15c2df11377b9ed/frameset.htm]
[JavaDocs UWL API|http://help.sap.com/javadocs/NW04S/current/uw/overview-summary.html]
I hope that you find this information useful!
Best Regards,
Beth Maben
EP - Senior Support Consultant
AGS Primary Support, Business Suite & Technology
Please see the UWL Wiki @
https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq *** -
Hi friends,
Pls check below the runtime error description ,which I'm getting when releasing the Order - PM.
Pls advise, What happ'd and how to fix it.
Regards
Sankar.
Runtime Errors MESSAGE_TYPE_X
Date and Time 31.03.2008 13:16:08
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
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
Short text of error message:
Unable to read RFC destination WORKFLOW_LOCAL_250
Long text of error message:
Technical information about the message:
Message class....... "SWF_RUN"
Number.............. 617
Variable 1.......... "WORKFLOW_LOCAL_250"
Variable 2.......... "RFC_READ_DESTINATION_TYPE"
Variable 3.......... "DESTINATION_NOT_EXIST"
Variable 4.......... " "
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:
"MESSAGE_TYPE_X" " "
"CL_SWF_RUN_WIM_LOCAL==========CP" or "CL_SWF_RUN_WIM_LOCAL==========CM088"
"IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER"
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.
System environment
SAP-Release 700
Application server... "SILDEV"
Network address...... "192.168.255.70"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x IA64 Level 3"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "SILDEV"
Database type..... "MSSQL"
Database name..... "DEV"
Database user ID.. "dev"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 3 2008 03:55:37"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "SQL_Server_8.00 "
Patch level. 150
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 8379680
Heap.... 0
Page.... 16384
MM Used. 4889280
MM Free. 3487552
User and Transaction
Client.............. 250
User................ "PM5CHARL"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "49F6FEDCA000F177897B0017A4ABF059"
Program............. "CL_SWF_RUN_WIM_LOCAL==========CP"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "DEV"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........."C0A8FF46013847F096C00004"
Outbound Queue Name.." "
Client.............. 250
User................ "PM5CHARL"
Transaction......... " "
Call Program........."SAPLERFC"
Function Module..... "ARFC_DEST_SHIP"
Call Destination.... "NONE"
Source Server....... "SILDEV_DEV_00"
Source IP Address... "192.168.255.70"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "CL_SWF_RUN_WIM_LOCAL==========CP" -
in "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 10
of the (Include) program "CL_SWF_RUN_WIM_LOCAL==========CM088".
Source Code Extract
Line SourceCde
1 METHOD if_swf_run_wim_utl_internal~get_system_user .
2 DATA: l_excp TYPE REF TO cx_swf_run_wim.
3
4 TRY.
5 IF me->m_int_state-system_user IS INITIAL.
6 me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
7 ENDIF.
8 re_user = me->m_int_state-system_user.
9 CATCH cx_swf_run_wim INTO l_excp.
>>>>> MESSAGE ID l_excp->t100_msg-msgid
11 TYPE 'X'
12 NUMBER l_excp->t100_msg-msgno
13 WITH l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
14 l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
15 ENDTRY.
16
17 ENDMETHOD. "
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 2
SY-TABIX 1
SY-DBCNT 0
SY-FDPOS 1
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE CPIC and RFC Control
SY-MSGTY X
SY-MSGID SWF_RUN
SY-MSGNO 617
SY-MSGV1 WORKFLOW_LOCAL_250
SY-MSGV2 RFC_READ_DESTINATION_TYPE
SY-MSGV3 DESTINATION_NOT_EXIST
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080331
SY-UZEIT 131608
SY-XPROG SAPMSSY1
SY-XFORM XAB_READ
Active Calls/Events
No. Ty. Program Include Line
Name
26 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM088 10
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
25 METHOD CL_SWF_UTL_MAIL===============CP CL_SWF_UTL_MAIL===============CM00J 5
CL_SWF_UTL_MAIL=>GET_OWNER
24 METHOD CL_SWF_UTL_MAIL===============CP CL_SWF_UTL_MAIL===============CM002 37
CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
23 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM0IE 38
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
22 METHOD CL_SWF_RUN_WIM_STATE==========CP CL_SWF_RUN_WIM_STATE==========CM021 7
CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL
21 METHOD CL_SWF_RUN_WIM_STATE==========CP CL_SWF_RUN_WIM_STATE==========CM01V 12
CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION
20 METHOD CL_SWF_RUN_WIM_STATE_FLOW=====CP CL_SWF_RUN_WIM_STATE_FLOW=====CM004 2
CL_SWF_RUN_WIM_STATE_FLOW=>IF_SWF_RUN_WIM_STATE~EXECUTE_STATE_TRANSITION
19 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM09A 72
CL_SWF_RUN_WIM_LOCAL=>SET_STATUS_INTERNAL
18 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM0H3 16
CL_SWF_RUN_WIM_LOCAL=>_SET_STATUS
17 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM04P 7
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SET_STATUS
16 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM011 12
CL_SWF_RUN_WIM_EXECUTION_MGR=>SET_WORKITEM_STATUS_ERROR
15 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM01A 81
CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXCEPTION_RESULT
14 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM00R 93
CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXECUTION_RESULT
13 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM008 144
CL_SWF_RUN_WIM_EXECUTION_MGR=>START_EXECUTION
12 METHOD CL_SWF_RUN_WORKFLOW_START=====CP CL_SWF_RUN_WORKFLOW_START=====CM016 42
CL_SWF_RUN_WORKFLOW_START=>START_WORKITEM
11 METHOD CL_SWF_RUN_WORKFLOW_START=====CP CL_SWF_RUN_WORKFLOW_START=====CM002 33
CL_SWF_RUN_WORKFLOW_START=>EXECUTE
10 FUNCTION SAPLSWW_SRV LSWW_SRVU13 135
SWW_WI_CREATE_VIA_EVENT_INTERN
9 FUNCTION SAPLSWW_SRV LSWW_SRVU11 64
SWW_WI_CREATE_VIA_EVENT
8 FORM SAPLSWW_SRV LSWW_SRVU11 1
SWW_WI_CREATE_VIA_EVENT
7 FORM SAPMSSY1 SAPMSSY1 271
XAB_RUN_DRIVER
6 FUNCTION SAPLSXAB LSXABU01 9
RFC_RUN_XAB_DRIVER
5 FUNCTION SAPLERFC LERFCU01 115
ARFC_EXECUTE
4 FUNCTION SAPLERFC LERFCU02 386
ARFC_DEST_SHIP
3 FORM SAPLERFC LERFCU02 1
ARFC_DEST_SHIP
2 FORM SAPMSSY1 SAPMSSY1 85
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30
%_RFC_START
Chosen variables
Name
Val.
No. 26 Ty. METHOD
Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
RE_USER
222222222222
000000000000
000000000000
000000000000
L_EXCP
B0004000
90006000
SY-MSGID
SWF_RUN
55455542222222222222
376F25E0000000000000
00000000000000000000
00000000000000000000
L_EXCP->T100_MSG-MSGID
SWF_RUN
55455542222222222222
376F25E0000000000000
00000000000000000000
00000000000000000000
SWFCO_WIM_WI_FORWARD
SWW_WI_FORWARD
555554544554542222222222222222
377F79F6F271240000000000000000
000000000000000000000000000000
000000000000000000000000000000
SY-MSGNO
617
333
617
000
000
L_EXCP->T100_MSG+40(6)
617
333
617
000
000
SY-MSGV1
WORKFLOW_LOCAL_250
54544445544444533322222222222222222222222222222222
7F2B6CF7FCF31CF25000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+48(100)
WORKFLOW_LOCAL_250
54544445544444533322222222222222222222222222222222
7F2B6CF7FCF31CF25000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV2
RFC_READ_DESTINATION_TYPE
54455444544554445444555542222222222222222222222222
263F2514F45349E149FEF49050000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+148(100)
RFC_READ_DESTINATION_TYPE
54455444544554445444555542222222222222222222222222
263F2514F45349E149FEF49050000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV3
DESTINATION_NOT_EXIST
44554445444544554545522222222222222222222222222222
45349E149FEFEF4F5893400000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+248(100)
DESTINATION_NOT_EXIST
44554445444544554545522222222222222222222222222222
45349E149FEFEF4F5893400000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+348(100)
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
No. 25 Ty. METHOD
Name CL_SWF_UTL_MAIL=>GET_OWNER
RE_OWNER
%_DUMMY$$
2222
0000
0000
0000
ME->M_OWNER
%_VIASELSCR
0
4
ME
A0005000
E0001000
L_WORKITEM
60009000
3000C000
SY-REPID
CL_SWF_UTL_MAIL===============CP
4455545554544443333333333333334522222222
3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No. 24 Ty. METHOD
Name CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
EX_SENT_TO_ALL
2
0
0
0
EX_MAIL_OBJECT
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
CL_SWF_UTL_MAIL===============CP
4455545554544443333333333333334522222222
3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME
A0005000
E0001000
OBJECT_HD_CHANGE-ACNAM
SWW_WI_DISPLAY_FOR_MAIL
555554544554455445544442222222222222222222222222222222
377F79F4930C19F6F2FD19C0000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
OBJPARB
Table IT_7581x570
\CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJPARB
Table reference: 224
TABH+ 0(20) = E06D6DEFF9060000000000000000000000000000
TABH+ 20(20) = E0000000F6020000010000003A020000FFFFFFFF
TABH+ 40(16) = 042A0200600B000010000000C1248401
store = 0xE06D6DEFF9060000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 224 (0xE0000000)
label = 758 (0xF6020000)
fill = 1 (0x01000000)
leng = 570 (0x3A020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000046
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x80095FEFF9060000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 540 (0x1C020000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
OBJECT_HD_CHANGE-OBJDES
Workflow 405090 set to status ERROR
56766667233333327672762776777245545222222222222222
7F2B6CF70405090035404F03414530522F2000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
%_FSREG_001
OBJCONT
Table IT_7609x510
\CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJCONT
Table reference: 225
TABH+ 0(20) = 106F6DEFF9060000000000000000000000000000
TABH+ 20(20) = E1000000F802000009000000FE010000FFFFFFFF
TABH+ 40(16) = 042A0200300B000010000000C1248401
store = 0x106F6DEFF9060000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 225 (0xE1000000)
label = 760 (0xF8020000)
fill = 9 (0x09000000)
leng = 510 (0xFE010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000045
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x402D5FEFF9060000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 541 (0x1D020000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
OWNER
222222222222
000000000000
000000000000
000000000000
SENDER
222222222222
000000000000
000000000000
000000000000
SY-SUBRC
0
0000
0000
SWFCO_MAIL_ERROR_NOTIFY
0002
3333
0002
0000
0000
OBJECT_HD_CHANGE
E ERRORMESSAGEWorkflow 405090 set to status ERROR 00000000000000 F F S
4222222222245545445544456766667233333327672762776777245545222222222222222233333333333333242425
50000000000522F2D5331757F2B6CF70405090035404F03414530522F2000000000000000000000000000000060603
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OBJECT_TYPE
RAW
545
217
000
000
SWFCO_OBJTYPE_BOR
BO
44
2F
00
00
No. 23 Ty. METHOD
Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
LT_AGENTS
Table IT_7521x28
\CLASS=CL_SWF_RUN_WIM_LOCAL\METHOD=IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL\DATA=LT_AGEN
Table reference: 207
TABH+ 0(20) = 806B6DEFF9060000000000000000000000000000
TABH+ 20(20) = CF000000F0020000010000001C000000FFFFFFFF
TABH+ 40(16) = 04180100E006000010000000C1248401
store = 0x806B6DEFF9060000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 207 (0xCF000000)
label = 752 (0xF0020000)
fill = 1 (0x01000000)
leng = 28 (0x1C000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000022
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xA0696DEFF9060000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 537 (0x19020000)
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
SYST-REPID
CL_SWF_RUN_WIM_LOCAL==========CP
4455545554554454444433333333334522222222
3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD+840(28)
WS20000014
55333333332222
73200000140000
00000000000000
00000000000000
SY-REPID
CL_SWF_RUN_WIM_LOCAL==========CP
4455545554554454444433333333334522222222
3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
FUNCNAME
SWW_WI_DISPLAY_FOR_MAIL
555554544554455445544442222222
377F79F4930C19F6F2FD19C0000000
000000000000000000000000000000
000000000000000000000000000000
SWFCO_WI_REMOTE
R
5
2
0
0
PARAMETER-NAME
WI_ID
54544
79F94
00000
00000
SWFCO_CALLBACK_AGENTS
CALLBACKAGENTS
54444444454444552222222222222222
F31CC213BF175E430000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
PARAMETER-VALUE
000000405090
333333333333
000000405090
000000000000
000000000000
ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD-WI_ID
000000405090
333333333333
000000405090
000000000000
000000000000
PARAMETER
807020C0
7080A050
00000000
00100010
LS_MAILOBJ
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000Hi Sankar,
Clearly RFC destination WORKFLOW_LOCAL_250 doesnot exist. But please don't create it directly using Sm59.
Log into client 250 and go to transaction SWU3. Here you will get option for creating RFC destination making use of user WF-BATCH. In case there is workflow expert in your project take his help.
Once this is done this dump should not come.
Regards.
Ruchit. -
Runtime Error in Acrobat X Pro
After installing Acrobat X Pro on my Windows 7 based PC, when I tried to open the program, received the following message:
An internal error has occurred.
After clicking "OK," the following message appeared:
Runtime Error!
Program C:\.....
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
I have uninstalled and reinstalled Acrobat X Pro 3 times and get the same error.
Please help!Hi,
Please follow the suggestions provided here : http://helpx.adobe.com/acrobat/kb/runtime-error-roaming-profile-workflows.html -
Runtime error in Universal Worklist in portal
Hi!
An error occurs when I open the page Universal Worklist -
Administration under System Administration > System Configuration >
Universal Worklist & Workflow. The error message is:
Portal runtime error.
An exception occurred while processing your request. Send the exception
ID to your portal administrator.
Exception ID: 09:44_02/10/08_0004_221082950
Refer to the log file for details about this exception.
This error is also displayed when opening the page Portal Eventing,
Portal Navigation under System Administration > Support > Web Dynpro
Test Tools > Application Integrator Tests.
The portal UME is configured with ADS as data source and we are using
the dataSourceConfiguration_ads_readonly_db_with_krb5.xml configuration
file. Single Sign-On using SAP logon tickets with user mapping to
reference system is also implemented.
Users have different users IDs in the SAP System than in the portal,
and scenario 2 from SAP Help "Single Sign-On to SAP Systems"
(http://help.sap.com/saphelp_nw04/helpdata/en/4d/dd9b9ce80311d5995500508b6b8b11/frameset.htm) is implemented
"Scenario 2: Single Sign-On using SAP logon tickets with user mapping."
The problem occurred after changing the UME with ADS and implemented
Single Sign-on.
Error messages from log:
Date : 10/03/2008
Time : 10:08:56:057
Message : Content pass of Application Integrator failed.
Component Name: com.sap.portal.appintegrator.sap.WebDynpro,
Context Name (iView): pcd:portal_content/every_user/general/uwl/com.sap.netweaver.bc.uwl.uwlSapWebDynproLaunch,
Top Layer: WebDynpro/TopLayer,
Producer ID (FPN): null,
System Alias: SAP_LocalSystem,
[EXCEPTION]
com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
... 33 more
Severity : Error
Category : /System/Server
Location : com.sap.portal.sapapplication
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_18
Datasource : 1223021485930:N:\usr\sap\DPN\JC32\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 00145ED7E6460061000007830000B6B800045854D84A3E79
Source Name : com.sap.portal.sapapplication
Argument Objs : com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
... 33 more
Arguments : com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
... 33 more
Dsr Component : n/a
Dsr Transaction : f52708e0912011ddb1e200145ed7e646
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : /System/Server
Resource Bundlename :
Session : 32121
Source : com.sap.portal.sapapplication
ThreadObject : SAPEngine_Application_Thread[impl:3]_18
Transaction :
User : Asle.Gaarder
Date : 10/03/2008
Time : 10:08:56:026
Message : Cannot provide backend user ID and password for user "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder") for system "SAP_ECC_REFERENCE" because these credentials could not be found in the user mapping data.
Severity : Info
Category :
Location : com.sap.security.core.umap.imp.UserMappingDataImp.enrich(Properties)
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_18
Datasource : 1223021485930:N:\usr\sap\DPN\JC32\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 00145ED7E6460061000007820000B6B800045854D849CB92
Source Name : com.sap.security.core.umap.imp.UserMappingDataImp
Argument Objs : "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder"),"SAP_ECC_REFERENCE",
Arguments : "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder"),"SAP_ECC_REFERENCE",
Dsr Component : n/a
Dsr Transaction : f52708e0912011ddb1e200145ed7e646
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives :
Resource Bundlename :
Session : 32121
Source : com.sap.security.core.umap.imp.UserMappingDataImp
ThreadObject : SAPEngine_Application_Thread[impl:3]_18
Transaction :
User : Asle.GaarderHi,
Check the logon type for systems SAP_LocalSystem and SAP_ECC_REFERENCE which must be set to SAPLOGONTICKET not UIDPWD.
It basically fails since the password doesn't exist for the mapping, as it is only dependent on trust.
There was a change in a recent SP which added an extra check in this area.
Dagfinn -
RUNTIME Error - User Status for Order release
HI Friends,
Pls go thru the run-time error description,which i'm getting on Order release.Pls reply,.
Runtime Errors MESSAGE_TYPE_X
Date and Time 31.03.2008 13:16:08
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
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
Short text of error message:
Unable to read RFC destination WORKFLOW_LOCAL_250
Long text of error message:
Technical information about the message:
Message class....... "SWF_RUN"
Number.............. 617
Variable 1.......... "WORKFLOW_LOCAL_250"
Variable 2.......... "RFC_READ_DESTINATION_TYPE"
Variable 3.......... "DESTINATION_NOT_EXIST"
Variable 4.......... " "
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:
"MESSAGE_TYPE_X" " "
"CL_SWF_RUN_WIM_LOCAL==========CP" or "CL_SWF_RUN_WIM_LOCAL==========CM088"
"IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER"
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.
System environment
SAP-Release 700
Application server... "SILDEV"
Network address...... "192.168.255.70"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x IA64 Level 3"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "SILDEV"
Database type..... "MSSQL"
Database name..... "DEV"
Database user ID.. "dev"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 3 2008 03:55:37"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "SQL_Server_8.00 "
Patch level. 150
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 8379680
Heap.... 0
Page.... 16384
MM Used. 4889280
MM Free. 3487552
User and Transaction
Client.............. 250
User................ "PM5CHARL"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "49F6FEDCA000F177897B0017A4ABF059"
Program............. "CL_SWF_RUN_WIM_LOCAL==========CP"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "DEV"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........."C0A8FF46013847F096C00004"
Outbound Queue Name.." "
Client.............. 250
User................ "PM5CHARL"
Transaction......... " "
Call Program........."SAPLERFC"
Function Module..... "ARFC_DEST_SHIP"
Call Destination.... "NONE"
Source Server....... "SILDEV_DEV_00"
Source IP Address... "192.168.255.70"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "CL_SWF_RUN_WIM_LOCAL==========CP" -
in "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 10
of the (Include) program "CL_SWF_RUN_WIM_LOCAL==========CM088".
Source Code Extract
Line
SourceCde
1
METHOD if_swf_run_wim_utl_internal~get_system_user .
2
DATA: l_excp TYPE REF TO cx_swf_run_wim.
3
4
TRY.
5
IF me->m_int_state-system_user IS INITIAL.
6
me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
7
ENDIF.
8
re_user = me->m_int_state-system_user.
9
CATCH cx_swf_run_wim INTO l_excp.
>>>>>
MESSAGE ID l_excp->t100_msg-msgid
11
TYPE 'X'
12
NUMBER l_excp->t100_msg-msgno
13
WITH l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
14
l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
15
ENDTRY.
16
17
ENDMETHOD. "
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
2
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
1
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC and RFC Control
SY-MSGTY
X
SY-MSGID
SWF_RUN
SY-MSGNO
617
SY-MSGV1
WORKFLOW_LOCAL_250
SY-MSGV2
RFC_READ_DESTINATION_TYPE
SY-MSGV3
DESTINATION_NOT_EXIST
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080331
SY-UZEIT
131608
SY-XPROG
SAPMSSY1
SY-XFORM
XAB_READ
Active Calls/Events
No. Ty. Program Include Line
Name
26 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM088 10
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
25 METHOD CL_SWF_UTL_MAIL===============CP CL_SWF_UTL_MAIL===============CM00J 5
CL_SWF_UTL_MAIL=>GET_OWNER
24 METHOD CL_SWF_UTL_MAIL===============CP CL_SWF_UTL_MAIL===============CM002 37
CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
23 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM0IE 38
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
22 METHOD CL_SWF_RUN_WIM_STATE==========CP CL_SWF_RUN_WIM_STATE==========CM021 7
CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL
21 METHOD CL_SWF_RUN_WIM_STATE==========CP CL_SWF_RUN_WIM_STATE==========CM01V 12
CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION
20 METHOD CL_SWF_RUN_WIM_STATE_FLOW=====CP CL_SWF_RUN_WIM_STATE_FLOW=====CM004 2
CL_SWF_RUN_WIM_STATE_FLOW=>IF_SWF_RUN_WIM_STATE~EXECUTE_STATE_TRANSITION
19 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM09A 72
CL_SWF_RUN_WIM_LOCAL=>SET_STATUS_INTERNAL
18 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM0H3 16
CL_SWF_RUN_WIM_LOCAL=>_SET_STATUS
17 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM04P 7
CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SET_STATUS
16 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM011 12
CL_SWF_RUN_WIM_EXECUTION_MGR=>SET_WORKITEM_STATUS_ERROR
15 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM01A 81
CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXCEPTION_RESULT
14 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM00R 93
CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXECUTION_RESULT
13 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM008 144
CL_SWF_RUN_WIM_EXECUTION_MGR=>START_EXECUTION
12 METHOD CL_SWF_RUN_WORKFLOW_START=====CP CL_SWF_RUN_WORKFLOW_START=====CM016 42
CL_SWF_RUN_WORKFLOW_START=>START_WORKITEM
11 METHOD CL_SWF_RUN_WORKFLOW_START=====CP CL_SWF_RUN_WORKFLOW_START=====CM002 33
CL_SWF_RUN_WORKFLOW_START=>EXECUTE
10 FUNCTION SAPLSWW_SRV LSWW_SRVU13 135
SWW_WI_CREATE_VIA_EVENT_INTERN
9 FUNCTION SAPLSWW_SRV LSWW_SRVU11 64
SWW_WI_CREATE_VIA_EVENT
8 FORM SAPLSWW_SRV LSWW_SRVU11 1
SWW_WI_CREATE_VIA_EVENT
7 FORM SAPMSSY1 SAPMSSY1 271
XAB_RUN_DRIVER
6 FUNCTION SAPLSXAB LSXABU01 9
RFC_RUN_XAB_DRIVER
5 FUNCTION SAPLERFC LERFCU01 115
ARFC_EXECUTE
4 FUNCTION SAPLERFC LERFCU02 386
ARFC_DEST_SHIP
3 FORM SAPLERFC LERFCU02 1
ARFC_DEST_SHIP
2 FORM SAPMSSY1 SAPMSSY1 85
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30
%_RFC_START
Chosen variables
Name
Val.
No. 26 Ty. METHOD
Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
RE_USER
222222222222
000000000000
000000000000
000000000000
L_EXCP
B0004000
90006000
SY-MSGID
SWF_RUN
55455542222222222222
376F25E0000000000000
00000000000000000000
00000000000000000000
L_EXCP->T100_MSG-MSGID
SWF_RUN
55455542222222222222
376F25E0000000000000
00000000000000000000
00000000000000000000
SWFCO_WIM_WI_FORWARD
SWW_WI_FORWARD
555554544554542222222222222222
377F79F6F271240000000000000000
000000000000000000000000000000
000000000000000000000000000000
SY-MSGNO
617
333
617
000
000
L_EXCP->T100_MSG+40(6)
617
333
617
000
000
SY-MSGV1
WORKFLOW_LOCAL_250
54544445544444533322222222222222222222222222222222
7F2B6CF7FCF31CF25000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+48(100)
WORKFLOW_LOCAL_250
54544445544444533322222222222222222222222222222222
7F2B6CF7FCF31CF25000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV2
RFC_READ_DESTINATION_TYPE
54455444544554445444555542222222222222222222222222
263F2514F45349E149FEF49050000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+148(100)
RFC_READ_DESTINATION_TYPE
54455444544554445444555542222222222222222222222222
263F2514F45349E149FEF49050000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV3
DESTINATION_NOT_EXIST
44554445444544554545522222222222222222222222222222
45349E149FEFEF4F5893400000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+248(100)
DESTINATION_NOT_EXIST
44554445444544554545522222222222222222222222222222
45349E149FEFEF4F5893400000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
L_EXCP->T100_MSG+348(100)
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
No. 25 Ty. METHOD
Name CL_SWF_UTL_MAIL=>GET_OWNER
RE_OWNER
%_DUMMY$$
2222
0000
0000
0000
ME->M_OWNER
%_VIASELSCR
0
4
ME
A0005000
E0001000
L_WORKITEM
60009000
3000C000
SY-REPID
CL_SWF_UTL_MAIL===============CP
4455545554544443333333333333334522222222
3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No. 24 Ty. METHOD
Name CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND
EX_SENT_TO_ALL
2
0
0
0
EX_MAIL_OBJECT
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
CL_SWF_UTL_MAIL===============CP
4455545554544443333333333333334522222222
3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME
A0005000
E0001000
OBJECT_HD_CHANGE-ACNAM
SWW_WI_DISPLAY_FOR_MAIL
555554544554455445544442222222222222222222222222222222
377F79F4930C19F6F2FD19C0000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000
OBJPARB
Table IT_758[1x570]
\CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJPARB
Table reference: 224
TABH+ 0(20) = E06D6DEFF9060000000000000000000000000000
TABH+ 20(20) = E0000000F6020000010000003A020000FFFFFFFF
TABH+ 40(16) = 042A0200600B000010000000C1248401
store = 0xE06D6DEFF9060000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 224 (0xE0000000)
label = 758 (0xF6020000)
fill = 1 (0x01000000)
leng = 570 (0x3A020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000046
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x80095FEFF9060000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 540 (0x1C020000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
OBJECT_HD_CHANGE-OBJDES
Workflow 405090 set to status ERROR
56766667233333327672762776777245545222222222222222
7F2B6CF70405090035404F03414530522F2000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
%_FSREG_001
OBJCONT
Table IT_760[9x510]
\CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJCONT
Table reference: 225
TABH+ 0(20) = 106F6DEFF9060000000000000000000000000000
TABH+ 20(20) = E1000000F802000009000000FE010000FFFFFFFF
TABH+ 40(16) = 042A0200300B000010000000C1248401
store = 0x106F6DEFF9060000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 225 (0xE1000000)
label = 760 (0xF8020000)
fill = 9 (0x09000000)
leng = 510 (0xFE010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000045
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x402D5FEFF9060000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 541 (0x1D020000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
OWNER
222222222222
000000000000
000000000000
000000000000
SENDER
222222222222
000000000000
000000000000
000000000000
SY-SUBRC
0
0000
0000
SWFCO_MAIL_ERROR_NOTIFY
0002
3333
0002
0000
0000
OBJECT_HD_CHANGE
E ERRORMESSAGEWorkflow 405090 set to status ERROR 00000000000000 F F S
4222222222245545445544456766667233333327672762776777245545222222222222222233333333333333242425
50000000000522F2D5331757F2B6CF70405090035404F03414530522F2000000000000000000000000000000060603
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OBJECT_TYPE
RAW
545
217
000
000
SWFCO_OBJTYPE_BOR
BO
44
2F
00
00
No. 23 Ty. METHOD
Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL
LT_AGENTS
Table IT_752[1x28]
\CLASS=CL_SWF_RUN_WIM_LOCAL\METHOD=IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL\DATA=LT_AGEN
Table reference: 207
TABH+ 0(20) = 806B6DEFF9060000000000000000000000000000
TABH+ 20(20) = CF000000F0020000010000001C000000FFFFFFFF
TABH+ 40(16) = 04180100E006000010000000C1248401
store = 0x806B6DEFF9060000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 207 (0xCF000000)
label = 752 (0xF0020000)
fill = 1 (0x01000000)
leng = 28 (0x1C000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000022
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xA0696DEFF9060000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 537 (0x19020000)
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
SYST-REPID
CL_SWF_RUN_WIM_LOCAL==========CP
4455545554554454444433333333334522222222
3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD+840(28)
WS20000014
55333333332222
73200000140000
00000000000000
00000000000000
SY-REPID
CL_SWF_RUN_WIM_LOCAL==========CP
4455545554554454444433333333334522222222
3CF376F25EF79DFCF31CDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
FUNCNAME
SWW_WI_DISPLAY_FOR_MAIL
555554544554455445544442222222
377F79F4930C19F6F2FD19C0000000
000000000000000000000000000000
000000000000000000000000000000
SWFCO_WI_REMOTE
R
5
2
0
0
PARAMETER-NAME
WI_ID
54544
79F94
00000
00000
SWFCO_CALLBACK_AGENTS
CALLBACKAGENTS
54444444454444552222222222222222
F31CC213BF175E430000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
PARAMETER-VALUE
000000405090
333333333333
000000405090
000000000000
000000000000
ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD-WI_ID
000000405090
333333333333
000000405090
000000000000
000000000000
PARAMETER
807020C0
7080A050
00000000
00100010
LS_MAILOBJ
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME
60009000
3000C000
SWFCO_WORKITEM_OBJECT
_WORKITEM
55454454422222222222222222222222
F7F2B945D00000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
No. 22 Ty. METHOD
Name CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL
SWFCO_WORKITEM_OBJECT
_WORKITEM
55454454422222222222222222222222
F7F2B945D00000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
No. 21 Ty. METHOD
Name CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION
IM_STATE_ACTIONS
Table IT_279[30x152]
\CLASS=CL_SWF_RUN_WIM_STATE_FLOW\DATA=M_STATE_ACTIONS
Table reference: 112
TABH+ 0(20) = 90CE53EFF9060000B04D6BEFF906000000000000
TABH+ 20(20) = 70000000170100001E0000009800000090010000
TABH+ 40(16) = 049A01007004000010000000C9248001
store = 0x90CE53EFF9060000
ext1 = 0xB04D6BEFF9060000
shmId = 0 (0x00000000)
id = 112 (0x70000000)
label = 279 (0x17010000)
fill = 30 (0x1E000000)
leng = 152 (0x98000000)
loop = 400 (0x90010000)
xtyp = TYPE#000009
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 1 (ItIndexLinear)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xF0C453EFF9060000
pgHook = 0xF0CE53EFF9060000
idxPtr = 0x50E253EFF9060000
shmTabhSet = 0x0000000000000000
id = 207 (0xCF000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 48 (0x30000000)
lineAlloc = 48 (0x30000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x204C6BEFF9060000
collHook = 0x0000000000000000
ext2 = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
SWFCO_WI_NO_DEADLINE
0000
3333
0000
0000
0000
L_OBJ
A0005000
D0002000
ME
A0005000
D0002000
ME->IF_SWF_RUN_WIM_STATE~NEW_STATUS
ERROR
455452222222
522F20000000
000000000000
000000000000
<%_L003>
ERROR
455452222222
522F20000000
000000000000
000000000000
SY-REPID
CL_SWF_RUN_WIM_STATE==========CP
4455545554554455545433333333334522222222
3CF376F25EF79DF34145DDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
<%_L004>
F
4
6
0
0
<STATE_ACTION>
FERROR 01DYN_SEND_ERROR_REPAIR_MAIL
4455452222222334545544454554555454455444422222222222222222222222222222222222
6522F200000000149EF35E4F522F2F250192FD19C00000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000
<%_L002>
<%_L002>-WI_STAT
SYST-REPID
CL_SWF_RUN_WIM_STATE==========CP
4455545554554455545433333333334522222222
3CF376F25EF79DF34145DDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SWFCO_WI_STATUS_WILD_CARD
222222222222
A00000000000
000000000000
000000000000
<%_L002>-WI_TYPE
<STATE_ACTION>-METHOD
DYN_SEND_ERROR_REPAIR_MAIL
4545544454554555454455444422222222222222222222222222222222222
49EF35E4F522F2F250192FD19C00000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000
%_SPACE
2
0
0
0
LV_EXCP
F0000000
F0000000
No. 20 Ty. METHOD
Name CL_SWF_RUN_WIM_STATE_FLOW=>Hello,
Get help from your abaper on this.
Vinay -
Status of the background task is ready. We already corrected the background step so we tried to use SWIA to restart workitem. But accidentally, we placed the main instance number. Now the status of the workflow is error (in swi2_freq). We tried to use SWPR to restart workflow, we placed the main instance number but we are having runtime error after clicking 'restart workflow' button.
Runtime Errors: OBJECT_OBJREF_NOT_ASSIGNED
Exception: CX_SY_REF_IS_INITIAL
Short text: Access via 'NUL' object reference not possible.
Thanks!In the workflow you are trying to refer a method which does not has any insatnce please check in the seconndary methods tab of the respective step in the workflow definiton.
Beacuse , IN that tab if you are trying to refer any methods , then you should have a container element reffering to the object with instance..., So tehre could be a possibility that you are using this tab.....
Please check and can you please let us know what for what process actualyy you are trying to trigger the workflow... I eman is it a standard workflow or customized.... I mean like Leave or TRAVEL.... -
Runtime error in preview pdf tab for formdesigner.exe in acrobat pro x
when we click on the preview pdf tab in the livecycle designer for acrobat pro 10.0.2, we receive a runtime error for formdesigner.exe. This has happened on 2 different machines we tested on. Please advise.
Hi,
Please follow the suggestions provided here : http://helpx.adobe.com/acrobat/kb/runtime-error-roaming-profile-workflows.html -
OOTB workflow gives error when user rejects in the document in publishing a major version.
Hi All,
I am using OOTB workflow with little customization with following configuration
1. Allow content approval enabled
2. Configure a workflow with following general settings true
3. Start workflow on publish of Major version only is enabled
4. workflow has following configuration enabled.
Now, when user start publishing of major version and Starts the workflow. workflow starts without any problem.
But as and when the user rejects the document it is rejected with Reject status with "Approval Status" as well as workflow status which is expected.(This is correct )
But when i look at the workflow history i can see at last line there is an Error with
An error has occurred in In [Workflow Name].
Now when user check out and check in item again and try to publish with Major version again. it gives errors that the previous version is still running.
I have trace a lot and also test with original OOTB workflow itself. it is behaving the same.
As per my findings there is problem in "Completion condition of this task process" the end task process is not being executed correctly.
I tried to end the task process with End the task process action but it is still not working.
I need some help in this issue as users are facing problems in case of rejection. I hope some one has the solution for the same.
Two things i have noticed are
1. My MS office 2010 professional plus is expired as i was using trial version
2. I have made stop inheriting tasks permission and remove all default groups as i have settings in workflow "Only allow task reception and process owner to read and edit workflow task"
3. Earlier i had also installed "Sharepoint 2010 April 2012 updates". i had also observed that (installing Sharepoint 2010 April 2012 updates) before that if user has selected "Automatically rejects the document if any participant rejected". it ends
with "rejected" status. At present it remains in inprogress and not stops with rejected status.
Can any one give me a hint what should be the problem ? Is it a problem with latest Sharepoint 2010 April 2012 updates ?
Thanks,
S. M. MANIYARI have done following testing.
1. The server in which i have not installed sharepoint 2010 April 2012 updates the above scenario is working fine without any problem
2. I have also observed following logs of error in server where April 2012 updates is installed.
8/28/2012 03:51:41.33 w3wp.exe (0x0F08) 0x0A00 SharePoint Foundation
Workflow Infrastructure 88xr Unexpected WinWF Internal Error, terminating workflow Id# 8bf7fef1-c92e-4b22-a16f-480425d3adc6
08/28/2012 03:51:41.33 w3wp.exe (0x0F08) 0x0A00 SharePoint Foundation
Workflow Infrastructure 98d4 Unexpected System.InvalidOperationException:
CompositeActivity cannot transition to 'Closed' status when there are active child context still exist for child activity. at System.Workflow.ComponentModel.Activity.MarkClosed() at System.Workflow.ComponentModel.ActivityExecutionContext.CloseActivity()
at Microsoft.Office.Workflow.Actions.OfficeTask.FinalClose(Object sender, EventArgs eventArgs) at System.Workflow.ComponentModel.ActivityExecutorDelegateInfo`1.ActivityExecutorDelegateOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
at System.Workflow.Runtime.Scheduler.Run()
Following are last two lines of workflow history.
S. M. MANIYAR -
Runtime Errors: DYNPRO_SEND_IN_BACKGROUND
Hi,
There are lots of dump called DYNPRO_SEND_IN_BACKGROUND in my prd system. The short text of the dump is Screen output without connection to user.
Runtime Errors DYNPRO_SEND_IN_BACKGROUND
Short text
Screen output without connection to user.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPMSSY0" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
During background processing, the system attempted to send a
screen to a user.
Current screen: "SAPMSSY0 " 0120.
I already check the logical connections in SM59 and i have rfc destination WORKFLOW_LOCAL_010 with user logon WF-BATCH, i run also SWU3 transaction to configure workflow.
Anyone could help me.
Thanks,
BismitaHI,
Error in the ABAP Application Program
The current ABAP program "SAPMSSY0" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
During background processing, the system attempted to send a
screen to a user.
Current screen: "SAPMSSY0 " 0120.
"DYNPRO_SEND_IN_BACKGROUND" " "
"SAPMSSY0" or " "
"SYSTEM-EXIT"
Dump message: "DYNPRO_SEND_IN_BACKGROUND" " "
Program Name and Screen no: Current screen: "SAPMSSY0 " 0120.
As per our analysis using where user list this program hits 1.ECATT(Script), 2. Internet service.
We have deactivated the ECATT in production even though getting the same dump.
I don’t have any knowledge about internet service, so kindly suggest to me.
Regards,
Bismita
Maybe you are looking for
-
F4 Help for KONZS field in KD03
Hi All, Could you please help to add the search help for KONZS(Corporate help) in XD03 t.code ECC6.0 system. Thanks, Harinath
-
The scenario is like I am reading data from the attachment of an email using mail sender adapter and creating a file at unix server. The mail attachment looks like this : Lead code:12929 Order ref: sp/jaksd/1212 order type: S Item code
-
Scripting Language Options for the Script Task Options SSIS 2012
Can python or perl be used as a script language in the drag and drop script task? I believe only VB.Net and C# are, but I see under SSDT Tools -> Options there are some choices for Python Debugging? I'd like to use python as my SSIS scripting languag
-
Could not create pool connection. the dbms driver exception was : null
Hi, I am creating Data source to connect to my DB2 database Details of the connections are as follows 1) URL : jdbc:as400://hostname;translate binary=true 2) Driver class : com.ibm.as400.access.AS400JDBCDriver am getting following error when I am try
-
[Solved] Errors when starting openldev?
Hi, I used openldev for a project a while back and I know that it was upgraded since I used it. I went to start it today and I get the following errors: failed to open libtool archive "/usr/lib/openldev/libinsertinfo.la" failed to open libtool archi