3
Vote

Workflow cannot be run after switching database

description

Hi, there
 
I have reported this issues, I am not sure if you have worked out the solution in this new release.
 
We have a muliple Trident database which contain different projects so that we can eaily move to another project by switching the database connection.
 
Trident has the functionailty to easily changing connections, however the workflow cannot be executed after switching database. The workflow status stays "Waiting".
 
The possible reasons are:
 
  1. When we change the connection, the new connection will be written into the connection configuration file that sits in C:\Documents and Settings[MY ACCOUNT]\Application Data\Research\Trident\ConnStore-Application.configSources.
  2. However, the WorkflowHost, or WorkflowExecutor work under the system account , in my case, it is under "NETWORK SERVICE" account. So WorkflowExecutor actually read the connection from the file in C:\Documents and Settings[NETWORK SERVICE]\Application Data\Research\Trident\ConnStore-Application.configSources.
     
    We think the connection file in "Network Service" folder that is used by WorkflowExecutor is not changed when we changed connection from Trident Composer. Thus, we try to run a workflow in the new connection, TridentExecutor still use the old connection, that is why the status of execution is "Waiting"
     
    Then we tried we manually modified the connection under "Network Service" folder after we changed the connection from composer, and then restarted the TridentWorflowExection Service. It worked.
     
    If my solution is correct. Can you please modified the ConnectionManager code to make it modify both configuration files and restart ExectionsService after that?
     
    Cheers

comments

fra30c wrote Nov 17, 2010 at 1:53 AM

I have the same problem. The functionality of "Connection" and selecting any saved connection other than the last installed fails to allow the execution of any workflow.

rahularora25 wrote Nov 17, 2010 at 1:09 PM

Hi,

Correct, as a workaround we have to manually modify the following configuration files of the Executors :
  1. TridentTrayApp.exe – “%appdata%\Research\Trident\ConnStore-Application.configSources”
  2. TridentWorkflowHost.exe – “C:\ProgramData\Research\Trident\ConnStore-Application.configSources”
  3. Trident Provenance – “C:\ProgramData\Research\Trident\ConnStore-ExecutionService.configSources”
This is there as per Trident design. It is a new feature which can be implemented in Trident. We will keep you posted on the updates.

Regards,
Trident Support Team

rahularora25 wrote Jan 25, 2011 at 1:30 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

fra30c wrote Feb 17, 2011 at 5:20 AM

Hi,

When you say that "This is there as per Trident design. It is a new feature which can be implemented in Trident", do you mean that the functionality to change database connections is complete or is this something that will be fixed in a future version?

abhisheks wrote Feb 17, 2011 at 1:15 PM

Hi,

This issue will be fixed in future version. As per now, we suggest you to manually modify the configuration files as the next release of Trident is not scheduled in near future.
Please let us know if you have any further query/concern.

Regards,
Support Team

Sign in to add a comment or to set email notifications