The file is of course, digitally signed, which means it has been tried and tested to work optimally within a Windows environment. The purpose of this program is to allow multiple client applications to have more than one source of data, for any one transaction.
The msdtc. If msdtc. Through the use of msdtc. Whenever Microsoft Distributed Transaction Coordinator is loaded, or whenever an associated application is started, msdtc. There are also several different versions of this file currently available.
The default install location for this file is:. You can rest assured that it will not bring any harm to your system. By removing this process, you will lose the coordination functionality, which is likely to cause problems with the application s it was installed along with. In addition to that, removing this process may cause other applications to fail, such as. Note: Although it is recommended that you do not remove this service, it is possible for you to disable it.
If you are certain that none of the applications you are using require it. You can disable it by doing the following:. This process is known to be quite CPU intensive. Some of these malicious files may have a filename that is very similar to this process msdtc. 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.
Note Other parties can be transaction managers, resource manager, or clients. In both Microsoft Windows NT 4. 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. 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.
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. Click Start , click Run , type regedit, and then click OK. Click Start , click Run , type cmd, and then click OK. To do this, click Start , click Run , type dcomcnfg. For more information, click the following article number to view the article in the Microsoft Knowledge Base:. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
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, visit the following Microsoft Web site:. If you do not see your language, it is because a hotfix is not available for that language. For more information about how to obtain a Windows 7 or Windows Server R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:. The global 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 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. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
0コメント