Urgent - workflow stopped today

Hi guys,
We are using WS20000077 and WS20000075, both have been working fine until today. All of a sudden, when users create PR and/or PO, they can't see them in their Outbox, there's no notification to the approvers. I checked SWDD, the latest version are still both active, in SWEL, all events are triggered, event linkages are still active. What could be the problem here?
Many thanks,
Kathryn

Is the customizing still correct - SWU3
What happened to the workflows by viewing the log SWI1
Check if the system log shows what caused this, somthing like tablespaces are full
Check ST22 for shortdumps
Check if someone changed the org structure or authorizations
If you´ve done the above and the problem still persists, you can create an oss message with prio High (if this is in a production environment)
Kind regards, Rob Dielemans

Similar Messages

The touch screen is not working when I am in the Music app of my iPod Touch. How do I get it to begin working? It just stopped today.

The touch screen is not working when I am in the Music app of my iPod Touch. How do I get it to begin working? It just stopped today.
Does anyone know what I can do? I am unable to switch screens, and I can not see the track that is playing. The only was I can switch between songs is to use the controls on my headphones.

Try the stamdard fixes to rule out a software problem:
- Reset. Nothing will be lost
Reset iPod touch: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Restore from backup
- Restore to factory defaults/new iPod.

Workflow stopped working when we added new person to dummy HR position

Hi,
We have a third party expense reporting system which apparently sends some sort of IDOC to our SAP system. This uses a HR dummy position in a dummy org to which users have been assigned. These users are supposed to receive workflow emails that are expense reporting related.
In August we added a person to this HR position and there were no issues.
In October we added a person to this HR position and workflow stopped working. We tried taking the person back off who was last added and workflow will not come back on.
How do we get the workflow to process again? We can figure out why that one person didn't work if we can get the workflow working for the other 5 people going again.
Sorry for the high level details of the issue. I haven't worked all the parts of it and am just pulling info from people to try and help find a solution.
UPDATE:
Here is the problem as described by my colleague.
For the Concur expense reporting system, the data from the Concur system is communicated as IDOCs to SAP through the PI middleware. When these IDOCs fail during the inbound processing (status 51) emails will be triggered and sent to the org unit (position - 50003828). A change was made to the position by the HR team on Oct 7th (a new user was added and one was removed). Since then the users have stopped receiving emails. The workflow has stopped.
We tried to take that new user back off and the email did not start back up. We would like to get it started again and then figure out how to add that new user without an issue.
Thanks,
Wendy
Edited by: Wendy Miller on Nov 11, 2011 11:59 AM

Hello,
"A change was made to the position by the HR team on Oct 7th (a new user was added and one was removed). Since then the users have stopped receiving emails. The workflow has stopped."
The fact that the users have stopped receiving emails does not mean that the workflow has stopped. Ask your colleague why he thinks that.
My guess: a change was made to that position, for example it was date-delimited so that it's no longer valid.
As suggested above, look in SWI1. It'll be very easy if you know what the workflow number (WS....) is.
Is it absolutely certain that it's a workflow sending these mails? If you look at an example of a mail, who was it sent by?
Applying SWI1_RULE would only help if there was just one new user not receiving emails.
regards
Rick Bakker
hanabi technology

Workflow stopping @ beginning of sub workflow

Guys,
I am calling Sub workflow from MAIN workflow.
Processing of Main workflow stopping @ the STEP, wherein i trigger sub workflow.
The status is : In process. (it is a background task to trigger sub workflow)
If i process it manually with SWIA t-code , it is porcessing further.
But, it is not processing automatically.
Please guide.......
Regrads.
santosh.

