PowerBI Service refresh issues - keyword isn't supported

[DamienW]

My DataSet in the PowerBI service is not refreshing due to issues processsing the Dataset (Per the following error message):

Message:	The keyword isn't supported: version. Parameter name: keyword Table: [TableName].
Cluster URI:	WABI-AUSTRALIA-SOUTHEAST-redirect.analysis.windows.net
Activity ID:	ff4cbfb5-36f5-47d1-9790-98aac4265ed1
Request ID:	a02bbf13-94de-9159-7ac9-ed9597ec1e20
Time:	2017-10-31 22:45:39Z

However the table in question only has 3 columns, primary key, foreign key and value.

The Desktop version does not show any issues with the dataset and refreshses no problems at all.

The gateway used is the on-premises gateway (not personal mode), and has been successfully updating up until yesterday.

Any ideas?

[v-haibl-msft]

@DamienW

What is the datasource and connection mode in your scenario?

Do you have any parameter created in Query Editor?

Could you please also help collect the fiddler traces during refresh the dataset in PBI Service? Please enable following option in fiddler and make sure there is only one browser page/tab opened during the collection.

Then you can share the .saz file through online file service like OneDrive.

Best Regards,
Herbert

[DamienW]

The data source is an SQL DB

However I do have some parameteres generated by the QueryEditor, these are Date Values, however not related to the error message, as the date valies are in their own tab.

With regards to fiddler traces, work in progress, get those as soon as i can.

[DamienW]

@v-haibl-msft

The error message I get in Fiddler is the following, also, not sure if this is helpful, each time I try to refresh the error message now lists a different table each time.

POST https://v20.vortex-win.data.microsoft.com/collect/v1 HTTP/1.1
Cache-Control: no-cache
Connection: Keep-Alive
Content-Type: application/x-json-stream; charset=utf-8
Content-Encoding: deflate
Accept: application/json
Accept-Encoding: gzip, deflate
User-Agent: MSDW
X-UploadTime: 2017-11-07T22:41:00.649Z
X-AuthMsaDeviceTicket: t=GwAWARR4BAAUW6CljNsPH2VM5ReSSizGbhFDONYOZgAAEDCIxexIAfEbuxafC3n5CgjgAFZDGOwzbamFr20o1I5l8HI5H/hZUYyANe+SBzYwWcupYOErRv+Ezmn92yJkZLtGe7xNbgDGaBcPVA/piia3a/Pez4ixXVNJfnbdYv0BEgGCQQg9/KCicI7abl6h5bqsMjjU4JaebfFevLJ+K265m2wK2JNOfIA8oive5zpkp1ktl5YurVKSSotOG/QtmmNRaelNaZ8evD0sRkfcpv2f+wU9mb3mlAmz56RHFlpfi0wxC1+CwFTJ5kHm7DuTy29cZJCVnCKUSROkM4M1ZJUah5es3o7iUhxbRgBbIpukcKhHGwE=&p=
Content-Length: 1206
Host: v20.vortex-win.data.microsoft.com

HTTP/1.1 408 Request body incomplete
Date: Tue, 07 Nov 2017 22:41:01 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
Cache-Control: no-cache, must-revalidate
Timestamp: 08:41:01.154

The request body did not contain the specified number of bytes. Got 0, expected 1,206

Per the above comment about QueryEditor, I did make a change to that last week, however reverted the change yesterday, to and was able to resave (new file name) and upload and refresh successfully, however now getting the same error message again last night and today with the scheduled refresh.... This is fustrating, the only way I can update BI currently, is refreshing locally via the desktop and uploading to the service.

[DamienW]

Just an update to this post, found out, that everytime I uploaded a new version of the PBIX, it would reset the gateway to none (as I don't use a local gateway) meaning the online service couldn't connect and would time out.

I don't think "keyword isn't supported" adequately explains the above scenario.

[Ualas]

Estou com esse mesmo problema com alsguns conjuntos de dados.

Observação é que a cada tentativa de atualização, o erro aponta para uma tabela difente: