Trident could not execute workflow

Oct 5, 2010 at 3:24 PM

Hello,

I've got the 64 bit version of Trident installed and executed a quite simple workflow consisting of just a "Write to Console" action with a fixed text. Unfortunately, an error dialog showed up reading "Execution of the workflow failed. Reason: Workflow runtime process exited".

Could you please help?

Kind regards,
Dirk

 

wfexecutor.log:

Timestamp: 05.10.2010 17:13:23
Category: FileLogger
Severity: Information
Machine: DIRK
Application Domain: TridentWorkflowHost.exe
Process Name: C:\Program Files\Microsoft Project Trident - A Scientific Workflow Workbench\Executor\TridentWorkflowHost.exe
Extended Properties:
----------------------------------------------------
Timestamp: 05.10.2010 17:13:30
Message: TridentWorkflowHost completed
Category: FileLogger
Severity: Information
Machine: DIRK
Application Domain: TridentWorkflowHost.exe
Process Name: C:\Program Files\Microsoft Project Trident - A Scientific Workflow Workbench\Executor\TridentWorkflowHost.exe
Extended Properties:

0613d948-3697-403f-9a39-52bed5eced8fwfexecutor.log:

Timestamp: 05.10.2010 17:13:28
Message: HandlingInstanceID: 5bc9f8a3-6e52-4a22-9da6-a409f8a0e242
An exception of type 'Microsoft.Research.DataLayer.RecordNotFoundException' occurred and was caught.
----------------------------------------------------------------------------------------------------
10/05/2010 17:13:28
Type : Microsoft.Research.DataLayer.RecordNotFoundException, Microsoft.Research.DataLayer.DataLayerCommon, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
Message : Data not found
Source : Microsoft.Research.DataLayer.DataProviders.Microsoft
Help link :
Data : System.Collections.ListDictionaryInternal
TargetSite : System.Collections.Generic.List`1[Microsoft.Research.DataLayer.IObject] ReadManyInternal(System.Data.SqlClient.SqlCommand, Action, System.Collections.Generic.List`1[Microsoft.Research.DataLayer.Parameter] ByRef, ObjectCreator, System.Collections.Generic.List`1[Microsoft.Research.DataLayer.IObject] ByRef)
Stack Trace :    at Microsoft.Research.DataLayer.SQLConnectionWorker.ReadManyInternal(SqlCommand cmd, Action action, List`1& paramList, ObjectCreator creator, List`1& results)
   at Microsoft.Research.DataLayer.SQLConnectionWorker.ExecuteSearch(Storage objType, SearchQuery query, ObjectCreator creator, List`1& results)
   at Microsoft.Research.DataLayer.SQLConnectionWorker.Object(Storage obj, Action action, List`1& paramList, ObjectCreator creator, List`1& results)
   at Microsoft.Research.DataLayer.UserCredential.Search(ISearch query, Connection conn)
   at Microsoft.Research.DataLayer.ActivitySecurity.GetUser(Connection connection)
   at Microsoft.Research.DataLayer.ActivityAfterCalls.CheckActivity(Storage storage, Action action, List`1 paramListResp, Exception& error)
   at Microsoft.Research.DataLayer.FilterAfterCalls.Object(Exception& error, Storage& storage, Action& action, List`1& paramListReq, List`1& paramListResp)
   at Microsoft.Research.DataLayer.ConnectionSecure.Object(Storage obj, Action action, List`1& paramList)
   at Microsoft.Research.DataLayer.BasicObject.Load[T](Guid id, Connection c, ObjectCreator creator)
   at Microsoft.Research.DataLayer.ActivityInstance.get_Activity()
   at Microsoft.Research.eResearch.Execution.JobMonitor..ctor(Guid jobId, Boolean isLightWeightExecution)
   at Microsoft.Research.eResearch.Execution.JobExecutor.<>c__DisplayClassb.<Execute>b__2()
   at Microsoft.Research.eResearch.Common.ExceptionHandler.Handle(String policyName, Action action, Action finalBlock)

Additional Info:

MachineName : DIRK
TimeStamp : 05.10.2010 15:13:28
FullName : Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
AppDomainName : JobExecutorDomain
ThreadIdentity :
WindowsIdentity : NT-AUTORITÄT\SYSTEM

Category: FileLogger
Severity: Error
Machine: DIRK
Application Domain: JobExecutorDomain
Process Name: C:\Program Files\Microsoft Project Trident - A Scientific Workflow Workbench\Executor\TridentWorkflowHost.exe
Extended Properties:
----------------------------------------------------

Oct 6, 2010 at 5:15 AM

Hi,

We are working on your issue. We will get back to you as soon as possible.

Please let us know if you have any further comments/issues.
Regards,
Support Team

Oct 7, 2010 at 7:39 AM

Hi,

After analyzing the log files, we have noticed the following exceptions: 

Type : Microsoft.Research.DataLayer.RecordNotFoundException
Message : Data not found

The ‘Data not found’ exception is raised in when the application is not able to find the specified data in Trident database. This might have been due to the following reason:

If the Trident Workflow Composer(or WorkflowExecutionService) and TridentWorkflowHost.exe are referring to different databases.  For example trident composer(or WorkflowExecutionService)  might have been referring to TridentDB1 and TridentWorkflowHost.exe might be referring to TridentDB2.

The reason for trident composer(or WorkflowExecutionService)  and the TridentWorkflowHost.exe referring to different DB’s could be the anomalies in the config files.  

Can you please share the following files to tridentp@microsoft.com or v-vichan@microsoft.com?

1.    Configurations files:

 

  • Trident Workflow Composer’s: %appdata%/Research/Trident/ ConnStore-Application.configSources
  • WorkflowExecutionService: C:\ProgramData\Research\Trident\ConnStore-ExecutionService.configSources
  • TridentWorkflowHost.exe: C:\ProgramData\Research\Trident\ConnStore-Application.configSources

2.    Code for the WriteToConsole Activity that you have imported. Also, please mention the OS which you are using.

Please let us know if you have any further comments/issues.
Thanks,
Trident Support Team

Oct 11, 2010 at 2:53 PM

Hello,

I just sent you the files per e-mail. The activity is that supplied with the Trident distribution (https://tridentworkflow.svn.codeplex.com/svn/Trident/Product/Activities/TridentDataActivities/WriteToConsole.cs).

Kind regards,
     Dirk

Oct 27, 2010 at 8:42 AM

Hi Dirk,
 
We were not able to reproduce this issue on our Test machines using the “WriteToConsole” Activity. We were able to execute the workflow successfully. The configuration files that you have shared with us look fine.

Can you please share the workflow package which you are trying to execute to tridentp@microsoft.com or v-raaror@microsoft.com?
 
In meantime can you try re-installing Trident and then try to execute the workflow?

Please let us know if you have any other questions/issues.
Regards,
Trident Support Team

Oct 28, 2010 at 3:04 PM

Hi,

Can you please let us know if our response helped in answering your questions?

Thanks,
Trident Support Team

Jan 25, 2011 at 1:27 PM

Hi,

We have not heard back from you for a long time and we hope this means your question has been answered. We are marking the thread as closed.

Please let us know in case you have any further questions/concerns.

Regards,
Trident Support Team

Jan 25, 2011 at 1:28 PM

Hi,

We have not heard back from you for a long time and we hope this means your question has been answered. We are marking the thread as closed.

Please let us know in case you have any further questions/concerns.

Regards,
Trident Support Team