Hi Arghadip,
Design Description of MAIN WF.
BO: ZBUSECM(original: ECM).
1)WF get triggered by ECO(CC01).
2)ACTIVITY STEP to extract fields for both (Material & BOM ).
3)2 level FORK to trigger BOM & Material WF.
4) CONDITION to check flags for both BOM & Material.
5) BOM : if yes, reset flag to space & proceed. if no, no action. proceed further. till end of FORK.
6) MATERIAL :if yes,reset flag to space
6a)BLOCK to trigger material WF.
6b)STEP to Trigger material WF(This will call sub workflow).
6c)WAIT step to receive material WF "COMPLETED" event.
6d)ENDBLOCK to trigger material WF.
7) END of 2 level FORK.
8) ECH: Release ECO.
9) WAIT step to ECM Close.
10) Send mail for ECM Closure Notification.
11) WF Complete.
Design Description of Material(SUb) WF.
BO: ZBUS1001(supertypel: BUS1001006).
starting from 6b above.
1)WF get triggered by 6b event "INITIATE".
2)ACTIVITY STEP to send the material for editing to MM COntroller agent.
3) ACTIVITY STEP to send material for editing to fianance agent.
4) ACTIVITY STEP to complete the sub flow by triggering custom event "ZMANITRIGGERMATWFCOMPLETE" , which further calls the "COMPLETED" event by function module to hand over the control back to MAIN WF.
Now, the above mentioned step(4) is not handing over the control to main WF........
& also matnr is not being passed to sub flow now........
Regards & thanks.
santosh.
Edited by: santosh koraddi on Jun 22, 2010 7:22 PM

Workflow stop at container operation

Hi,
I have problem in workflow.
My workflow stop at container operation and i don't have any idea why it could happend.
[Workflow Stop|www.freeimagehosting.net/uploads/4132b300f6.gif]
Thanks,

Hi,
Can you check the workflow log with technical details.
I think it would give you better idea what is happening?
Try refreshing the buffer.
Regards,
Raj

Workflow stops at very weird point...

Since today I am having some extremely weird Workflow issues. Workflows just appear
to stop randomly at the middle where they were working fine yesterday. For example, I have the following three consecutive Write To History blocks:
The first two blocks write a line succesfully to the history list and then it just stops. Third block writes nothing.
Really clueless here, service status for worklows is OK I just checked.... Anyone an idea?

OK, now not anymore. Didn't change anything.

Apple Mail stopped today; server suddenly redirects through Yahoo

