Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Microsoft Access .accdb Input error

AJ-CH
8 - Asteroid

Hello, 

I am using Alteryx version 10.6/11.0 and recently after MS office upgrade to never version (office 365) i am having connectivity issues. I am unable to connect access tables as input to Alteryx. Getting following error: "Get Table List Error: InboundNamedPipe::ReadFile:  Not enough bytes read. Overlapped I/O operation is in progress.".

 

Any help will greatly appreciate.

 

Thanks.

 

 

7 REPLIES 7
JordanB
Alteryx
Alteryx

HI @AJ-CH

 

In the past clients have resolved this error by downloading some additional drivers from Microsoft: http://www.microsoft.com/en-us/download/details.aspx?id=13255

 

Hopefully this will resolve that issue.

 

Best,

 

Jordan Barker

Solutions Consultant

AJ-CH
8 - Asteroid
 
AJ-CH
8 - Asteroid

Thanks Jordan for your response. But, I already have this module installed. I reinstalled it but still not working. Any other suggestions?

SeanAdams
17 - Castor
17 - Castor
Let's debug this together:
- what version of the OLEDB driver are you using - and are you connecting via OLEDB? You can check this when you connect to MS Access
- Do you get the same error if you go through ODBC instead of OLEDB?
- this happen on your machine for every access database or just one?
If just one - Does your access DB have any corruption issues?

Hopefully these questions will give us directions to where to look for a solution
JordanB
Alteryx
Alteryx

Hi @AJ-CH

 

I too had the same error message when I moved over to Office 365. I went install the AccessDatabaseEngine._64.exe not realizing my office products were 32bit.

 

Can you check your office products bit version, if it says 32bit then choose to download AccessDatabaseEngine.exe instead. This removed the same error you were receiving and I can now pull tables from access. 

 

Best,

 

Jordan Barker

Solutions Consultant

AJ-CH
8 - Asteroid

Hi

 

AJ-CH
8 - Asteroid

 

Labels