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

Question

Question

ODBC Error - Already open?

Updated October 7, 2015
asked on October 6, 2015

I get this error when I have multiple files doing a query to an ODBC source. I have verified nobody else has the file open other than Workflow.

 

10/6/2015 2:40:47 PM    Query Data    ERROR   The Microsoft Access database engine cannot open or write to the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view and write its data.

0 0

Replies

replied on October 6, 2015

Workflow is multi-threaded, so there could be multiple connection attempts simultaneously. What type of data source is it?

0 0
View 3 previous replies
replied on October 6, 2015

CSV file

0 0
replied on October 6, 2015

Is the file local to the Workflow Server or on a network drive?

0 0
replied on October 6, 2015

Network drive, but even when I moved it to a local drive it gave me the same error.

0 0
replied on October 6, 2015

Network drives are not accessible to services. When it's on the local drive, does it give the exact same error? It sounds like it can't resolve the path if it says "unknown". This is a system ODBC data source, not a user one, right?

0 0
replied on October 7, 2015

Yes, it is the same error when local and yes it is setup as a System DSN.

Note, it will run but given more than maybe 3 or 4 files, I will get this error. I have put a try-catch in place but with 30-100 files kicking off this workflow at the same time, it will error out even with the try catch. I even scripted a 15 second delay in the Catch branch and will get the error. I don't understand why it's holding onto the file for so long per file.

 

My only other thought is to put a "For Each Entry" and scheduling the workflow to run instead of by condition. Thoughts?

0 0
replied on October 7, 2015 • Show version history

Another alternative is to load the data into a SQL database. I do not believe you should have any issues doing that. The issue you are possibly experiencing is collisions with connections. I usually see this with using an excel file though I have not used an access database as of yet. You could have your workflow run at a schedule and have it run to process the documents with a "For Each Entry" activity so you would only have one query connection at a time.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...