Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Symptoms

Consider the following scenario:

  • You create or use the following domain accounts:

    • An account to run the BizTalk host instance (for example, Domain\btssvc)

    • An account to access a file share (for example, Domain\btsfile)

  • You set up Microsoft BizTalk Server 2013 R2 on a server that is running Windows Server 2012 R2.

  • You create a BizTalk host instance that is configured to run as the domain user (Domain\btssvc).

  • You create a file share on the file server that is in the same domain or another trusted domain. Then, you enable access to this share for only the Domain\btsfile account user. (You do not enable access to this share for the Domain\btssvc user.)

  • You create and enable a file receive port and a file adapter receive location to receive files from the share, or you create a file adapter send port to send files to the share. You also specify the Domain\btsfile account user in the alternative credentials setting.

In this scenario, the file receive location and the file send ports fail, and you receive the following error message:

Err (800704c3)


Additionally, the following error is logged in the event log:

ERROR_SESSION_CREDENTIAL_CONFLICT

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this update in Windows 8.1 or Windows Server 2012 R2, you must first have update 2919355 installed.

To resolve this issue, you must also install Cumulative Update 1 for BizTalk Server 2013 R2.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 8.1 and Windows Server 2012 R2 file information and notesImportant Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" on the page. Always refer to the "Applies to" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.17xxx

    Windows 8.1 and Windows Server 2012 R2

    RTM

    GDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 8.1 and Windows Server 2012 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 8.1

File name

File version

File size

Date

Time

Platform

Mrxsmb20.sys

6.3.9600.17891

154,112

29-May-2015

02:26

x86

Mrxsmb.sys

6.3.9600.17891

328,704

29-May-2015

02:25

x86

For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Mrxsmb20.sys

6.3.9600.17891

202,240

29-May-2015

03:16

x64

Mrxsmb.sys

6.3.9600.17891

401,408

29-May-2015

03:15

x64

Additional file information for Windows 8.1 and Windows Server 2012 R2

Additional files for all supported x86-based versions of Windows 8.1

File name

X86_7106d866bfb7000f6ca117835c774646_31bf3856ad364e35_6.3.9600.17891_none_ce1358e3ebd0693c.manifest

File version

Not applicable

File size

1,043

Date (UTC)

29-May-2015

Time (UTC)

09:15

File name

X86_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.3.9600.17891_none_1f6cdc0ea56a5184.manifest

File version

Not applicable

File size

4,096

Date (UTC)

29-May-2015

Time (UTC)

03:30

File name

X86_microsoft-windows-smbminirdr_31bf3856ad364e35_6.3.9600.17891_none_142353a86cc1dfb1.manifest

File version

Not applicable

File size

95,613

Date (UTC)

29-May-2015

Time (UTC)

03:29

Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2

File name

Amd64_0372f9cc13c8cb75496ed447c0c6c3a1_31bf3856ad364e35_6.3.9600.17891_none_3cb586f693f382e9.manifest

File version

Not applicable

File size

1,049

Date (UTC)

29-May-2015

Time (UTC)

09:15

File name

Amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.3.9600.17891_none_7b8b77925dc7c2ba.manifest

File version

Not applicable

File size

4,100

Date (UTC)

29-May-2015

Time (UTC)

04:16

File name

Amd64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.3.9600.17891_none_7041ef2c251f50e7.manifest

File version

Not applicable

File size

95,617

Date (UTC)

29-May-2015

Time (UTC)

04:15


Status

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

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×