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:
- 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.
- 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?