Forum Discussion
September 2017 update bug. Unexpected error: Object reference not set to an instance of an object
Hi all.
After September 2017 update (2.50.4859.502) we've faced similar issue some users had reported in February: when we try to get data from Analisys Services, where our MS Dynamics OLAP Cube is located, we end up with the following error: 'Unexpected error: Object reference not set to an instance of an object'. Rolling back to previous PBI version does resolve the issue.
Hope, this bug will be fixed as soon as possible.
And it has eventually been fixed. Hurray!
18 Replies
Hi all.
After September 2017 update (2.50.4859.502) we've faced similar issue some users had reported in February: when we try to get data from Analisys Services, where our MS Dynamics OLAP Cube is located, we end up with the following error: 'Unexpected error: Object reference not set to an instance of an object'. Rolling back to previous PBI version does resolve the issue.
Hope, this bug will be fixed as soon as possible.
Nope, it didn't happen in November as well...
Here are the trace logs.
Hi Fuzzy_Barsik,
I'd like to suggest you create a support ticket to contact to power bi team for further support.
Regards,
Xiaoxin Sheng
HI Fuzzy_Barsik,
Can you please share more detailed information about your issue, it seems related to power bi desktop.
For example:
Trace log, operation steps, screenshots.
Since I can't repro this issue, I'd like to suggest you submit a support ticket for further support.
Regards,
Xiaoxin Sheng
Hi.
No special steps, everything we used to do on a daily basis: Get data -> Analisys Services:
Server address, Import -> OK:
Error:
On an attempt to refresh data in existing template:
I did try to file a bug report here (was unable to find my previous post in the Issues Forum, had to post againg and correct the link).
Since I'm new to the Community, please advise where to file a bug report, if I did it wrong.
It's a pity the bug wasn't fixed in October update... :smileysad:
Waiting for November update. Don't hold my breath though...
I am facing exact same issue.
PowerBI desktop client connected to SSAS (MS SQL 2016, connecting through msmdpump.dll)
Just tried Nov update (2.52.4921.581) and got the same error report.
Let me know if you figure this out. Thanks!
It hasn't been fixed in December as well... :smileymad:
Still there in January... :smileymad:
Hasn't been fixed with the 2.54.4970.961 update as well.
Another one month has passed...
Dear community,
I try to open an csv File with an R Scripting command. It is a very simple command and works fine with all my other colleagues.
I go Get Data-> Other -> R Scripting and enter the following command:
df_groceries <- read.csv("C:/Users/nhecht/Groceries_dataset.csv")
Then the following error message comes up:
I changed my Power BI Version (initially January 2018) back to September 2017. But the error keeps coming.
The error comes also up when I try to open a .txt file with R Scripting.
I have set up under Options the preffered R home directory to R 3.4.3.
I have checked the path where the csv is stored. It is correct.
Does anybody have an idea what the problems is?
Many thanks
And it has eventually been fixed. Hurray!
Hi, I am facing the same issue in the version 2.55.5010.641 64-bit (February 2018). I am using 64-bit R and RStudio version 3.5.0 x86_64. I tried to read a csv using df <- read.csv function, which works on RStudio, but when I do the following on Power BI: Get Data > R script > df<- read.csv("C:\\Users\\user\\Desktop\\test.csv")
The error msg appears: "Unexpected error: Object reference not set to an instance of an object"
This issue seems a repeat of what happened here, what can I do to fix this?
Hi phoenix
Our particular issue has been fixed in March.
Try to update Power BI. If it doesn't help, file a bug report in the Issues board.
