Hello - Since Wed Feb 5th, I have really been challenged with multitude of refresh errors. Primarily related to External component has thrown an exception or unknown error. As I go look at queries, seems to be related to a folder connection linking to mdb/MDB files. I have created a very small test query - to these mdb files, and seems as I go step thru the query the first time or two, things are ok. However if I attemt to do any transformation (select columns, filter, format to text - I get the error message below.
One my bigger data model, this was working just as recently as 2 days ago - and now after trying on multiple computers, and older backup files - this error continues to haunt me.. 1) This was working within the last 2 days. 2) Prior backups seem to work at first, then fail. 3) Tried on multiple computers. 4) I have isolated the two mdb queries to their own testing file,
I'm stumped, and need a solution!
Thanks for your thoughts!.
I have filtered out any rows with errors (there are none)
I have been in communication w/Microsoft support - and they encouraged me to change from a folder connection to the pure Access (single file) connection. After doing so - my test files seem to be working better, but still occcassional hiccups After making the suggested changes to my larger data model - 100% failures on attempted refreshes.
All I can offer right now - is to encourage everyone to submit their own case. Maybe get enough people with same errors - might create a sense of urgency. https://powerbi.microsoft.com/en-us/support/free/ See lower right corner for submitting a case. I will add, the technician I am working with does seem very diligent in her efforts - I think it's moving the problem up the ladder is the bottleneck.
I am using the Dec release of PowerBI. There was no January release, not sure of Feb. My problems started around Feb 4/5th - but was working before this date.
I'm also in contact with Microsoft support. The technician was unable to pinpoint the problem when I had a Teams meeting with him on Friday. He is supposed to bring along a Sharepoint expert and schedule another call this week to try to get to the bottom of this.
I'm also running the Power BI release from December 2019. There hasn't been an update in January or February yet.
I will update once I have my follow up with the MS tech and Sharepoint expert.
Hello - I received an email from MS support - and this case (along with 2 other similar cases) have been escalated to the product development team. Will be a month or so - upon hte next release. We shalll see...
I hope this isn't a double-post. My last reply errored-out, and I don't see it in this thread. So I'm trying again.
I have begun seeing this problem just this week. I am using a remote Win 10 VMWare machine via RDP at a client's site. The PBI Desktop file has worked fine for a few months. It connects to a single query in a very small Access.accdb file (492K).
This morning I updated to the Feb 2020 release and had the same problem.
I have been trying to convince the client that PBI would be better than the Excel solution I started them off with. They are interested and want me to build it out with some more features before showng the President. This problem puts all of us developers in a bad position. I have another client that is chomping at the bit to use this stuff internally AND for THEIR clients! Right now, I would have to tell them to stand by.
I hope MS will escalate this and get a solution fast.
Hi Rich! I'm with you on the urgency and need to keep everyone happy. Delays like this, only dampens enthusiasm for those we promise...
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...
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.