APP 2013 APP SCOPED TIPO ESTERNO TIPO ODATA Throttling Anche se è disabilitato

Question

Ho un'app per SharePoint-Hosted 2013 che utilizza un tipo di contenuto esterno OTATA (all'interno dell'app stessa).Con minori quantità di dati funziona bene, ma con risultati più grandi, le chiamate di Odata stanno dando un messaggio di errore sull'essere strozzato.

<m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
<m:code>-2146232832, Microsoft.SharePoint.SPException</m:code>
<m:message xml:lang="en-US">
OData Service Connector has throttled the response. The response from OData Service contains more than '3000000' bytes. The maximum amount of data that can be read through OData Service Connector is '3000000'. The limit can be changed via the 'Set-SPBusinessDataCatalogThrottleConfig' cmdlet.
</m:message>
</m:error>

.

Leggo questo articolo su Throttling: http://blogs.msdn.com/b/bcs/Archive/2010/02/16/bcs/Archive/2010/02/16/bcs-PowerShell-introduction-and-throttle-Management.aspx

Dopo aver letto questo articolo ho disabilitato la limitazione per la dimensione e il timeout di Odata utilizzando questo PowerShell:

$bdcProxy = Get-SPServiceApplicationProxy | where {$_.GetType().FullName -eq ('Microsoft.SharePoint.BusinessData.SharedService.' + 'BdcServiceApplicationProxy')}
$odataRule = Get-SPBusinessDataCatalogThrottleConfig -Scope OData -ThrottleType Size -ServiceApplicationProxy $bdcProxy
Set-SPBusinessDataCatalogThrottleConfig -Identity $odataRule -Enforced:$false
$odataRule = Get-SPBusinessDataCatalogThrottleConfig -Scope OData -ThrottleType Timeout -ServiceApplicationProxy $bdcProxy
Set-SPBusinessDataCatalogThrottleConfig -Identity $odataRule -Enforced:$false

.

L'ho anche eseguito per lo scope del WCF.

Ma ho ancora lo stesso messaggio di errore.Tutte le macchine nella fattoria sono state riavviate completamente dopo aver funzionato.Qualche idea che altro avrebbe causato questo, cose da controllare, qualsiasi cosa?

Answer 1

I know this is an old question, but I recently had the same problem so I thought I'd post my solution for anyone else who finds this post.

Basically, I ran into the exact same problem, I followed the very limited information available and nothing seemed to change. So I opened a support case with Microsoft and this is a known issue. The workaround/correct procedure is to use the -FileBacked parameter on the Get-SPBusinessDataCatalogThrottleConfig command. The documentation on TechNet isn't super helpful for the parameter, stating:

Requests the throttling configuration for file backed metadata catalogs.

So in the case of this question changing the command to be:

$odataRule = Get-SPBusinessDataCatalogThrottleConfig -FileBacked -Scope OData -ThrottleType Size -ServiceApplicationProxy $bdcProxy
Set-SPBusinessDataCatalogThrottleConfig -Identity $odataRule -Enforced:$false

That worked for me.