Quantcast
Channel: Service topics
Viewing all articles
Browse latest Browse all 61769

Connection to BusinessCentral cloud: request failed, Error 10122

$
0
0

Hi everyone, 

 

I'm coming across a rather frustrating issue. My report refreshes keep getting timed out on one table, the sales quotes. There hasn't been a giant increase on quotes that could cause the size of this table to be too large. Nor have we changed anything to the connecting webservice. So I don't really understand why this table suddenly is starting to time out.

 

See error below: 
Data source error: DataSource.Error: Dynamics365BusinessCentral: Request failed: The operation has timed out. Microsoft.Data.Mashup.ErrorCode = 10122. DataSourceKind = Dynamics365BusinessCentral. DataSourcePath = Dynamics365BusinessCentral. ;Dynamics365BusinessCentral: Request failed: The operation has timed out. The exception was raised by the IDataReader interface. 


Every dataset refresh via the service there is a small shot that it would succeed. And even if it succeeds, it's only after 2-4 tries of approx 1h. Occasionally it works on the first try. The dataset is trying to connect to Business Central in the cloud. This issue happens for multiple different reports all running for the same company within Business Central. The reports also all run at different timings to keep the workload lower. But also when trying to refresh on the desktop version it would fail with a timout. I already tried clearing cache in PBI desktop.

I had issues with refreshing the dataset before, that issue was noted and solved in this thread. That's also how my connection string is now built up Dynamics365BusinessCentral.ApiContentsWithOptions(null, null, null, [UseReadOnlyReplica = null]). I have tried setting it back to a null but the timeout keeps appearing. Both on desktop and service. 

 
I also came across a similar topic here but this is based on an on-prem version of BC, we have a cloud version. We're also not running on the Premium version of Power BI, but on the pro. 

The refresh issues started happening april 1st. Hoped it to be an april fools but sadly it wasn't.
Anyone else experiencing something similar or has found a solution to bypass the failures? 

Viewing all articles
Browse latest Browse all 61769

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>