MS DTC에 오루가 있어서 COM+등등의 서비스들을 사용하지 못했었습니다. 며칠을 미루다 검색해 보니 아래의 내용이 있더군요. 실행 계정만 바꾸니 바로 됩니다. 왜 계정이 로칼 계정으로 되어 있었는지 모르겠습니다. 따로 변경한 적은 없는 것 같은데...
MQ관련해서 테스트 할것이 있었는데 이제 집에서도 작업할수 있을것 같네요.
MSDTC must run under NT AUTHORITYNetworkService account
Starting with Windows XP and continuing with Windows Server 2003, the account under which MSDTC service runs must be "NT AUTHORITYNetworkService" (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cossdk/htm/pgdtc_admin_7gkz.asp).
If you change the account to something else than NetworkService, your distributed transactions will fail because MSDTC will not be able to do mutual authentication with the other parties (transaction managers, resource managers, clients) involved in the transaction. In some cases, even the local transactions will fail.
If in NT4 or Windows 2000, you used to change the default MSDTC account to a domain account so that MSDTC can use Windows authentication when performing recovery with XA databases like Oracle, you can't do it anymore on XP and 2003 (at least not in a secure way). Instead you need to give to the NetworkService account from the machine where MSDTC is running, the permissions and roles needed to perform XA recovery on the XA database. The exact method of doing this is specific to each database but the simple story is that you need to add the "machine account" of the machine where MSDTC is running to the list of users that can do recovery on the XA database. Also, take a look at http://weblogs.asp.net/florinlazar/archive/2003/12/04/41370.aspx for more troubleshootings on MSDTC and XA.
posted on Friday, January 02, 2004 3:02 PM by florinlazar
Post a Comment ::