At about noon today my AppleMail stopped loading. Somehow the incoming server address got changed to redirect through Yahoo (I've never had a Yahoo acct), and the box is greyed-out so I can't change it. Frustrated. This has happened with three email addresses I use. Until a couple of hours ago the outgoing server was fine but now that won't even work. The computer has slowed down and is nearly unresponsive.

Thanks much.
I get a dialogue box that says Internet Account Preferences can't connect to the account. It asks for the password. When I type it in, I get a message Unable to Verify Account Name or Password. This happened on all three email addresses. There was no "Advanced" option to select. (I'm able to access all of my mail through Verizon's website; it's just Apple Mail that is the problem. It is very slow in responding in any direction: click on a folder and it takes many seconds to open; try to open a new blank message, it takes several seconds and then the curser sticks or doesn't work). All other applications are working okay but considerably slower than earlier today.
I made an appointment at the Genius Bar for tomorrow. Maybe this has something to do with Yosemite, but I downloaded that several days ago and it's been working well.

URGENT: RSL Stopped Working - Need to compile with Runtime Shared Library

I need this target to compile using the “Use Runtime Shared Library” option such that Flex libraries will be not included IN the swf, however I cannot get it to work. No matter what, mxmlc includes them. Oddly it DID work briefly for short time, however suddenly stopped again and unfortunately going through subversion revision history yields no insight whatsoever to what evoked this breakage.
<target name="compile" depends="replace_build_version">
 <exec executable="${FLEX_HOME}/bin/mxmlc.exe" dir="${basedir}">
 <arg value="${basedir}/src/Main.mxml"/>
 <arg value="-output=${basedir}/bin-release/Main.swf"/>
 <arg value="-static-rsls=false"/>
 <arg value="-debug=false"/>
 <arg value="-include-libraries=${basedir}/libs"/>
 <arg value="-source-path=${basedir}/src"/>
 <arg value="-creator=me"/>
 <arg value="-source-path=${basedir}/locale/en_US"/>
 <arg value="-source-path=${basedir}/locale/ru_RU"/>
 <arg value="-locale=en_US" />
 <arg value="-include-resource-bundles=en_US,ru_RU"/>
 <arg value="-runtime-shared-library-path=${FLEX_HOME}/frameworks/libs/framework.swc,http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/framework_4.1.0.16076.swz,http://fpdo wnload.adobe.com/pub/swz/crossdomain.xml"/>
 <arg value="-runtime-shared-library-path=${FLEX_HOME}/frameworks/libs/textLayout.swc,http://fpdownload.adobe.com/pub/swz/tlf/1.1.0.604/textLayout_1.1.0.604.swz,http://fpdownlo ad.adobe.com/pub/swz/crossdomain.xml"/>
 <arg value="-runtime-shared-library-path=${FLEX_HOME}/frameworks/libs/osmf.swc,http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/osmf_flex.4.0.0.13495.swz,http://fpdo wnload.adobe.com/pub/swz/crossdomain.xml"/>
 <arg value="-runtime-shared-library-path=${FLEX_HOME}/frameworks/libs/spark.swc,http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/spark_4.1.0.16076.swz,http://fpdownlo ad.adobe.com/pub/swz/crossdomain.xml"/>
 <arg value="-runtime-shared-library-path=${FLEX_HOME}/frameworks/libs/sparkskins.swc,http://fpdownload.adobe.com/pub/swz/flex/4.1.0.16076/sparkskins_4.1.0.16076.swz,http://fpd ownload.adobe.com/pub/swz/crossdomain.xml"/>
 <arg value="-external-library-path=${FLEX_HOME}/frameworks/libs/flex.swc"/>
 <arg value="-theme=${FLEX_HOME}/frameworks/projects/spark/MXFTEText.css"/>
 <arg value="-theme=${FLEX_HOME}/frameworks/themes/Spark/spark.css"/>
 <arg value="-verbose-stacktraces"/>
 </exec>
 </target>

I really hate to do this, but I very much need someone from Adobe to chime in here. It is causing some serious headaches. Ant nor the straight Flash Builder 4 will build with RSLs properly enabled now and this is really a very urgent situation for me. It has doubled file size and made the application absolutely unbearable for users.
Thanks!

Workflow stops going ahead

Dear all,
I created a very simple workflow. Besides the "start" and "end" step, there's only one step, which just writes a record into DB table. This step has no agent. I tested it via transaction SWUS but found the status is always "in progress". The progress stops at the step which should write to DB table. Can you help to solve this problem?
Thanks + Best Regards
Jerome

Hi Jerome,
did you mark your task as a background task?
And check the protocol of your WF in TA SWIA. It may give you a clue...
Peter

Windows Service Hosted workflow, Stop it with ServiceOperation call?

I am working on a POC for Scheduling Workflows. I have a workflow hosted with Workflow Services Host. Using a While activity I loop while KeepRunning = true. Using Pick-->PickBranch I have two ServiceOperations running in Receive activities in each
Branch. There is a StartWorkflow ServiceOperation in one branch and a StopWorkflow ServiceOperation in another branch. The StartWorkflow operation basically just runs another Workflow called RunWorkflow with a calculated Delay activity between each
completion. It will loop indefinitely on that RunWorkflow activity until the KeepRunning is set to false. The StopWorkflow ServiceOperation is what changes the KeepRunning flag to false. My problem is that the StartWorkflow operation never completes so that
the Messaging directed to StopWorkflow can take place. I have used a CorrelationHandle to group the two ServiceOperations together set to a Guid property on the incoming DataContracts (requests). Is there someway to get the StartWorkflow operation to stop
in this scenario?

HI Les G. Kinney,
Welcome to WorkFlow forum.
Workflow tracing offers a way to capture diagnostic information using .NET Framework trace listeners. Tracing can be enabled if a problem is detected with the application and then disabled again once the problem is resolved.
According to your description above, it's recommended to enable
workflow tracing first, it will give some hints why this happens.
Windows Workflow scheduling services manage how workflow instances are scheduled by the workflow runtime engine. This resource is also available. See:
https://msdn.microsoft.com/en-us/library/vstudio/ms735790(v=vs.90).aspx
Best regards,
Angie
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

URGENT - OracleListener stopped right away after starting it manually

Hi,
I have OracleEX 10g and Odp.NET 11g insalled in my machine, today I de-installed ODP.NET 11g, after that I could not make the database to run anymore, I tried to run OracleExListener in the Services, but it stopped right away after starting it.
how to fix this?

Thank you very much for your reply :)
I am very bigginer with Oracle, but I can provide you with the infor in the listener.log
TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production on 20-FEB-2008 14:17:50
Copyright (c) 1991, 2005, Oracle. All rights reserved.
System parameter file is C:\oraclexe\app\oracle\product\10.2.0\server\network\admin\listener.ora
Log messages written to C:\oraclexe\app\oracle\product\10.2.0\server\network\log\listener.log
Trace information written to C:\oraclexe\app\oracle\product\10.2.0\server\network\trace\listener.trc
Trace level is currently 0
Started with pid=912
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC_FOR_XEipc)))
Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=user)(PORT=1521)))
TNS-12545: Connect failed because target host or object does not exist
TNS-12560: TNS:protocol adapter error
TNS-00515: Connect failed because target host or object does not exist
32-bit Windows Error: 1001: Unknown error
No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC_FOR_XEipc)))
I am not faimilar how to reconfigure, and I would really appreciate if someone can give step-by-step guid..
thanks,

