Forum Discussion
AsyncOperationStreamingRetriesExhausted Refresh Failures
Microsoft support ended up telling me that it was an outage in the West region that was affecting some but not all customers. They said that the reason it wasn't shown on the outage page was because it wasn't universal to all customers in the region. It tapered off through Friday and Saturday and seems to be completely gone this morning.
Microsoft support ended up telling me that it was an outage in the West region that was affecting some but not all customers. They said that the reason it wasn't shown on the outage page was because it wasn't universal to all customers in the region. It tapered off through Friday and Saturday and seems to be completely gone this morning.
Xaraja This issue also affected us as well, same dates. Between the 10th and the 13th we had over 200 dataset refreshes fail in production. It was a lot! We have an open ticket too. We also did see some more on 1/20 though. We received the same response. As a side note, for lbendlin our gateway configs are not set to stream before completion (which is the default setting).
Xaraja
I am seeing the issue which was mentioned as below :
XXXXXXXX has failed to refresh.
Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.{"error":{"code":"DM_GWPipeline_Client_AsyncOperationStreamingRetriesExhausted","pbi.error":{"code":"DM_GWPipeline_Client_AsyncOperationStreamingRetriesExhausted","parameters":{},"details":[],"exceptionCulprit":1}}} Table: XXXX
as per solution, it was said that it is resolved but still this issue is shows up constantly to me.
any advice?thanks
Santosh kumar p
I filed a support ticket with Microsoft and spent some time on a conference call with a representative, but we didn't make any changes to our configuration and I'm not sure we actually accomplished anything to fix the problem. That's all I know to suggest.
Microsoft support did tell me that the problem wouldn't be totally fixed until the end of February, so it's possible that's why you're seeing it, and reporting it to them might be helpful.
Xaraja Thank you. I will do the same.
