The Microsoft Distributed Transaction Coordinator service must run under the NT AUTHORITY\NetworkService Windows account

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry

INTRODUCTION

This article discusses the Microsoft Windows account that the Microsoft Distributed Transaction Coordinator (MSDTC) service must run in Windows.

More Information

On all Windows Client and Server Operating Systems, you may have to restart the MSDTC service to perform these steps. To restart the MSDTC service, follow these steps:
  1. For Windows 8.1 and Windows 8
    From the Start screen, swipe in from the right side to display the charms, select Search, and then search for cmd. (Or, if you are using a keyboard and mouse, type cmd at the Start screen.) In the search results, press-and-hold or right-click Command Prompt, and then select Run as Administrator.

    For Windows 7 and earlier versions
    Press the Windows logo key+R, type cmd in the Run box, and then press Enter. Right-click cmd, and then select Run as Administrator.
  2. Type net stop msdtc, and then press the ENTER button.
  3. Type net start msdtc, and then press the ENTER button.
  4. Open the Component Services Microsoft Management Console (MMC) snap-in. To do this, click Start, and then click Run Type dcomcnfg.exe, and then click OK.
  5. Expand Component Services, expand Computers, and then expand My Computer.
  6. Right-click My Computer, and then click Properties.
  7. Click the MSDTC tab, and then click Security Configuration.
  8. Change the account in DCT Logon Account to "NT AUTHORITY\NetworkService". If a password is needed, enter a blank password.
  9. Click OK two times.

For Windows XP and Windows Server 2003

Starting in Windows XP and then continuing in Windows Server 2003, the MSDTC service must run under the NT AUTHORITY\NetworkService Windows account.

If you change the account to an account other than the NetworkService account, the distributed transaction fails. The transaction fails because the MSDTC service cannot do mutual authentication together with other parties that are involved in the transaction. Local transactions that use the MSDTC service may also fail.

Note Other parties can be transaction managers, resource manager, or clients.

In both Microsoft Windows NT 4.0 and Microsoft Windows 2000, you can change the default MSDTC service account to a domain account. You may change the account to perform Windows authentication when you are performing an XA recovery operation on an XA database such as an Oracle database.

However, in Windows Server 2003 and Windows XP, you cannot change the account. Instead, you must give the permissions and the roles that are required to perform an XA recovery operation to the NetworkService account on the computer where the MSDTC service is running.


The exact method of setting up an XA recovery operation is specific to each XA database. Typically, you have to add the computer account of the computer where the MSDTC service is running to the list of users who can perform an XA recovery operation on the XA database. Additionally, because the NetworkService account is a restricted account, you must provide the NetworkService account access to the folder where the XA DLL is located.

To change the account that the MSDTC service runs under back to the NetworkService account, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
  1. Click Start, click Run, type regedit, and then click
    OK.
  2. Locate and then click the following subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC
    If the following entries exist, go to step 6:
    • TurnOffRpcSecurity
    • AllowOnlySecureRpcCalls
    • FallbackToUnsecureRPCIfNecessary
  3. Create the TurnOffRpcSecurity entry:
    1. On the Editmenu, point to New, and then click DWORD Value.
    2. Type TurnOffRpcSecurity, and then press ENTER.
  4. Create the AllowOnlySecureRpcCalls entry:
    1. On the Editmenu, point to New, and then click DWORD Value.
    2. Type AllowOnlySecureRpcCalls, and then press ENTER.
  5. Create the FallbackToUnsecureRPCIfNecessary entry:
    1. On the Editmenu, point to New, and then click DWORD Value.
    2. Type FallbackToUnsecureRPCIfNecessary, and then press ENTER.
  6. Set the DWORD value for the TurnOffRpcSecurity entry:
    1. Right-click TurnOffRpcSecurity, and then click Modify.
    2. In the Edit DWORD Value dialog box, type the value 1, and then click OK.
  7. Set the DWORD value for the AllowOnlySecureRpcCalls entry:
    1. Right-click AllowOnlySecureRpcCalls, and then click Modify.
    2. In the Edit DWORD Value dialog box, type the value 0, and then click OK.
  8. Set the DWORD value for the FallbackToUnsecureRPCIfNecessary entry:
    1. Right-click FallbackToUnsecureRPCIfNecessary, and then click Modify.
    2. In the Edit DWORD Value dialog box, type the value 0, and then click OK.
After you have made the registry changes, you must restart the MSDTC service. To restart the MSDTC service, follow these steps:
  1. Click Start, click Run, type cmd, and then click OK.
  2. Type net stop msdtc, and then press ENTER.
  3. Type net start msdtc, and then press ENTER.
  4. Open the Component Services Microsoft Management Console (MMC) snap-in. To do this, click
    Start, click Run, type
    dcomcnfg.exe, and then click
    OK.
  5. Expand Component Services, expand
    Computers, and then expand My Computer.
  6. Right-click My Computer, and then click
    Properties.
  7. Click the MSDTC tab, and then click
    Security Configuration.
  8. Change the account in DCT Logon Account to
    NT AUTHORITY\NetworkService. If a password is needed, enter a blank password.
  9. Click OK two times.

References

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
816633 "The call to the GetXaSwitch function failed" error message with the Oracle 9.x client installed
899191 New functionality in the Distributed Transaction Coordinator service in Windows Server 2003 Service Pack 1 and in Windows XP Service Pack 2
For more information about how to manage accounts and user rights for Microsoft Distributed Transaction Coordinator (MSDTC), visit the following Microsoft Developer Network (MSDN) Web site: The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Propriedades

ID do Artigo: 903944 - Última Revisão: 19 de ago de 2015 - Revisão: 1

Comentários