Error in OTL Workflow

Hi,
I have defined the time categories.. One project was missed out, so when i submitted a time sheet it errored out. Now i have added it, and tried submitting new sheet with same data which worked but when i tried to rewind the existing one, it remained in error state..
Can anything be done to restore the errored out process to work....
Thanks in advance.
- Sujana

So it is happening only for the user who had an earlier stuck timecard?
How is the preference attached to the user? I guess you still have some issues due to the dates.
--Shiv

Similar Messages

Error in starting workflow queue listener

I have registered jobs with OEM using Warehouse builder workflow deployment
wizard. Following jobs has been registerd with OEM :
1) ACRM_IWF_ACRM_PWF
2)ACRM_IWF_OWB_STD_BEGIN
3) ACRM_IWF_OWB_STD_END
4) ACRM_IWF_OWB_STD_ERROR
Now i submit "ACRM_IWF_ACRM_PWF" from the OEM . I shows me status of the JOB as
"Failed" and gives the following error message:
Error in starting workflow listener: ** Initializing queue listener
** Initialized queue listener
** Recovering item type ACRM_IWF
** In recovery mode
** Recovery complete
** Processing all item types
** Waiting to dequeue message in listener
** Processing job 0x4143524D5F4957465F4F57425F5354445F424547494E
Exception in thread "main" java.lang.StringIndexOutOfBoundsException: String
index out of range: -1
at java.lang.String.substring(String.java:1085)
at
oracle.wh.runtime.workflowrt.QueueListener.parseParameters(QueueListener.java:10
03)
at oracle.wh.runtime.workflowrt.QueueListener.startJob(QueueListener.java:798)
at
oracle.wh.runtime.workflowrt.QueueListener.processJobs(QueueListener.java:746)
at
oracle.wh.runtime.workflowrt.QueueListener.initAndRun(QueueListener.java:299)
at oracle.wh.runtime.workflowrt.QueueListener.main(QueueListener.java:197)
1

This is not actually a Workflow component, this is part of the Oracle Warehouse Builder product, although the name is similar to the Workflow Agent Listener in v2.6.
I have registered jobs with OEM using Warehouse builder workflow deployment
wizard. Following jobs has been registerd with OEM :
1) ACRM_IWF_ACRM_PWF
2)ACRM_IWF_OWB_STD_BEGIN
3) ACRM_IWF_OWB_STD_END
4) ACRM_IWF_OWB_STD_ERROR
Now i submit "ACRM_IWF_ACRM_PWF" from the OEM . I shows me status of the JOB as
"Failed" and gives the following error message:
Error in starting workflow listener: ** Initializing queue listener
** Initialized queue listener
** Recovering item type ACRM_IWF
** In recovery mode
** Recovery complete
** Processing all item types
** Waiting to dequeue message in listener
** Processing job 0x4143524D5F4957465F4F57425F5354445F424547494E
Exception in thread "main" java.lang.StringIndexOutOfBoundsException: String
index out of range: -1
at java.lang.String.substring(String.java:1085)
at
oracle.wh.runtime.workflowrt.QueueListener.parseParameters(QueueListener.java:10
03)
at oracle.wh.runtime.workflowrt.QueueListener.startJob(QueueListener.java:798)
at
oracle.wh.runtime.workflowrt.QueueListener.processJobs(QueueListener.java:746)
at
oracle.wh.runtime.workflowrt.QueueListener.initAndRun(QueueListener.java:299)
at oracle.wh.runtime.workflowrt.QueueListener.main(QueueListener.java:197)
1

Having problems with Bridge shutting down after saving photo in PS Cs5,,,,,,,,, Also when i attempt to update either PS or bridge get an error message in Adobe application manger "Error loading updater workflow"

Having problems with Bridge shutting down after saving photo in PS Cs5,,,,,,,,, Also when i attempt to update either PS or bridge get an error message in Adobe application manger "Error loading updater workflow"

