Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: Can't download files from SharePoint Server 2013 document libraries by using SharePoint Services adapter

FIX: Can't download files from SharePoint Server 2013 document libraries by using SharePoint Services adapter

View products that this article applies to.

Symptoms

Assume that you use the SharePoint Services adapter in Microsoft BizTalk Server 2013. When you download files from SharePoint Server 2013 document libraries that contain managed metadata columns by using the adapter, you receive the following error message:
The Windows SharePoint Services receive adapter has failed to process the SharePoint file FileName. The following error has been encountered:
[System.InvalidCastException] Unable to cast object of type 'System.Collections.Generic.Dictionary`2[System.String,System.Object]' to type 'Microsoft.SharePoint.Client.Field'.
Error code: 12310
Once you have addressed the issue causing this problem, you can undo the check-out for this file and the adapter will try to process it again.
This error was triggered by the Windows SharePoint Services receive location or send port with URI wsss://[...]?ViewName=ToBizTalk.
Windows SharePoint Services adapter event ID: 12457

↑ Back to the top

Cause

The issue occurs because BizTalk Server 2013 uses SharePoint 2010 client libraries. However, SharePoint 2013 client libraries are expected.

↑ Back to the top

Resolution

Cumulative update information

This issue was first fixed in the following cumulative update of BizTalk Server:

↑ Back to the top

Workaround

To work around this issue, use one of the following workarounds:
  • Don't use managed metadata columns in SharePoint Server 2013 document libraries.
  • Replace the referenced SharePoint 2010 assemblies with SharePoint 2013 assemblies from the SharePoint 2013 server:
    • Microsoft.SharePoint.Client, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c
    • Microsoft.SharePoint.Client.Runtime, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e94
    Then, create the following binding redirection in BizTalk configuration files (BTSNTSvc.exe.config and BTSNTSvc64.exe.config):
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.SharePoint.Client"
                              publicKeyToken="71e9bce111e9429c"
                              culture="neutral" />
            <bindingRedirect oldVersion="14.0.0.0"
                             newVersion="15.0.0.0"/>
          </dependentAssembly>
                      <dependentAssembly>
            <assemblyIdentity name="Microsoft.SharePoint.Client.Runtime"
                              publicKeyToken="71e9bce111e9429c"
                              culture="neutral" />
            <bindingRedirect oldVersion="14.0.0.0"
                             newVersion="15.0.0.0"/>
          </dependentAssembly>
    </assemblyBinding>

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

For more information about the service packs and cumulative update list for BizTalk Server, see KB 2555976: Service pack and cumulative update list for BizTalk Server .

For more information about BizTalk Server hotfixes, see KB 2003907: Information about BizTalk hotfixes and cumulative update support .

↑ Back to the top

Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 3050885
Revision : 1
Created on : 1/7/2017
Published on : 10/9/2015
Exists online : False
Views : 208