Solved: refresh failure for one of eight datasets (persona...

MojoGene · ‎04-04-2018

One of my eight datasets is having strange refresh failures. The personal gateway shows that it is online and running. The data source credential are unchanged and show no issues. I updated the personal gateway to the latest version. I deleted and re-uploaded the dataset in question. Oddly, the dataset refreshed as soon as it was uploaded, but will not refresh now. (Automatic refreshes are scheduled.) Any advice appreciated.

Here is the failure message:

Something went wrong

Please make sure your data gateway (personal mode) is installed and configured properly.
Please try again later or contact support. If you contact support, please provide these details.

Processing errorPlease make sure your data gateway (personal mode) is installed and configured properly.

Cluster URIWABI-US-EAST2-redirect.analysis.windows.net

Activity ID3213d47d-5ba7-49dc-b4a1-3e2bcf5ec510

Request ID37e8d5da-5adc-85aa-ca78-03cd80712749

Time2018-04-04 11:57:28Z

MojoGene · ‎04-05-2018

@Anonymous

Thanks for the pointer. I had already found that post and worked my way through a lot of it. (Much of it is beyond my humble skills.) I didn't find the answer there.

I did somehow stumble on the answer. I had an inquiry in the affected dataset that captured the time and date from the web. It was not updating properly, so I deleted the inquiry from the dataset. That cured the refresh issue.

Still can't explain why the error message was pointing to the personal gateway as the source of the problem.

View solution in original post

Anonymous · ‎04-04-2018

Hi @MojoGene,

See details in this post. The linked article is a good starting point.

https://community.powerbi.com/t5/Service/Failed-to-parse-gateway-core-config-file-Object-reference-n...

Thanks,
Richard

MojoGene · ‎04-05-2018

@Anonymous

Thanks for the pointer. I had already found that post and worked my way through a lot of it. (Much of it is beyond my humble skills.) I didn't find the answer there.

I did somehow stumble on the answer. I had an inquiry in the affected dataset that captured the time and date from the web. It was not updating properly, so I deleted the inquiry from the dataset. That cured the refresh issue.

Still can't explain why the error message was pointing to the personal gateway as the source of the problem.

Anonymous · ‎04-05-2018

@MojoGene, I think that when the query to the data returns an error the gateway throws a generic error and then you have to dig into the gateway logs to determine the exact root cause of the error.

Glad you were able to resolve your issue!