Sorry for the late reply. My email firewall has become a little over zealous & sent a lot of my emails straight to my junk email folder, so I have only just now discovered your reply in my junk mail folder.
The only "don't open files exceeding xxx megabytes" instruction I can find in my Prefs, is in the Bridge Prefs for Thumbnails, & mine is set at 1000mb. The biggest files I handle are bigger than 200mb so I should be able to open a few, not just one.
However, this doesn't explain why I can open a psd format file of 180mb, close it, but then can't open a RAW format file of only 26mb immediately after.
I can open the RAW file only if I restart my computer - very annoying!
However, thanks for the advice about the video card & memory.
So, I'm still stuck as to what the issue is.

Getting error while publishing workflow using SP designer for SharePoint 2013

Hi,
I am try to setup Workflow manager for our sharepoint applications.
WF manager set ran without any issue.
I registered the SPWorkflow service which succeeded as well. The Workflow service application shows "Workflow is connected"
I am creating a workflow using sharepoint designer using my credential (not Service account). I am able to save it but while publishing, its prompting with an error.
The error says "Errors were found while compiling the workflow.The workflow files were saved but cannot run." Clicking advanced button show
"Microsoft.SharePoint.SPException: We're sorry, we weren't able to complete the operation, please try again in a few minutes. If you see this message repeatedly, contact your administrator.
at Microsoft.SharePoint.SPScaleOutDatabaseMap.CreateSqlSession(ISPScaleOutDatabaseMapProvider mapProvider, Byte[] compositeKey, Guid forceRefreshVersion, Guid& version)
at Microsoft.SharePoint.SPScaleOutDatabaseCommandExecutor.Execute(ExecuteDelegate operation, ISPScaleOutDatabaseMapProvider mapProvide"
Any help would be highly appreciated
Thanks,

Hi,
According to your post, my understanding is that you got error while publishing workflow using SharePoint designer for SharePoint 2013.
Please check whether the Central Admin > Manage Service Application-> “App Management Service” is started.
Please check whether the “Configure service application associations”, ”App Management Service” is already associated.
Then please check whether the “Manage Services on server” and the “App Management Service” is started.
In addition, please try to re-register Workflow Service.
If the issues still exists, please follow the steps in the
Steps to Verify that Server Is Correctly Set Up. After you verified that the server is correctly set up, follow the steps in the
Steps to Troubleshoot Workflow Management Service and
Troubleshooting the Service Bus for Windows Server then retry your action related to publishing workflows
More information:
http://wp.ahcheng.com/2013/03/23/error-were-found-when-compiling-the-workflow-the-workflow-files-were-saved-but-cannot-be-run/
http://sp2013.pro/2013/04/solution-errors-were-found-when-compiling-the-workflow-the-workflow-files-were-saved-but-cannot-be-run-cannot-set-unknown-member/
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Error while querying workflow message attributes for task

Can some one please help me with this error?
I get this error when I submit a task in worklist app. I have figure out that it is causing due to one payload in the table in the task. If remove that payload I am able to submit the task.
Error while querying workflow message attributes for task a99d1cf3-5e91-4c4a-8660-aeae91bfbec0 with version 5.
Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
oracle.jbo.JboException: Error while querying workflow message attributes.
Error while querying workflow message attributes for task a99d1cf3-5e91-4c4a-8660-aeae91bfbec0 with version 5.
Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services.
     at oracle.bpel.services.datacontrol.XSDDataControl.invokeOperation(XSDDataControl.java:460)
     at oracle.adf.model.bean.DCBeanDataControl.invokeMethod(DCBeanDataControl.java:430)
     at oracle.adf.model.binding.DCInvokeMethod.callMethod(DCInvokeMethod.java:261)
     at oracle.jbo.uicli.binding.JUCtrlActionBinding.doIt(JUCtrlActionBinding.java:1635)
     at oracle.adf.model.binding.DCDataControl.invokeOperation(DCDataControl.java:2144)
     at oracle.adf.model.bean.DCBeanDataControl.invokeOperation(DCBeanDataControl.java:467)
     at oracle.adf.model.adapter.AdapterDCService.invokeOperation(AdapterDCService.java:307)

Can anybody help me on this?
I did some google but I get this only which is not much helpful.
http://download.oracle.com/docs/cd/E14571_01/core.1111/e10113/chapter_bpm_messages.htm

Error when running workflow form list item - workflow manager SharePoint 2013

I am getting the following error in the workflow services log when I tried to run a SPD 2013 workflow from as list item. The workflow page comes up with an "An unexpected error has occurred"
page when opened:
Error processing management request. Method: GET, RequestUri: http://servername:12291/$Workflows/$Instances?$skip=0&$top=100&monitoringParameter=1f51aa43-2f1c-4fc5-a86d-f638ca57c00d, Error: System.Data.SqlClient.SqlException (0x80131904): The procedure "GetInstances" has no parameter named "@OtherWorkflowStatus".
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Gateway.HttpAsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Gateway.WorkflowServiceGateway.<>c__DisplayClass9d.<EndGetInstances>b__9c()
at Microsoft.Workflow.Gateway.WorkflowServiceGateway.ExceptionFilter[T](Func`1 body)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
ClientConnectionId:d2039360-b352-4d81-9bb7-b647e2938d06
Can't find anything on google.
Edit: Ok, when I look at the error, it is saying the the "GetInstances" stored procedure in the WFInstanceManagementDB database does not have a parameter named "@OtherWorkflowStatus".
For laughs, I added the parameter (which wasn't in there). Now I get the error:
Procedure or function 'GetInstances' expects parameter '@OtherWorkflowStatus', which was not supplied
It seems like there is something not right about my installation. Previously, I couldn't get the workflow backend service to run because there were config values missing from the workflow manager database. At the time I tried to uninstall/reinstall
WFM to no avail. I eventually had to manually add the values to get it to work. Something is not right about the WFM install/config process.

Here is what I had to do to get it working:
Leave the WFM (Workflow Manager) farm using the WFM config tool
Uninstall WFM, Service Bus, and the CU's from control panel
Uninstall Workflow Manager Client if it exists in the control panel, it didn't in mine
Delete the following databases in SQL Server:
SbGatewayDatabase
SbManagementDB
SBMessageContainer01
WFInstanceManagementDB
WFManagementDB
WFResourceManagementDB
Delete the workflow proxy service in Central Admin (important)
Application Management > Manage Service Applications
Highlight (select) the Workflow Service Application Proxy service (don’t click the hyperlink)
Select “Delete” from the ribbon.
Restart the server
Reinstall
Enable the workflow proxy service in CA for the web app, the 2013 workflow option will not show up in SPD unless you do this.
Application Management > Manage Web Applications
Select your web app
Select “Service Connections” from the ribbon
Check the Workflow Service Application Proxy item and click “OK”

Error in the workflow which executes background synchronous webservice task

Hi,
I am very new to SAP Workflows. I created a workflow with one activity step in it. The activity step actually executes a task TS77000300 (synchronous calculation - its an SAP task). When I test it. I get an error "Error when starting the service" with exception 8987, area SWF_HTTP and message 125 - Object WEBSERVICE method PROCESSBATCH cannot be executed.
I checked in WF_EXTSRV tcode, there is an entry for the background synchronous webservice task.
I checked in SWLWPTSSID table, there is an mapping between task-id and service id from WF_EXT SRV.
I am not sure where its going wrong. Any help resolving this issue is appreciated. Thanks a lot.
Regards,
Raja

Gurprit/All
Thanks Gurprit for the direction.
Even if I execute the the workflow( WS77000647 from SAP). The first step invokes Process Dialog which asks for three numbers and two operands. When I input all the input params and click calculate button, the second step which is actually the background synchronous task, results in the same error in the workflow log and in the Process Dialog page browser it says "Entries sent for calculation" with the same input screen.
Am I missing anything here to run background synchronous task? Any help regarding this is appreciated.
Thanks & Regards,
Raja

ORABPEL-9708 Error while querying workflow task WFTask. Caused by:ORA-00936

Hi,
I am trying to integrate my Primavera p6 web version8.0 with the BPM setup 11.1.1.3 . The BPM is setup fine.
But when I integrated with primavera p6 and on load of workflows portlet of p6 web where the BPM tasks are listed, I am getting following exception in BPM console:
Error while querying workflow task WFTask.
Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services. .
ORABPEL-9708
Error while querying workflow task WFTask .
Error while querying workflow task WFTask.
Check the underlying exception and the database connection information. If the error persists, contact Oracle Support Services. .
at oracle.bpel.services.workflow.repos.driver.WFTask.getWFTask(WFTask.java:2181)
at oracle.bpel.services.workflow.repos.driver.PersistencyService.getWFTask(PersistencyService.java:907)
at oracle.bpel.services.workflow.query.impl.TaskQueryService.queryTasks(TaskQueryService.java:751)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at oracle.bpel.services.workflow.common.WorkflowServiceCacheEventAdvice.invoke(WorkflowServiceCacheEventAdvice.java:89)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at oracle.bpel.services.workflow.test.workflow.ExceptionTestCaseBuilder.invoke(ExceptionTestCaseBuilder.java:155)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at oracle.bpel.services.common.dms.MethodEventAspect.invoke(MethodEventAspect.java:70)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at oracle.bpel.services.common.dms.MethodPhaseEventAspect.invoke(MethodPhaseEventAspect.java:82)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy220.queryTasks(Unknown Source)
at oracle.bpel.services.workflow.query.ejb.TaskQueryServiceBean.queryTasks(TaskQueryServiceBean.java:120)
at oracle.bpel.services.workflow.query.ejb.TaskQueryService_oz1ipg_EOImpl.queryTasks(TaskQueryService_oz1ipg_EOImpl.java:1019)
at oracle.bpel.services.workflow.query.ejb.TaskQueryService_oz1ipg_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.sql.SQLSyntaxErrorException: ORA-00936: missing expression
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:95)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:135)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:210)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:473)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:423)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1095)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:201)
at oracle.jdbc.driver.T4CCallableStatement.executeForDescribe(T4CCallableStatement.java:864)
at oracle.jdbc.driver.T4CCallableStatement.executeMaybeDescribe(T4CCallableStatement.java:948)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1335)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3568)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3620)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1667)
at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:135)
at oracle.bpel.services.workflow.repos.driver.WFTask.getWFTask(WFTask.java:2153)
at oracle.bpel.services.workflow.repos.driver.PersistencyService.getWFTask(PersistencyService.java:907)
at oracle.bpel.services.workflow.query.impl.TaskQueryService.queryTasks(TaskQueryService.java:751)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at oracle.bpel.services.workflow.common.WorkflowServiceCacheEventAdvice.invoke(WorkflowServiceCacheEventAdvice.java:89)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at oracle.bpel.services.workflow.test.workflow.ExceptionTestCaseBuilder.invoke(ExceptionTestCaseBuilder.java:155)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at oracle.bpel.services.common.dms.MethodEventAspect.invoke(MethodEventAspect.java:70)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at oracle.bpel.services.common.dms.MethodPhaseEventAspect.invoke(MethodPhaseEventAspect.java:82)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy220.queryTasks(Unknown Source)
at oracle.bpel.services.workflow.query.ejb.TaskQueryServiceBean.queryTasks(TaskQueryServiceBean.java:120)
at oracle.bpel.services.workflow.query.ejb.TaskQueryService_oz1ipg_EOImpl.queryTasks(TaskQueryService_oz1ipg_EOImpl.java:1019)
at oracle.bpel.services.workflow.query.ejb.TaskQueryService_oz1ipg_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Could anybody please help me out in resolving the issue?
Thanks and Regards,
Krish

I have the same problem with P6 R8 integration with BPM 11g (running on WL 10.3.5.0). Any sugestions how to solve this?

"error loading updater workflow"...trying to install camera raw 6.3 plug in

A very helpful response to an earlier question got me to realize the need to instll the latest raw plugin....6.3....
Now when I go to install I get "error loading updating workflow"
any help on this one???
Thanks
I have CS5 using windows 7 on my dell inspiiron 1545 pc......this was an update t cs5 from previously installed cs4
version

"PDA file "and "changed PDA file...."
PDA file
12/21/2010 11:35:13 PDApp - Build Version - 1.0.175.0
12/21/2010 11:35:13 PDApp - Logging Level verbosity Set to 4
12/21/2010 11:35:13 PDApp.CommandLineParser - Parsing the command
line provided. Number of command line arguments is 6
12/21/2010 11:35:13 PDApp - DWA AppletID argument not specified on
command line. Trying to find the existing instance
12/21/2010 11:35:13 PDApp - This is the first instance so creating a
thread for listening to the created pipe
12/21/2010 11:35:13 PipeThread - Pipe thread started
12/21/2010 11:35:13 PDApp - Starting AsyncMessageProcessor
12/21/2010 11:35:13 PDApp.AsyncMsgProcessor - AsyncMsgProcessor
initialized...
12/21/2010 11:35:13 PDApp.AsyncMsgProcessor - AsyncMsgProcessor
started. on thread id = 4960
12/21/2010 11:35:13 PDApp - Detecting Applet Database Library file...
12/21/2010 11:35:13 PDApp - Fetching Applet registeration
information...
12/21/2010 11:35:13 PDApp.AppletManager - AppletManager initialize...
12/21/2010 11:35:13 PIM - Build Version - 1.0.175.0
12/21/2010 11:35:13 PIM - Logging Level verbosity Set to 4
12/21/2010 11:35:13 PIM - CREATE PIM Instance ...
12/21/2010 11:35:13 Utilities - File does not exist
12/21/2010 11:35:13 PIM - trying to createOrUpdatePIMDbSchema.
12/21/2010 11:35:13 PIM - Current db schema version on machine 1.
12/21/2010 11:35:13 PIM - Current db schema version to install 1.
12/21/2010 11:35:13 PIM - PIM DB Schema is up to date. Current schema
version is 1.
12/21/2010 11:35:13 PIM - PIM Database is Up To Date.
12/21/2010 11:35:13 PIM - PIMSqlite closeDB status 0
12/21/2010 11:35:13 PIM - FREE PIM Instance ...
12/21/2010 11:35:13 PDApp.AppletManager - Applet database path -
C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\core\..
12/21/2010 11:35:13 PDApp.AppletManager - PIM library path -
C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\core\AdobePIM.dll
12/21/2010 11:35:13 PDApp.AppletManager - Loading PIM library...
12/21/2010 11:35:13 PDApp.AppletManager - Getting applet data from
Applet database
12/21/2010 11:35:13 PDApp.AppletManager - All installed pakages
version string (pim_getCurrentPackagesVersion) is
DWA:1.0.172.0|LWA:1.0.175.0|PDApp:1.0.175.0|UWA:1.0.175.0
12/21/2010 11:35:13 PDApp.AppletManager - Registering Applets...
12/21/2010 11:35:13 PDApp.WindowManager - Initializing native
WindowManager
12/21/2010 11:35:13 PDApp.WindowManager - Creating window instance
12/21/2010 11:35:13 PDApp.WindowManager - Checking for appletID and
appletVersion given in CommandLineOptions
12/21/2010 11:35:13 PDApp.WindowManager - Creating APE stage instance
12/21/2010 11:35:15 PDApp.ExternalGateway - MessageHandler
initialized...
12/21/2010 11:35:15 PDApp.ExternalGateway - ExternalGateway
initialized...
12/21/2010 11:35:15 PDApp.ExternalGateway - NativeCommandHandler
initialized...
12/21/2010 11:35:15.431 PDApp.StartupCommand Logging Level verbosity
Set to INFO
12/21/2010 11:35:15.432 PDApp.StartupCommand Processing the startup
Command
12/21/2010 11:35:15.439 PDAPP.AppletManager Starting Applet
registeration...
12/21/2010 11:35:15.457 PDAPP.MainDisplayMediator Looking up for the
Exact versioned applet for ID :UWA_UI
12/21/2010 11:35:15.479 PDAPP.AppletManager Loading Applet: UWA_UI
Version = 1.0
12/21/2010 11:35:15.514 PDApp.ZStringLoader PDAPP SWF - locale set
to - en_US
12/21/2010 11:35:15.570 PDAPP.AppletManager Loading progress0 out of
521002
12/21/2010 11:35:15.572 PDAPP.AppletManager Loading progress65536 out
of 521002
12/21/2010 11:35:15.574 PDAPP.AppletManager Loading progress131072
out of 521002
12/21/2010 11:35:15.583 PDAPP.AppletManager Loading progress196608
out of 521002
12/21/2010 11:35:15.585 PDAPP.AppletManager Loading progress262144
out of 521002
12/21/2010 11:35:15.588 PDAPP.AppletManager Loading progress327680
out of 521002
12/21/2010 11:35:15.590 PDAPP.AppletManager Loading progress393216
out of 521002
12/21/2010 11:35:15.592 PDAPP.AppletManager Loading progress458752
out of 521002
12/21/2010 11:35:15.594 PDAPP.AppletManager Loading progress521002
out of 521002
12/21/2010 11:35:16.023 PDApp.ExternalGateway Recieved Applet Loading
Completion
12/21/2010 11:35:16.027 UWA.ZStringLoader Trying to load ZString for
preferred locale - en_US
12/21/2010 11:35:16.087 UWA.ZStringLoader Applet locale set to -
en_US
12/21/2010 11:35:16.319 UWAApplet.Startup Processing the startup
command
12/21/2010 11:35:16.324 UWA.LoadWorkflowCommand Processing the
LoadWorkflowCommand
12/21/2010 11:35:16 PDApp.AppletManager - Loading Applet - UWA_Native
for WindowID - 1
12/21/2010 11:35:16 UWANative - Build Version - 1.0.175.0
12/21/2010 11:35:16 UWANative - Logging Level verbosity Set to 4
12/21/2010 11:35:16 UWANative - Updater in patch mode
12/21/2010 11:35:16 UWANative - Error in mdbOpenSessionNoCreate 1
12/21/2010 11:35:16 UWANative - Failed to initialize Updater Core
12/21/2010 11:35:20 Utilities - Directory not present
12/21/2010 11:35:20 UWANative - Could not delete the temp folder "".
12/21/2010 11:35:16.594 UWA.LoadWorkflowCommand The start applet did
not return the result xml. Startapplet returned
12/21/2010 11:35:16.595 UWA.LoadWorkflowCommand Cannot start
UWANative Applet
12/21/2010 11:35:20 PDApp.AppletManager - Un-loading Applet -
UWA_Native for window ID - 1
12/21/2010 11:35:20 PDApp.ExternalGateway - Callng the finalize
function of the applet
12/21/2010 11:35:20 PDApp.ExternalGateway - Unloading applet
12/21/2010 11:35:20.878 PDApp.HostMessageHandler Recieved force
window close message
12/21/2010 11:35:20.878 PDApp.HostMessageHandler Sending message to
native
12/21/2010 11:35:20 PDApp.WindowManager - Window destruction reached
for ID - 1
12/21/2010 11:35:21 PipeThread - Pipe Connected. Waiting for data to
come on pipe
12/21/2010 11:35:21 PipeThread - 2 bytes read on pipe
12/21/2010 11:35:21 PipeThread - Data recieved on pipe. Sending the
data to the main thread to process and show window
12/21/2010 11:35:21 PipeThread - Message Sent to main thread
12/21/2010 11:35:21 PipeThread - Disconnecting pipe
12/21/2010 11:35:21 PipeThread - Pipe Disconnected
12/21/2010 11:35:21 PipeThread - Terminating the pipe thread
12/21/2010 11:35:21 PDApp - Terminating native MessageQueueManager
12/21/2010 11:35:21 PDApp - Terminating native AppletManager
12/21/2010 11:35:21 PDApp.AppletManager - AppletManager destructed
12/21/2010 11:35:21 PDApp - Terminating WindowManager
12/21/2010 11:35:21 PDApp.WindowManager - Destroying PDApp main
window's
12/21/2010 11:35:21 PDApp.WindowManager - Destroying PDApp main
window's sucessfully
12/21/2010 11:35:21 PDApp - Terminating ExternalGateway
12/21/2010 11:35:21 PDApp.ExternalGateway - ExternalGateway
destructed
12/21/2010 11:35:21 PDApp - Terminating MessageHandler
12/21/2010 11:35:21 PDApp.ExternalGateway - MessageHandler
finalize...
12/21/2010 11:35:21 PDApp.ExternalGateway - MessageHandler destructed
12/21/2010 11:35:21 PDApp - Terminating NativeCommandHandler
12/21/2010 11:35:21 PDApp.ExternalGateway - NativeCommandHandler
destructed
12/21/2010 11:35:21 PDApp - Terminating AsyncMessageProcessor
12/21/2010 11:35:21 PDApp.AsyncMsgProcessor - Destroying
AsyncMsgProcessor
12/21/2010 11:35:21 PDApp - Terminating NativePlatformHandler
12/21/2010 11:35:21 PDApp - Terminating logger
PDA changed file
12/21/2010 03:00:24 AAMUpdatesNotifier - Build Version - 1.0.175.0
12/21/2010 03:00:24 AAMUpdatesNotifier - Logging Level verbosity Set
to 4
12/21/2010 03:00:27 Utilities - File does not exist
12/21/2010 03:00:41 AAMUpdatesNotifier - CFU .... StatusCode(41)
ErrorCode(212)
12/21/2010 03:00:41 AAMUpdatesNotifier - inside getUpdates
12/21/2010 03:00:41 AAMUpdatesNotifier - Cannot find any update Node
12/21/2010 03:00:41 AAMUpdatesNotifier - All updates count 0

About ale error handling in workflow?

Hi,
can any one explian in detail ale error handling through workflow,its urgent for me.
Regards,
phani

Hi Srikanth,
follw the steps it will helpful u,
Pre-requisites.
It is assumed that the reader of this article has some knowledge in SAP workflow BOR objects and ALE Idoc process like process code, Partner Profile etc.
Description
Here, we will be discussing in details the Error handling of an Inbound Idoc through triggering an event, which in turn will be triggering a workflow attached to the workflow.
Steps:-
1.     Create custom BOR object with the events, Start and Stop event
2.     Create a workflow for the error handling, like generating a notification whenever an error occurred in the Inbound Idoc.
3.     Creation of Function Module and attachment with the Process Code
4.     Create the settings for the Inbound Process of the Idoc through the Process Code.
Creation of BOR objects. Go to the[http://www.****************/Tutorials/ALE/ErrorHandling/page3.htm] transaction SWO1.
Enter a name for the Object type and click CREATE button for creating the custom BOR object.
Enter the details required for creating the BOR objects...
Create the Key fields and events of the BOR object.
For creating the Key fields place the cursor on the Key fields and Click on the Create Button
Create events for triggering the workflow and stopping the workflow.
For creating the event place the cursor on the EVENTS and Click the create button like Key fields.
Create two events.
Enter the event name description etc and proceed further to create it.
Similarly create another event for ending the Workflow in the similar manner like that created earlier.
Now, Generate the BOR object through the generate button
Release the EVENTS and subsequently release the BOR object.
After the creation of BOR object
Create a workflow for the generation of notification whenever an error is reached in the Inbound Idoc.
Execute the transaction SWDD.
Click on the CREATE button for creating the workflow for error handling.
Choose the Step type to be inserted for the notification like here we are using Send Mail option for sending a mail to the user whenever any error occurred.
Activate the Workflow and test it whether it is working as per the requirement.
After the successful completion it is required to attach the workflow with the event.
Go to the Header section (Denoted by CAP).
Go to the Start Events TAB.
Enter the details of the event with which the workflow should be linked like the category, BOR object type and the event with which that should be linked.
Enter here the BOR object that has been created and give the name of event created for starting the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Click on the Binding Button for generating the binding between the event and the workflow.
Generate the binding and click OK button to save the binding.
Click on Activate / deactivate button for activating the linkage.
After the successful linkage the following sign will appear on the workflow.....
This shows that the workflow has been linked to the event and it will be triggered whenever that particular event will be triggered.
After the creation and successful linkage of workflow with the event it is required it is required to generate a function module and attached it to the process code.
Go to SE37 transaction and copy a standard process code function module to a custom one. Do no delete any parameters from the function module as the SAP standard program itself is calling this.
In that function module do the required validation and whenever the validation fails set a standard parameter WORKFLOW_RESULT to 9999 from within the function module, otherwise normally proceed to set the status to 53.
After the creation of function module it is required to attach it to the process code and corresponding attached to the message type at the Partner Profile stage.
The process code is being created through the transaction WE42
Go to the change mode and click the New Entries button for creating new process code.
Enter the Process Code Name, description and choose the processing type as Processing by function module. Click on the extension button of Identification.
The details for the of the Process Code after clicking the identification button will be
Whenever idoc arrives into the Destination system then the standard SAP triggers the Process code attached to the Message type in the partner profile. The partner profile is being maintained in the transaction WE20.
Since, it is and inbound scenario so the message type and the corresponding process code will be maintained for the Inbound Parameters.
Click on Create Inbound Parameters button for creating new Inbound Message type and the corresponding message type.
Enter the process code for the corresponding message type.
Click SAVE button for saving the changes.
Whenever the IDOC arrives into the target system, it checks the partner profile and finds the corresponding process code. The process code is being linked with the function module through which the IDOC is required to be processed.
Regards,
Phani.

Outbound Idoc error handling through workflow

Hi,
I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
How this task can be triggered when outbound idoc error occurs in the system?
Kr,
Vithalprasad
Edited by: Vittalprasad on Jun 9, 2010 11:52 AM

Hi,
Have a look
Outbound IDoc Error Handling via Workflow
Outbound idoc error handling through workflow

OUTBOUND- ERROR HANDLING USING WORKFLOW

Hi Gurus,
Can any one tell me about workflow & how to do error handling using WORKFLOW in OUTBOUND IDOC.Below are the points , Please check it & send me reply.
1.Value not found for Custom IDoc fields.
2. Partner Profile not maintained correctly.
3. Syntax error in IDoc.
4. IDoc ready for dispatch (ALE Service).
Regards,
Chiranjeevi.

Hi,
FOr most of your requirements, there is already std. SAP IDOC error Single-step tasks.
Have a look at WE46 transaction.
Also, if you go to SWO1 and search with "IDOC*", you will get all the BO's even.
It's pretty straightfwd. Also, in Partner Profiles, WE20, for each of the IDOC type, there is one "Post.Processing AGent", whom if you set up correctly, will be the person receiving this Errored IDOC mails.
Hope this helps
venu

Error when associating workflow with Task Content Type

Using SharePoint Designer 2010, I have created a simple workflow that sends an email out when a tasks due date has past. I created this as a Global Workflow and then tried to "Associated to Content Type", selecting "Task". I am then taken
to... COMPANY PORTAL--> Site Settings--> Site Content Types--> Task--> Add a Workflow. When I try to associate the new "Global" workflow and select OK I get the following error...
Error
Workflows may not be associated with content types whose base is on 'WorkflowTask'.
I have looked up the error but find no real explination of what it means. And I have associated global workflows with custom content types and never had this issue.
So what's going on?
Thanks
Steve
Thanks in advance for your time. Steven

Hi ,
I understand that when you bind the workflow to Tasks content type, there is an error. I can reproduce this error. This is because we cannot add a reusable workflow to a workflow tasks content type. When you add the reusable workflow to the Tasks content
type, you must have checked the ‘Add this workflow to all content types that inherit from this content type’. In this way, the workflow will be added to all the Tasks content type and workflowtasks content type. There will an error. After you close the error
message, the workflow is added to the Tasks content type.
The workaround is the check No to ‘Add this workflow to all content types that inherit from this content type’.
Thanks,
Entan Ming
Entan Ming
TechNet Community Support

Error loading updater workflow elements 9

Can anyone help, i have elements 9, and have tried to install the camera raw update, however when i try the install i get a message box saying.... error loading updater workflow..... this is now driving me insane..... i have dowladed the latest downlad manager and have also tried some older updates but still end up with the same message. i have the latest updated version of elements but no raw plugin in the plugin list and when i press update it says version is the latest. i have tried to manually download the plugins with no luck. i am running windows vista, please help as the software is no use if i cant open the raw files.

Try again. The read-me instructions are not very clear. After you extract files from the zip folder double click on the patch installer application and allow access if prompted.
The Adobe Application Manager should open automatically and complete the installation.
Click to enlarge image

Error in Invoice workflow

Quantity entered larger than quantity to be debite
Error handling for work item 000011592049
Canceled by user
Canceled by user
Quantity entered larger than quantity to be debite
Hi All,
I am gettin the above error in invoice workflow. Can anyone tell me what could be the reason?
Regards,
Raj

I solved the error using these parameters:
Evaluation ID 3EV_IN_600_000
Process level schema 3C_IN_600_000
Level type S Automatic
Task ID 40007988
Decision type 1 Decision for Entire Document.

Error in OTL Workflow

Similar Messages

Maybe you are looking for