Moving Workflows stops email tickets being generated

Hi Guys,
I'm trying to move workflows from Management Server A to Management Server B.
The steps I followed were:
On Management Server B:
Stop System Center Data Access Service and Microsoft Monitoring Agent and System Center Management Configuration services
Delete the Health Service State folder in \Program Files\Microsoft System Center 2012\Service Manager
Connect to ServiceManager Database instance
Run: EXEC p_PromoteActiveWorkflowServer ManagementServerB.local on ServiceManager db
Restart services on Management Server B
After this was performed emails being sent in were not coming through. I reran the query chnaging it back to Management Server A and they all came through. The exchange connector was originally setup on Management Server A. has anyone had this issue?
I'm using SCSM 2012 R2. on Server 2012.

The exchange connector uses the EWS APIs. the exchange connector runs on the workflow server (since the work done for the connector is in a workflow). Whoever set up your exchange connector the first time had to install these DLLs into the service manager
folder on the workflow server the as part of installing the connector (see the exchange connector's install guide, the DOCX file on
this download page).
if you moved the workflows by promoting a different server, and that different server didn't have the EWS API dlls from the above link copied into the Service Manager folder, then you would see the exchange connector failing in this way.
Can you tell if any other workflows are running sucessfully on the new server?

Workflow stopped at background step

Hi Experts,
I have a background step in my workflow , when iam testing this workflow from SWUS the workflow is getting stopped at this background step the workflow is not going forward to next step. the workflow log shows ' task started in background'
moreover i did't find any errors in the log for the same.and i checked SM37 there the relevent job is finished. please advice what canbe the problem?
Thanks & Regards,
Sarath.

HI Sarath ,
Just change yuor task from BAckgroung to foreground. Insert a break point in the code of the function module used in the task and execute your workflow.
Coz you cant debug a background task , you will never come to know wht is happening inside .
By debugging get the problem in the code , rectify it and change the task again to the background .
Hope this will help.

Urgently Upgrade Stop In XPRAS_UPG Phase

Hi all,
This is our infrastructure:
Windows 2000
Oracle 9.2.0.7
SAP 4.6B
Kernel Release 46D
We are upgrading our DEV System to R/3 Enterprise 4.7 Ext. 2 Sr1
Our Upgrade Process Stop in the XPRAS_UPG Phase. Basically it gives this error:
WARNING: tp terminated with status 12
R3up> ERROR: tp terminated with error status -1
R3up> ERROR: 2 errors detected during XPRAS_UPG
R3up> ERROR: 1 activities have been aborted in XPRAS_UPG
R3up> ERROR: Operation(s) not completely processed.
 Remaining change request found in buffer TVD.
 Ignoring aborted import steps will cause severe inconsistencies
