Complete button not invoking process

[JT01]

I have a process I created in workbench that used to work.  Now when I click on the complete button in workspace it looks like it works... the form goes away and takes you back to the process card screen.  However the process doesn't actually run.  With recording on in workbench its like nothing happens, you can invoke the process from workbench and it works just fine though.

This is happening on every process I have in workspace.  Any ideas on a fix?  I have restarted the jboss service already.

[Jasmin_Charbonn]

Do you have a Start Point on your process? Do you see the green arrow on your first step?

Jasmin

[JT01]

Yes, I have a start point on the process.

~Josh

[Jasmin_Charbonn]

Are you using an XDP or a PDF?

If you use a PDF, you might have to set the target url of the submit button , to where it's going to submit to. You want to set the url of the submit button to go to http://server_name:port/workspace-server/submit.

If you use an XDP, it should add automatically it in the action profile.

Jasmin

[JT01]

My input is an XDP.

[NW987]

What does the adminui tell you the process status is?  What is in the server log?

[JT01]

The process has no status.  If you start the process in workspace it doesn't work.  Invoking from workbench works just fine.

Log file says this when being invoked with workspace.

2010-04-05 10:53:18,488 WARN  [com.adobe.idp.taskmanager.dsc.util.TaskManagerDSCUtil] TaskManagerDSCUtil:getTemplate():Error:Service: Mobile Device Agreement Log  not found.
2010-04-05 10:53:18,488 WARN  [com.adobe.idp.taskmanager.dsc.util.TaskManagerDSCUtil] TaskManagerDSCUtil:getTemplate():Error:Service: Mobile Device Agreement Log  not found.

~Josh

[Jasmin_Charbonn]

I would recreate the Task Manager endpoint.

Somehow it's not able to find it, even though you see the card.

Jasmin

[JT01]

That was the first idea I had as well, didn't work.  For the heck of it I just recreated the Endpoint again with no success.  Same error in the log file.

2010-04-05 11:49:47,319 WARN  [com.adobe.idp.taskmanager.dsc.util.TaskManagerDSCUtil] TaskManagerDSCUtil:getTemplate():Error:Service: Mobile Device Agreement Log  not found.

I just want to mention again that this is not happening with only one process.  This is on my test environment and all seven of the processes I am currently developing that were functioning last week do the same thing now... nothing.

I have a more complex process that I thought I would try something different with.  I invoked the process in workbench and it puts the form into a reviewers inbox(mine), from there I submit the process farther and card disappears from my to do list and goes no where.  Inside of the adminui under the process search if I lookup the process id for this task it shows it is still on the step where the card disappeared.

[Former Community Member]

What version are you running?  This sounds like events aren't firing to take steps to their next location.  A form submission is processed in at least a couple of phases - first is the synchronous processing to do some validations, saving the submitted data and completing the current task (step), at which point is can return successful status to the caller; then secondly, it queues up the work required to move the process state along to the next step(s).  If the queued work isn't being processes, you could see what you are seeing.

Note that a StartPoint task does not have a Process Instance associated with it until after the asynchronous work is complete.

But to know what to look for to prove or disprove this, we need to know what LiveCycle version, service pack and possibly hot fix level you are running.

Jon

[JT01]

License Type: Full

Version: 8.2.1, GM

Patch Version: 3.19

Service Pack Version: 8.2.3260.1.221382.1

~Josh

[Former Community Member · Accepted solution]

I'm reasonably sure your events are not being processed.  But I would have expected lots of Scheduler/Quartz/JobManager errors in the log.  Check that your Scheduler service is running (use Components view in Workbench).  If it is, then you can confirm whether events are firing by creating a long lived process that uses the Wait service and waits for a couple of mins before continuing.  Use record and playback to see if it ever gets past the Wait service step.

If it isn't as simple as re-starting the Scheduler, you will need to get support involved and provide them your logs and whatever else they ask for.

Jon

[JT01]

Scheduler service was running and a simple 2 step long lived process with a 2 minute wait service ran both steps.  Thanks for the idea though Jon!

~Josh

[JT01]

Stopping the scheduler service and event management components in workbench and then restarting them fixed my workspace problem.

[Former Community Member]

Good to hear.  Nice job!

Jon