Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Oct 2018 version throws error when connecting the SPO list

I have a report that connects to a number of local Excel files, but also connects to a SharePoint Online list. When I upgraded from Aug 2018 release to Oct 2018 release, I can no longer refresh the report.  I get the following error message:

 

Capture.PNG

 

"IT Outages" is the SPO list.  Right before it errors out, a command-type window with "sqldumper" in the header pops up for about a second.

 

I rolled my PBI version back to Aug 2018, and it was able to refresh just fine.  I then reinstalled Oct 2018 (2.63.3272.40461 64-bit) but it still fails.

 

Thanks

David 

Status: New
Comments
v-qiuyu-msft
Community Support

Hi @dedelman_clng,

 

In this report, do you perform any transformation steps for the IT Outages query after retrieving data? 

 

Please open Power BI desktop October version then connect to the same SharePoint online list to see if any error occurs. 

 

Best Regards,
Qiuyun Yu 

 

dedelman_clng
Community Champion

Hi @v-qiuyu-msft

 

On the query for IT Outages, the only transformation steps in Query Editor are removing and renaming columns.  I make one calculated column and a few dozen measures on that table within the PowerBI report.

 

On a second query to the same source within Query Editor, I do an "Expand List Column" (saved as table "OutageCI")

 

"Refresh Preview" within Query Editor works correctly as well.  But when I run "Refresh" from the main report, the following errors show up in my Windows Application log

 

-----

The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

 

The Open Procedure for service "Lsa" in DLL "C:\Windows\System32\Secur32.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

 

The Open Procedure for service "MSDTC" in DLL "C:\WINDOWS\system32\msdtcuiu.DLL" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

 

Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code.

 

Could not open registry key: SYSTEM\CurrentControlSet\Services\piauth_stats\Performance. User: LNG\dedelman, Process name: PBIDesktop.exe  <-- This one appears 3 times in a row

 

Could not open registry key: SYSTEM\CurrentControlSet\Services\pimsgss\Performance. User: LNG\dedelman, Process name: PBIDesktop.exe  <-- This one appears 3 times in a row

 

Could not open registry key: SYSTEM\CurrentControlSet\Services\pinetmgr\Performance. User: LNG\dedelman, Process name: PBIDesktop.exe

 

Could not open registry key: SYSTEM\CurrentControlSet\Services\pisession_stats\Performance. User: LNG\dedelman, Process name: PBIDesktop.exe

 

Could not open registry key: SYSTEM\CurrentControlSet\Services\pisubsys_stats\Performance. User: LNG\dedelman, Process name: PBIDesktop.exe

 

The Open Procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

 

The description for Event ID 22 from source MSOLAP$AnalysisServicesWorkspace253967116 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

An unexpected exception occurred.

 

-------

 

I have uninstalled and reinstalled the latest October version several times with no change in result.

 

Thanks

David

v-qiuyu-msft
Community Support

Hi @dedelman_clng,

 

Please create a new blank report and paste Power Query for IT Outages from original report in this new report Advanced Editor, then apply change, check if you are able to refresh on report level. If you can refresh it now, please add one measure then click refresh button to test each measure. Also you can do the same test for table OutageCI to find which item might causes the issue. 

 

Best Regards,
Qiuyun Yu 

dedelman_clng
Community Champion

Hi @v-qiuyu-msft - I have done as you have suggested (both IT Outages and OutageCI), even going so far as to copy the PowerQuery for an Excel-based table, and a PowerQuery Date table.  No errors on any of them through multiple refreshes.  I created a calculated column and measure on each of the SPO-based tables. Still no errors.

 

What are the next steps?

Thanks,

David

v-qiuyu-msft
Community Support

Hi @dedelman_clng,

 

Please turn off below option then refresh it again to see if error occurs: 

 

q4.PNG

 

I see there are many tables in your issued report. Please open Query Editor, turn off "Include in reprot refresh" for any one table, then apply change, click on Refresh button to see if other tables. Then repeat the step to turn off for other tables, apply changes and refresh to see if you can find the problem. 

 

q3.PNG

 

Best Regards,
Qiuyun Yu 

dedelman_clng
Community Champion

Hi @v-qiuyu-msft

 

I did as you suggested, turning off individual tables 1 by 1. I did this both with Parallel loading enabled, and without.  No change in behavior.

 

The window that pops up has "C:\Program Files\Microsoft Power BI Desktop\bin\\SQLDumper.exe" as the header (note the 2 \\ between bin and SQLDumper.exe)

 

I can't find anywhere on my hard drive that it might be writing log files.

v-qiuyu-msft
Community Support

Hi @dedelman_clng,

 

It's hard to go further on forum side, I would suggest you create a support ticket to Microsoft and let engineers look into your environment to see what happens. 

 

Support Ticket.gif

 

Best Regards,

Qiuyun Yu