You are viewing limited content. For full access, please sign in.

Question

Question

Workflow not executing queries

asked on September 11, 2018

Hi There,

 

I have a workflow that is not executing Queries to any databases. When I test the connection, I can find what I am looking for, however, there are quite a few of these workflows running.

 

The Workflow seems to be waiting to execute the query and is not doing anything else. I cannot retry the step and I am out of Ideas.

 

Any advise would be greatly appreciated.

0 0

Replies

replied on September 11, 2018

I have run into this once trying to use odbc to both Excel and Access.  It worked in testing, but when the workflow ran, it just stopped (without any errors) at the Query task (waiting) and would not proceed.  I ended up uninstalling the AccessDatabaseEngine ODBC drivers and installing the newest version of that driver pack.  Then the queries executed without problems.

0 0
replied on September 11, 2018

Assuming it is an existing known working workflow, have you tried restarting the workflow server service? I have noticed this happen on some older versions of Laserfiche where external queries don't time out properly and end up stopping all queries.

0 0
replied on September 11, 2018

Hi John,

 

Yes, I attempted a service and server restart. both with no luck.

0 0
replied on September 11, 2018

I've had similar problems when using different two different data sources on the same Workflow server.

One connection was a 32 bit ODBC to the IBM iAccess utility that pulled data from an AS/400, and when I set up the other to use the built in 64 bit SQL server connection it failed. The connections to SQL server had to be done as 32 bit ODBC to work side-by-side with the ODBC connection to the iSeries access client.

Things would seem to execute fine in Designer, but fail in production. Never did find out the specifics as to why.

0 0
replied on September 11, 2018

Glen

The driver architecture must match that of your Workflow.  So if your Workflow installation is x86, any driver called by Workflow must be x86 and if your Workflow installation is x64 any driver that is called by Workflow must be x64.

In windows, you cannot call a architecture specific driver from another architecture so this is a Windows limit and not a Workflow limit or error.

2 0
replied on September 12, 2018

Thanks Bert. It's good to know what the cause was.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.