Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
I have a dataset that has a scheduled refresh. When it tries to refresh I get the following error:
An error happened while reading data from the provider: 'A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)'
This error occurs the majority of the time although sometimes it does work. However, I can refresh it in the service manually most of the time. Can someone give me a start of where to look? The only thing odd with this model is that it is attached to both a Service dataset and tables accessed through the gateway. TIA
Thanks for all your responses. I am still getting this error. Have updated the gateway, refreshed the model locally and scheduled refreshes throughout the day. I am still able to refresh the dataset locally but not in the service. Do not know if this is an issue, but in the model I attach to a Service dataset. When I go to Gateway I see this as part of my connections. See a "circle with and x" but do not know if that means anything. This is still going against another dataset. The lineage works fine and I think the credentials are fine. I refresh them fine in the service.
Hi, @Razorbx13
This error most likely indicates a temporary network problem.
It is recommended to schedule refreshes during times when the network is reliable.
Best Regards,
Community Support Team _ Eason
I can also recommend opening the model in design and seeing if your credentials a refresh. You can try to re-publish the model definition (metadata) and see if that helps (re-publishing model metadata can help refresh whatever settings on the Service that might have expired or need updating)
Hi @Razorbx13
Start by updating the Gateway and see what happens.
Regards
Amine Jerbi
If I answered your question, please mark this thread as accepted
and you can follow me on
My Website, LinkedIn and Facebook