2013 앱이 비활성화되었지만 외부 콘텐츠 유형 Odata 스로틀을 범위 지정했습니다.

Question

OData 외부 콘텐츠 유형 (앱 자체 내부)을 사용하는 2013 SharePoint 호스팅 앱이 있습니다.더 작은 양의 데이터를 사용하면 잘 작동하지만 결과가 크면 ODATA 호출이 스로틀에 대한 오류 메시지가 나타납니다.

<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>

.

나는이 기사를 제한에 대해 읽었습니다. http://blogs.msdn.com/b/bcs/archive/2010/02/16/bcs-powershell-introduction-and-andthertle-management.aspx

이 기사를 읽은 후이 PowerShell을 사용하여 Odata 크기와 시간 초과의 스로틀 링을 비활성화했습니다.

$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

.

WCF 범위도 실행했습니다.

그러나 여전히 동일한 오류 메시지가 나타납니다.농장의 모든 시스템도 실행 후 완전히 다시 시작되었습니다.어떤 아이디어가 이것을 일으키는 것, 확인해야 할 것들, 무엇이든,

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.