Error when publishing PBIX file - Publishing is complete. However, we couldn't refresh your dataset

[Prafferty]

When publishing a PBIX file, I will receive an error that the publishing completed, but the dataset could not be refreshed.  After publishing, the report in Power BI Service will not have the changes I added to the PBIX file.  In addition, any dashboards with live pages pulled from the report will no longer work.  This error only occurs when I am publishing PBIX files that meet the following criteria:

1. Data Source is a SQL Server Database
2. Dataset already exists in Power BI Service and I am publishing a new version

This error has occurred for two different PBIX files that both meet the above criteria.  However, I also published some PBIX files that created new datasets in Power BI Service and those worked fine.  In addition, I published a PBIX file that used SSAS as the data source and that worked fine as well.  In addition, this SSAS report was tied to an existing dataset in the Service.

I found a few other issues and forum posts that address the same problem:

https://community.powerbi.com/t5/Issues/publishing-is-complete-however-we-couldnt-refresh-your-datas...

https://community.powerbi.com/t5/Desktop/Publishing-online-from-Desktop-not-working/td-p/173109

https://community.powerbi.com/t5/Desktop/Publishing-dataset-fails-and-destroys-live-pages/td-p/28737...

[v-jiascu-msft]

Hi @Prafferty,

I can't reproduce it. Please provide more details.

1. What's the mode? Import or Direct query?

2. Did you upgrade the Data Gateway?

3. Did you create the data source of the Gateway in the Service?

4. What's new of the new version?

5. Did you change the password of the credential of Sql Server?

6. Did the Sql Server allow the remote connect? and the TCP/ip connection?

7. Can you manually refresh the dataset?

Best Regards,

Dale

[Prafferty]

Hi Dale,

When reproducing, did you use a report/dataset that already existed in the Service.  If you publish a completely new report, the issue will not occur.  Answers to your questions are below:

1. What's the mode? Import or Direct query?

Import

2. Did you upgrade the Data Gateway?

Checked our current data gateway version and it is 14.16.6464.1.  Is there a newer version?

3. Did you create the data source of the Gateway in the Service?

Yes.  The data source for this Gateway exists.

4. What's new of the new version?

I have added additional visuals and report pages to the report.

5. Did you change the password of the credential of Sql Server?

No

6. Did the Sql Server allow the remote connect? and the TCP/ip connection?

Yes

7. Can you manually refresh the dataset?

No.  When I press the refresh button, the yellow warning sign stays in place.

[Prafferty]

Also, when I checked the new visual that was not working in the service, I got these details:

Activity ID7c849703-47eb-4908-9b61-a30062ec0ce4

Request ID0297bae4-d76d-3bac-4391-e1493f1789fc

Correlation IDa2b4fafc-48fb-b1fb-931c-a2ca3bd41a46

TimeMon Dec 11 2017 10:23:41 GMT-0600 (Central Standard Time)

Version13.0.3419.168

Cluster URIhttps://wabi-us-north-central-redirect.analysis.windows.net

[Prafferty]

Hi Dale,

Is there any update on the issue I reported?

Thanks,

Peter