Forum Discussion

Razorbx13's avatar
Razorbx13
Post Patron
4 years ago

Scheduled Refresh Error Message

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

Need Help

4 Replies

  • Vera_Carey's avatar
    Vera_Carey
    Frequent Visitor
    4 years ago

    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)

     

  • v-easonf-msft's avatar
    v-easonf-msft
    Community Support
    4 years ago

    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

  • Razorbx13's avatar
    Razorbx13
    Post Patron
    4 years ago

    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.