In November 2017, we created and published a data model combining Odata feeds and excel files stored on a shared drive. The different sources are merged in the query editor.
After publishing the model, we were able to select the on premise data gateway to schedule refreshes of the model.
After the latest update of the Power BI gateway (End of January 2018) the scheduled refresh stopped working and we were not able to select the gateway anymore.
When we upload a model with all the sources but without merging them, the gateway works fine.
Anyone encountering the same issue or having any feedback?
Hello, Im unable to refresh one of my reports, the gateway is ok, and in power BI destkop refreshes properly. can you help me out, I get this message:
Last refresh failed: Thu Jan 11 2018 16:29:15 GMT+0100 (Romance Standard Time)
Cancellation occurred when sending or receiving a request
after the last Power BI Update we are facing some issues with our Direct Query reports based on SAP HANA.
It seems that after the last Update the query execution plan create SQL query with wrong syntax every time we interact with a slicer on a report.
We analyzed the On-Premise Data Gateway logs and we found that SQL query like these raise errors:
SELECT "t4"."Esercizio Sales" AS "c96","t4"."Data Sales" AS "c97","t4"."Mese Sales" AS "c98"
(select "DueYear" as "Esercizio Sales",
"C1" as "Data Sales",
"DueMonth" as "Mese Sales",
"DueWeek" as "Settimana Sales"
cast("DueDate" as DATE) as "C1"
group by "DueYear",
) as "ITBL"
where "C1" >= date'20120101' and "C1" <= date'20181231')
"t4"."Esercizio Sales" = '2017'
GROUP BY "t4"."Esercizio Sales","t4"."Data Sales","t4"."Mese Sales"
AS "basetable0"INNER JOIN
(SELECT '2017' AS "c96",'10' AS "c98" ) UNION ALL
(SELECT '2017' AS "c96",'11' AS "c98" ) UNION ALL
(SELECT '2017' AS "c96",'12' AS "c98" ) UNION ALL
(SELECT '2017' AS "c96",'01' AS "c98" ) UNION ALL
(SELECT '2017' AS "c96",'02' AS "c98" ) UNION ALL
(SELECT '2017' AS "c96",'03' AS "c98" ) UNION ALL
(SELECT '2017' AS "c96",'04' AS "c98" ) UNION ALL
(SELECT '2017' AS "c96",'05' AS "c98" ) UNION ALL
(SELECT '2017' AS "c96",'06' AS "c98" ) UNION ALL
(SELECT '2017' AS "c96",'07' AS "c98" ) UNION ALL
(SELECT '2017' AS "c96",'08' AS "c98" ) UNION ALL
(SELECT '2017' AS "c96",'09' AS "c98" )
AS "semijoin1" ON
("semijoin1"."c96" = "basetable0"."c96" OR "semijoin1"."c96" IS NULL AND "basetable0"."c96" IS NULL)
("semijoin1"."c98" = "basetable0"."c98" OR "semijoin1"."c98" IS NULL AND "basetable0"."c98" IS NULL)
GROUP BY "basetable0"."c97","basetable0"."c98"
the error occurs at the highlighted statement and seems related to the SELECT statement without FROM clause created by THE Power BI engine which SAP HANA cannot manage.
We are facing the same issue in Power BI Desktop
How is it possible?
I ran up a few on-premises gateways to test the new clustering functionality. While testing I reconfigured these gateways a few times which resulted in the creation of 2 gateway clusters being listed in the PowerBI Service. Once I was happy with the options I explored, I joined the servers to a single gateway cluster. When I attempted to click on the ellipsis and select "Remove" to delete the unwanted gateway cluster that now had no gateways configured.
I received the following error:
We could not remove this gateway because it is the primary gateway within a cluster that has other
gateway instances. Please remove other gateway instances from this cluster before removing the
Please try again later or contact support. If you contact support, please provide these details.
Activity ID: cdd6df13-c757-1c0a-a0e6-2e3bf002d8de Request ID: fcb39f98-2bbb-8de6-a6a6-32f8637cff6a Correlation ID: 45443bdb-551f-51ed-c621-71ca973a24fe Status code: 400 ecsCorrelationId: cdd6df13-c757-1c0a-a0e6-2e3bf002d8de Time: Thu Jan 04 2018 13:00:33 GMT+1100 (AUS Eastern Daylight Time) Version: 13.0.3495.303 Cluster URI: https://wabi-australia-southeast-redirect.analysis.windows.net
Followed by :
Not all gateway instance within this cluster are connected. Please find more details below about
specific errors for each gateway instance.Hide details Activity ID: cdd6df13-c757-1c0a-a0e6-2e3bf002d8de Request ID: 0f7bc62c-d442-8368-a95f-23d736052f3b Cluster URI: https://wabi-australia-southeast-redirect.analysis.windows.net Status code: Time: Thu Jan 04 2018 12:31:20 GMT+1100 (AUS Eastern Daylight Time) Version: 13.0.3495.303 Test Gateway Node 2:
Gateway on endpoint '<ii>sb://wabi-australia-southeast-relay34.servicebus.windows.net/
3a25589f-aeef-49ab-b481-0b237f407d96/</ii>' is unreachable. Test Environment:
Gateway on endpoint '<ii>sb://wabi-australia-southeast-relay22.servicebus.windows.net/
0755b3d2-c4de-40b7-a189-88dccefad1a4/</ii>' is unreachable.
I expect there are a few scenarios where you would need to remove existing gateway clusters when the servers are no longer configured or available.
I am having issues installing the Power BI Gateway (powerbigatewayinstaller.exe). It seems the installer doesn't initiate/run.
I think there might be an issue with the application itself, since I am having the same issues on three different computers.
I have tried:
- Run as administrator
- Start the installer from Run
- Check the Task Manager if the process is actually running, with no trace of the gateway.
So I figured I check the Event viewer, and found a .net runtime error with event id 1026. There's also an application error, but I presume this is down to the .net runtime error. The information from the event viewer is as follows:
Tillämpningsprogram: PowerBIGatewayInstaller.exe Framework-version: v4.0.30319 Beskrivning: Processen avslutades på grund av ett ohanterat undantag. Undantagsinformation: System.IO.FileNotFoundException vid Microsoft.DataProxy.PowerBIInstallDownloader.LandingPageViewModel..ctor(Microsoft.DataProxy.PowerBIInstallDownloader.MainViewModel) vid Microsoft.DataProxy.PowerBIInstallDownloader.MainViewModel..ctor() vid Microsoft.DataProxy.PowerBIInstallDownloader.MainWindow..ctor() Undantagsinformation: System.Windows.Markup.XamlParseException vid System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri) vid System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri) vid System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri) vid System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean) vid System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext) vid System.Windows.Application.DoStartup() vid System.Windows.Application.<.ctor>b__1_0(System.Object) vid System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) vid System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) vid System.Windows.Threading.DispatcherOperation.InvokeImpl() vid System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) vid System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) vid System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) vid MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) vid System.Windows.Threading.DispatcherOperation.Invoke() vid System.Windows.Threading.Dispatcher.ProcessQueue() vid System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) vid MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) vid MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) vid System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) vid System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) vid System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) vid MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) vid MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) vid System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) vid System.Windows.Application.RunDispatcher(System.Object) vid System.Windows.Application.RunInternal(System.Windows.Window) vid Microsoft.DataProxy.PowerBIInstallDownloader.App.Main()
Hello, I need some help. I can not update the reports. Through the on-demand and scheduled update, the message "Cancellation occurred while sending or receiving a request" appears.
Yesterday, all my datasets were refreshing just fine but today nothing happens.
- The automatic refresh hasn't done anything.
- When I press "Refresh now", I get a "popup" saying "preparing refresh" for a split second and then nothing happens.
The only way to update the data is to refresh the Desktop version and then upload it.
I have datasets connection to an on-premises database and one connecting to a sharepoint site.
- The on-premises connection usually works perfect, but now nothing happens.
- The sharepoint connection usually brings up an error, if I try to refresh, but now nothing happens (I just tried it this time as a test, as it usually doesn't work automatically).
Can you please help troublefinding - It seems like an issue on you online portal somehow.
Thanks in advance.
This issue has been occuring for the past week, only for one specific report. Publishing from the desktop client still works normally and is being used as a manual refresh.
Details Type Start End Status Message
|On demand||21/09/2017 4:40:43 PM||21/09/2017 4:40:48 PM||Failed||The gateway operation has been cancelled explicitly by the user or from a timeout.|
All of a sudden all of my automatic refreshes have been failing due a message "Your data source can't be refreshed because the credentials are invalid." Nothing has changed and I don't know why I am receiving this message.
I click on Edit Credentials (Salesforce credentials) and unable to do so because now I'm receiving this message "Failed to update data source credentials: We're sorry, an error occurred during evaluation".
This was all working fine a couple of days ago and yesterday, I started running into the refresh issue. I have deleted my cache, cookies, etc. but I am unable to edit my Salesforce creditials.
Anyone have any ideas / thoughts?
Our report - which is based on MY SQL Queries - seems to experience difficulties regarding the scheduled refresh. This is the error that we got back:
If anyone can offer any advice or provide further information that would be highly appreciated
I'm getting this error since yesterday on a new dataset. It is a simple excel file table. I've done the following.
Signed out of Power BI Desktop and back in
Got the latest personal gateway
turned the gateway service off / on
republished multiple times during this process.
Others seem to be having the same issue. see thread here
There is a current support site error message, but it is specific to SharePoint as a data source only.
After September 2017 update (2.50.4859.502) we've faced an issue similar to one 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 Desktop version resolves the issue.
I was hoping this bug would be fixed in October update, but that didn't happen...
Estou com uma situação posterior :
Tenho uma fonte de dados ODBC do banco Firebird, quando requisito uma atualização dos dados no Power BI desktop, o mesmo roda perfeitamente, inclusive consigo efetuar uma publicação de relatório, no entanto, criar uma fonte de dados (servidor de relatório) dentro do meu gateway resultados nesse erro:
Consigo a ajuda de vocês?
Since yesterday I'm having an issue connecting to an excel file in a Sharepoint folder. It was already working, but I made some changes and republished it. Refresh works fine in Power BI Desktop, but online. It seem it's trying to connect to a Sharepoint list, instead of folder. I have an other report connecting to an other excel file in the same folder and it works fine. Could this be connected to the issue in North Europe? I'm in that datacenter.
I wondr if there is someone facing the same problem as me.
My Enterprise Gateway was working smoothly until yesterday. I don't know how but i cannot choose my EG to refresh my dataset :
I created a sample report to test the datasources, in the example below the error (EG disabled) is happening when i use a merge join in my power query :
when i deploy the report with this step i have this error "You don't have any gateway installed or configured for the data sources in this dataset. Please install a new personal gateway or configure the data source for an existing data gateway"
but deploying without the merge join, everything works fine => i can select the EG!
I use Two souces in my report :
SQLSEVER for RLS table
Excle file for Fichier table
It seems strange to have this issue after a join operation in the model.
Thank you in advance for your help.
I have been using PBI Publisher for Excel for a while to connect to a Power BI model in the cloud. Everything was fine until this morning when I updated to the new version 2.37.3272.33601, with this version all my connections to data have been closed and I can no longer update my reports.
Anyone experiencing the same issue? All my users are in an older version (2.37.3272.28541) and things are working fine for them.
We are running into the problem that our redshift cluster, that is not open to all IP addresses, can't be reached from PowerBI Service as it is using multiple IP addresses that are also changing on weekly basis. But it can't be the idea of having this Redshift cluster open to all connections. For a company like us this is absolutly not acceptable. Is there any solution for this issue.
PS: connection on or Redshift Staging Cluster where we allow all connection works perfectly fine...