1

Resolved

TridentWorkflowHost.exe crashes

description

I've installed Trident on a Windows Server 2008 R2 system. (64bit) I'm using SQL Server 2008 Standard.
 
After installation, I can run the cove sample but the Ocean Current produces an error message in the Workflow Composer. The data seems to come through ok, but when I close the chart it crashes the Workflowhost.exe. Here is the event log info:
 
Error Details:-
 
 Faulting application name: TridentWorkflowHost.exe, version: 1.0.0.0, time stamp: 0x4c518ec8
 Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0
 Exception code: 0xc000041d
 Fault offset: 0x000000000000aa7d
 Faulting process id: 0xcc4
 Faulting application start time: 0x01cb4ee70a38309e
 Faulting application path: C:\Program Files\Microsoft Project Trident - A Scientific Workflow Workbench\Executor\TridentWorkflowHost.exe
 Faulting module path: C:\Windows\system32\KERNELBASE.dll
 Report Id: 58201b1e-bada-11df-9f3e-005056a60ecc
 
Log Files attached

file attachments

comments

tcvinay wrote Sep 15, 2010 at 8:45 AM

Hi,

Based on the analysis of the log files, we could come to conclusion that the issues might be because of the following reasons:
  1. WorkflowData.dll must be built under x86 architecture.
    Analysis:- This option can be ruled out, as we are building all the dll’s under “Any CPU” mode.
  2. This exception can occur when a .NET application running on a 64-bit platform attempts to load a DLL that does not support native 64-bit execution. If the application is built in platform-agnostic (i.e. "Any CPU") mode, it will launch in 64-bit mode on the host operating system, leading to this problem.
    Solution:- You need to build worflowdata.dll in 32-bit mode by compiling for x86 architecture explicitly, forcing the program to launch in WoW64 mode on the 64-bit system, and allowing the 32-bit DLL to be accessed.
We’ve created a Bug(TridentWorkflowHost.exe crashes) in CodePlex for tracking the issue to closure.

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

rahularora25 wrote Nov 4, 2010 at 4:23 PM

Issue: <<TridentWorkflowHost.exe crashes on 64-bit Windows>>

The issue was in the custom activity code which was aborting the thread which was hosting the Pop up dialog.

For example, in the custom activity, we were aborting the Thread in the PopupUI_Closed event handler by using the Thread.Abort method:
 void PopupUI_Closed(object sender, EventArgs e)
 {
       Thread.CurrentThread.Abort();
 }
Solution:

To solve this issue we need to replace the Thread.Abort code with the following code:
(sender as Window).Dispatcher.InvokeShutdown();

PopupUI_Closed event handler looks like below after replacing the Thread.Abort code.
    void PopupUI_Closed(object sender, EventArgs e)
    {
         (sender as Window).Dispatcher.InvokeShutdown();
    }

wrote Nov 4, 2010 at 4:25 PM

wrote Feb 14, 2013 at 8:04 PM

wrote May 16, 2013 at 9:26 AM

wrote May 16, 2013 at 9:26 AM

wrote Jun 14, 2013 at 7:55 AM