Logs that we reviewed:
XPRASUPG.ECO and R3up.ECO
the problem is with the RDDEXECL JOB. Which is in the status CANCELED
When we Check the JOB LOG it gives this:
 22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17

The conversion of some code pages is not supported.
What happened? 
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
 An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
 'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(FORM)".
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X u00F0####u00CCu00FF#,").
Please Some help!
We saw this note:
122597 Ignoring errors in the phase XPRAS
So we try with the option "u00CFgnore" + "Repair Severe Errors" but nothing happens, in remains in the same place, Start the Phase a again and Stop at the same point.
676135 Short Dump when you import Support Packages
This notes explain this: (Page 3 Paragraph 3)
If you are still upgrading, import the transport order into the system using 'R3trans -i <data file name>'. Enter the correct path to the data file (possibly DIR_PUT).
But we are scared about to STOP the upgrade here (Like 'cancel' option instead of continue and after restart the upgrade) does somebody apply this note?
This are the logs:
XPRASUPG.ECO
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR620ZF1.TVD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10593502")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""10593502""TVD"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
R3up.ECO:
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15160 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022101802
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 16400 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022105721
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15096 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Best Regards,
Desiree Cardenas

Hi Eric,
In fact in the previous post you can see:
the problem is with the
RDDEXECL JOB. Which is in the status CANCELED
When we Check the JOB LOG it gives this:
22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(FORM)".
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
Sorry for the big amount of information. I will put the complete JOB LOG.
LOG:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
If the application required you to enter a code page, you may be able to
avoid the error by restarting the application and entering a different
code page.
You can display the available codepages using the transaction SCP. For
more utilities for codepages, use the transaction SNLS.
Error analysis An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure
"READ_TEXTLINES" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
How to correct the error
The exception must either be prevented, caught within the procedure
"READ_TEXTLINES"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"CONVT_CODEPAGE_INIT" CX_SY_CODEPAGE_CONVERTER_INITC
"SAPLSTXD" or "LSTXDFDB"
"READ_TEXTLINES"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
 To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
 To obtain this, call the system log with Transaction SM21
 and select the "Print" function to print out the relevant
 part.
3. If the programs are your own programs or modified SAP programs,
 supply the source code.
 To do this, you can either use the "PRINT" command in the editor or
 print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
File attributes no file
System environment
SAP Release.............. "620"
Application server....... "vensapd"
Network address.......... "10.55.46.71"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 11
Short dump setting....... "full"
Database server.......... "VENSAPD"
Database type............ "ORACLE"
Database name............ "TVD"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Jun 25 2004 20:55:59"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "21"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "SAPLSTXD"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLSTXD" in "READ_TEXTLINES".
The main program was "RDDEXECU ".
The termination occurred in line 82 of the source code of the (Include)
program "LSTXDFDB"
of the source code of program "LSTXDFDB" (when calling the editor 820).
The program "SAPLSTXD" was started as a background job.
Processing was terminated because the exception "CX_SY_CODEPAGE_CONVERTER_INIT"
occurred in the
procedure "READ_TEXTLINES" "(FORM)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "SAPLSTXD ". Its source code starts in line 75
of the (Include) program "LSTXDFDB ".
Best Regards,
Desiree Cardenas

Urgent : Workflow with two steps

Hi All,
i am doin a workflow in which i am using a activity step first to display the PO/SO and then a user decision step for either approving or rejecting it.
bt once the activity step (work item in SAP inbox) is executed, the workflow is terminated.
the user decision step is not executed.
can anyone assist how can i make both step work synchronously?
Thanks in advance.

it is difficult to understand the issue. I request you to just do Business Business Object binding from Wflow to task in the decsion step. By doing that you will get the link of the PO/SO and you can use the decision also.
By the way are the present task in sequential fashion. I dont think so. It appears they are in a fork of 2 parallel branch and 1 necessary branch wich should not be the case change it 2 necessary branch
Thanks
Arghadip

Urgent - workflow stopped today

Similar Messages

Maybe you are looking for