Forum Discussion
External component as thrown an exception
The technician led and encouraged me to use the OBCD driver. As you go thru the steps, you will be prompted for excel or access. For my simple test, that solution seemed to work.
Part of my challenge, I'm connecting thru a folder, with multiple access files. This OBDC solution is good for a single file/query. I've got 10-15 files, and not excited about a short term surgery, not knowing if a fix is quick to come or months...
The technician was to get back to me once they got past the investigation stage.
Thanks for the hint. Did the tech recommend ODBC over OLE DB for any reason?
Am I to understand you are tapping 10-15 databases in a folder? If so, would it help you to build a new database file and link to the pertinent tables in each of the 10-15 files just so you can consolidate them into a single source as far as PBI is concerned?
I have a screen share session with an MS support rep, Power BI expert, and Sharepoint expert tomorrow morning. I get this error when connecting to a Sharepoint folder and pulling tables out of Excel files in those folders and appending those tables together in Power BI.
The process has been working for a year and a half and since Feb. 10 or so, I haven't had one successful refresh in Power BI Desktop. I've got the issue escalated so that they have 3 people connecting with me on one call tomorrow. Hope to find a solution...
Will keep you guys posted.
Any luck with the Experts?
Hi Rich - no, the latest communication with support was late last week. Feb 27/28th - or so. The case is still under investation - with no known solution date.
I did attempt to go down the ODBC route on desktop PBI - and does seem to be working better. However, with occassional hiccups. I then ventured to attempt the import process using ODBC connector within the Service dataflow, and in my simple testing case-no refresh failures.
Thanks for your suggestion on linking files. However, I am a "greenie" in this stuff -and my research didn't get me very far. But, yes, linking files would be a solution. As data is updated, what is the process to 'reload" the date into a linked mdb file. Is it manual?
What I have are annual mdb files - with potentially 20+ years of data. But, for now, I am limiting my import to 4 years (files). But, the challenge - I need two tables within the mdb file, thus doubling the import queries. With the older "folder" connector - the process was straight forward. I have 3 differing sets of annual mdb files to deal with. (3 sets*x2tables x 4yrs) = 24 potential queries.
Will keep everyone posted. I was hoping the tech would get back to me after this weekend's email informing her of my ODBC efforts.