Scheduled session fails, workflow succeeds

[Aalph]

Hi,

I have scheduled the workflow, but the sessions are failing.
All my objects are also checked-in, as suggested by some to check. Can anyone tell me whats happening by giving a look at my workflow error log. I have 2 session task for this workflow (tester1, tester2).


LM_36435 Starting execution of workflow [wf_Test] in folder [XYZ] last saved by user.
LM_44206 Workflow wf_Test started with run id [820], run instance name [], run type [Concurrent Run Disabled].
LM_44195 Workflow [wf_Test] service level [SLPriority:5,SLDispatchWaitTime:1800].
LM_44253 Workflow started. Clients will be notified
LM_36330 Start task instance [Start]: Execution started.
LM_36318 Start task instance [Start]: Execution succeeded.
LM_36388 Session task instance [s_m_tester1] is waiting to be started.
LM_36388 Session task instance [s_m_tester1] is waiting to be started.
LM_36682 Session task instance [s_m_teter1]: started a process with pid [576] on node [dev].
LM_36330 Session task instance [s_m_tester1]: Execution started.
LM_36682 Session task instance [s_m_tester2]: started a process with pid [4816] on node [dev].
LM_36330 Session task instance [s_m_ESL_tester2]: Execution started.
LM_44127 Failed to prepare the task [Session task instance [s_m_tester1]].
LM_36320 Session task instance [s_m_tester1]: Execution failed.
LM_44127 Failed to prepare the task [Session task instance [s_m_tester2]].
LM_36320 Session task instance [s_m_tester2]: Execution failed.
LM_36318 Workflow [wf_Test]: Execution succeeded.

Thanks.

 

[ArtieChoke]

Look at the session log. If there isn't one, then it means either the session or map is invalid.

"I think we're all Bozos on this bus!" - Firesign Theatre

 

[Aalph]

Hi Artichoke,
The workflow/session is running correctly, when its run manually. No errors.
But, session is failing when I schedule it. And there are no session logs generated. Its on v8.6.0.
Is it still a session or mapping invalid issue ?

 

[ArtieChoke]

Not if it runs manually. Are you using versioning? And is the the first version? If so, did you check it in?



"I think we're all Bozos on this bus!" - Firesign Theatre

 

[Aalph]

Yes its using versioning and all my objects are checked in.

 

[ArtieChoke]

Have you ever run anything successfully in the scheduler?


"I think we're all Bozos on this bus!" - Firesign Theatre

 

[Aalph]

This is the first time I am scheduling anything in the scheduler.

 

[ArtieChoke]

What operating system - windows or unix?

If windows, what account is the service running under?

"I think we're all Bozos on this bus!" - Firesign Theatre

 

[Aalph]

Finally, its working. We have versioning enabled in v8, where I am a first time user. The issue was due to some of my source tables not being checked-in.
The infa scheduler requires all its components to be 'CHECKED-IN', otherwise it fails the session.
This is how I found out my items which were still Checked-Out :

Went to Versioning tab -> Find Checkouts ->
Selected the folder and the user.
( This shows all items that are still not Checked-In )
Checked-In all the source tables and scheduled the workflow. It ran smoothly.

Apologies for the oversight,
Thankyou Artichoke.

 

[ArtieChoke]

That was gonna be my next suggestion. Glad it works now.

BTW, their scheduler is really lame. If you use SQL Server, it's much better to use that job scheduler and use the pmruncmd program to kick off the wf.

"I think we're all Bozos on this bus!" - Firesign Theatre