Approved

During the past days, some of our users have encountered error ms dtc error xp. This problem occurs for a number of reasons. Let’s take a look at them now.

This article describes all Windows accounts that the Microsoft Distributed Transaction Coordinator (MSDTC) must run on Windows.

Source Application: Windows Server 2012, Windows 8, Windows 7
Original ba numberKnowledge Base: 903944

Resume

On all Windows client and server operating systems, you may need to restart the MSDTC service to perform the following actions. To restart the service, follow these steps for msdtc:

1. For Windows 8.1 and Windows 8

   • On the Start Presentation screen, swipe up from the secondary right side to open the charms, find, use, and then find cmd. (Or, as if you were using a guitar and mouse, type any desktop into cmd.) In the search rankings, right-click or hold Command Prompt and select Run as administrator.

   For Windows 7 and earlier

   • Press Windows logo key + R, type cmd in the Run box, and press Enter. Right click on cmd then select Run as administrator.
2. 

   In this case, type net stop msdtc and press ENTER.

3. Type net start, msdtc then press ENTER.

4. Open a component including the Microsoft Management Console (MMC) Services snap-in. To do this, click the Start button. and then “execute”. Enter dcomcnfg.exe and click OK.

5. 

   Extend component services, mentally improve computers, and then expand your workspace.

6. Right-click My Computer, then click Properties.

7. Click the MSDTC tab, then click Security Configuration.

8. Approved

   The ASR Pro repair tool is the solution for a Windows PC that's running slowly, has registry issues, or is infected with malware. This powerful and easy-to-use tool can quickly diagnose and fix your PC, increasing performance, optimizing memory, and improving security in the process. Don't suffer from a sluggish computer any longer - try ASR Pro today!

   
   

   Change the account in DCT Logon To Account NT AUTHORITY NetworkService. If password a is required, enter a unique blank password.

9. Click OK twice.

For Windows And XP Windows Server 2003

Restart Windows and XP, then continue on Windows Server 2003. The MSDTC provider must be running under the Windows NT AUTHORITY NetworkService account. You

If you replace the current account with an account other than the NetworkService account, the distributed transaction will not work. The transaction fails because the MSDTC service is unable to mutually authenticate with the other parties involved in the transaction. Local transactions, which often use the MSDTC service, can also fail.

On Windows, Microsoft NT 4.0, Microsoft and Windows 2000, you have the option Possibility to change the default MSDTC service description to a domain account. You could potentially change the account to Windows Authentication when performing an XA restore operation on an XA database such as an Oracle database.

However, you cannot change the plan in Windows Server 2003 to Windows XP. Instead, you must assign the roles required to perform XA recovery to the NetworkService account on each computer that can run the MSDTC service.

The exact method for jointly determining the recovery of an XA operation is configured for each XA database. Usually you really need to add the IT department of the computer that is running the MSDTC service to the user group that can perform the wonderful xa restore operation on the XA database. Also, since the NetworkService website is a restricted account, you only need to grant access to the NetworkService account to make sure you are in the folder where the XA DLL is located.

To change the account for which the MSDTC service is being resubmitted to account NetworkService, follow these steps: Start,

1. Click Run, run regedit, and then click OK. AND

2. search. If so, click the following subkey: HKEY_LOCAL_MACHINE SOFTWARE Microsoft MSDTC .

   Generally, if you have the following entries, go to 6:

   • Turnoffrpcsecurity
   • Allow currpccalls
   • Rollback to unprotected pcifnecessaire

Create an entry

3. TurnOffRpcSecurity :

   1. On the Edit menu, choose New and click DWORD Value.
   2. Type TurnOffRpcSecurity and press Enter.

4. Create Record AllowOnlySecureRpcCalls :

   1. On the Current Editing menu, point to New and then just click DWORD Value.
   2. Type And allowonlysecurerpccalls and press Enter.

5. Create an entry FallbackToUnsecureRPCifNeeded :

   1. On the Edit menu, choose New and click DWORD Value.
   2. Type FallbackToUnsecureRPCIfNeeded and press Enter.

6. Specify a DWORD value for the TurnOffRpcSecurity entry:

   1. Right-click TurnOffRpcSecurity, then click Edit.
   2. In the dialog boxdo not “Change DWORD Value” enter value type 1 and click “OK”.

7. Set the DWORD value in AllowOnlySecureRpcCalls :

   1. Right-click AllowOnlySecureRpcCalls and choose Modify.
   2. Enter Et 0 in the Modify DWORD Value dialog box, but click OK.

8. Set to DWORD value to get FallbackToUnsecureRPCIfNeeded :

   1. Right-click and select Modify if necessary.
   2. In the Modify DWORD Value dialog box, enter And 0 and click OK.

It is important to restart the MSDTC service after making changes. To resume the MSDTC service, do all of the following:

1. Click Start, Run, type cmd and click OK.
2. Type net banid msdtc and press Enter.
3. Type net outset, msdtc and press Enter.
4. Open the Microsoft Component Service Management MMC snap-in. To do everything, click Start, Run, select dcomcnfg.exe, then click OK.
5. Expand Component Services, expand Computers, and then expand My Computer.
6. ClickRight click on “My Computer”, then click on “Properties.”
7. Click the MSDTC tab, then click Configuration Security.
8. Change the DCT connection account in the account to NT AUTHORITY NetworkService. If password a is required, enter a blank password.
9. Click OK twice. Functionality

Links

• What’s new in the Windows Distributed Transaction Coordinator service
• Account & Permission Management

The third-party products discussed in this article are manufactured by companies that are virtually independent of Microsoft. Microsoft offers an extended warranty, implied or not, regarding the performance or reliability of these products.

Application Server

• Windows 2012 R2 Data Center
• Windows Server 2012 R2 Standard
• Windows Server 2012 R2 Basics
• Windows 8.1 Enterprise
• Windows 8.1 Professional
• Windows 8.1
• Windows Server 2012 Data Center
• Windows Server 2012 Data Center
• Windows Server 2012 Standard
• Windows Server 2012 Standard
• Windows Server 2012 Essentials
• Windows 8 Enterprise
• Windows 8 Professional
• Windows 8
• Windows Server 2008 R2 Data Center
• Windows Server 2008 R2 Standard
• Windows Server 2010 R2 Enterprise
• Windows 7 Enterprise
• Windows 7 Professional
• Windows Server 2008 Data Center
• Windows Server 2008 Standard
• Windows Server 2008 Enterprise
• Windows Vista Enterprise
• Windows Enterprise
• Microsoft Vista Windows Server 2003 Enterprise Edition (x86 32-bit)
• Microsoft Windows Server 2003 Standard Edition (x86 32-bit)
• Microsoft Windows Server 2004 Datacenter Edition (x86 32-bit)
• Microsoft Windows Server 2003 Web Edition
• Microsoft Windows Server 2003 Standard x64 Edition
• Microsoft Windows Server ’03 Enterprise x64 Edition
• Microsoft Windows Server 2004 Datacenter x64 Edition
• Microsoft Windows XP Professional
• Microsoft Windows XP Professional x64 Edition

• 5 Request to read

This article provides information on how to modify the registry. Be sure to back up the registry before editing it. Make sure you know how to fix your registry if you are having problems. For more information on backing up, restoring, and editing the registry, see Registry extended info Mation for Windows Users .

Serious problems can arise if you think you are editing the registry by mistake using a registry editor or some other method. These problems may require a reinstallation of the operating configuration. Microsoft cannot guarantee that these health problems can be solved. Change computers at your own risk.

Charles Pye