Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi @vkal12
I have seen this error when the connection to SharePoint has been rejected from the Azure end of things. What is interesting in your case though is that the connection comes back and works again without anything being done to fix it.
It is probably just 'one of those things' and the way around it may be to write in a way of retrying when loads fail. You can do this with the errormode statement and checks before and after each load with the noofrows function. You can then have a while loop which keeps going around until data is refreshed, or a retry limit is met.
Alternatively, as you are on-prem, you can just let the reload fail and set the number of retries on the reload process to a suitable number.
Hope that helps.
Steve
Hi @vkal12
I have seen this error when the connection to SharePoint has been rejected from the Azure end of things. What is interesting in your case though is that the connection comes back and works again without anything being done to fix it.
It is probably just 'one of those things' and the way around it may be to write in a way of retrying when loads fail. You can do this with the errormode statement and checks before and after each load with the noofrows function. You can then have a while loop which keeps going around until data is refreshed, or a retry limit is met.
Alternatively, as you are on-prem, you can just let the reload fail and set the number of retries on the reload process to a suitable number.
Hope that helps.
Steve