0 Kudos

URGENT - Live Figures Down

Status: Needs Info
by jak82 Member on ‎03-17-2017 07:44 AM



We updated our gateway two days ago and everything was working fine, came in this morning and we are receiving this error.


This is urgent for us to resolve as they are live sales figures for our managers.  The code behind them hasnt changed and the gateways says the connection to the server is fine .... HELP!!




Status: Needs Info
by jak82 Member
on ‎03-17-2017 07:49 AM
Sorry we couldn't load the data for this visual
We reached the data gateway, but the gateway can't access the on-premises data source.
Please try again later or contact support. If you contact support, please provide these details.
Error CodeDM_GWPipeline_Gateway_DataSourceAccessError
Underlying error code-2146232060
Correlation ID0722c7d5-99fd-cfc9-a227-f0159cfad78c
Underlying error messageThe identifier that starts with '-- returns 2043 rows 
-- Order Header Data

-- Order Details Data
insertbk.ttlcode, -- product/publica' is too long. Maximum length is 128.
Activity IDda2636dc-081d-e3a3-ebbc-e0286c6a1c65
Request ID5df34fc3-e5f8-6dc6-46f7-40e41c98d497
TimeFri Mar 17 2017 14:47:47 GMT+0000 (GMT Standard Time)
Cluster URIhttps://wabi-north-europe-redirect.analysis.windows.net
by jak82 Member
on ‎03-17-2017 08:56 AM

Tested the pbi on the desktop and it works fine, but on upload to the service it stops working.  It seems to not be parsing the sql correctly when online!!!

by v-haibl-msft Super Contributor
on ‎03-21-2017 01:06 AM



Have you upgraded the gateway in your environment? If it is not the latest one, you can try to upgrade and have a try again.

If issues persists, I suggest you to create a support ticket at http://support.powerbi.com (see bottom of page).


Best Regards,


by Moderator Vicky_Song
on ‎03-21-2017 01:07 AM
Status changed to: Needs Info
by jak82 Member
on ‎03-21-2017 04:42 AM



We created the support ticket and it seems like the PowerBI online has changed the way it handles SQL queries.  


You can no longer have SQL comments in the query, we have been told Microsoft is aware of this new issue and is currently working on a fix.  Though for the time being I have to republish all our reports.