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

Question

Question

Workflow Data Query Issue with Excel

asked on September 3

Hello, I have a ODBC connection to an Excel spreadsheet and for most of today, the connection was fine and I had several successful queries.  However for some reason, now the ODBC connection is erroring out.  

 

It's giving me these two errors:

Error 1: [ODBC Excel Driver] Too many client tasks

Error 2: [ODBC Driver Manager] Driver's SQLSetConnectAttr failed

 

I've tried all sorts of things to reestablish the connection but so far it hasn't helped.  Googling the error online hasn't been helpful either.  I don't know if there's a windows service for ODBC drivers I can stop/start but I don't see anything that stands out. 

 

Also not sure how it happened...are you only allowed X amount of calls to a spreadsheet using ODBC or something?

0 0

Replies

replied on September 4 Show version history

Hi Grant,

I found these links mentioning the errors for the Excel ODBC driver:

How frequently are these query activities running? I found other mentions that the driver might cap out at 64 connections by default. Perhaps try adding a short delay before running the Query Data activity as the 2nd thread suggests and see if that helps.

You mentioned:

 for most of today, the connection was fine and I had several successful queries

Is this something new you've just started developing today and ran into the errors with, or has it been working in Prod for a while and the errors are new?

0 0
replied on September 4

Hey Sam thanks for reaching out!

So I've had a few workflows in the past that were pretty much throwaways....on the WF server I created an ODBC connection to spreadsheets then created a workflow to interact with that spreadsheet and for each row, confirm/convert data, run decisions, and finally write the values to a SQL table.

This specific project was to create a permanent ODBC connection to a spreadsheet where users could paste rows into that they wanted imported to SQL and then they would just submit a form that would trigger the WF and import the rows.

I was playing around with deleting or updating the rows in Excel just to indicate which rows were successfully imported and I was having some minor success when all of a sudden those errors started occurring.

Now it's like ODBC capped out on Excel calls....I tried connecting that same ODBC to a different spreadsheet and got the same error so I don't think it's the spreadsheet, I think it's the ODBC connection.
I doubt that I hit 64 queries with this one WF/spreadsheet but if it's counting total excel/odbc queries then yea it's possible that I've hit some sort of built in limit maybe?

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

Sign in to reply to this post.