This post originated from an RSS feed registered with .NET Buzz by Sam Gentile. Original Post: MSDTC must run under NT AUTHORITY\NetworkService account Feed Title: Sam Gentile's Blog Feed URL: http://samgentile.com/blog/Rss.aspx Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More! Latest .NET Buzz Posts Latest .NET Buzz Posts by Sam Gentile Latest Posts From Sam Gentile's Blog

Florin seems to have an answer to our woes expressed here and here. As he explains, XP and Win2K3 have changed such that the MSDTC service must under the  "NT AUTHORITY\NetworkService" account or transactions will fail to enlist asd we are seeing. However, we are already doing that of course on our Win2K3 boxes.

He goes on to say “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” and “The exact method of doing this is specific to each database.” There's the rub. We can't get anyone from Oracle or Microsoft to tell us what that should be for Oracle 9i and distributed transactions.  It seems like we have to do what we did in the old days of MTS and COM+ and create an account like mtsys as the Oracle docs say “Create the Microsoft Transaction Server administrative user account (the default username is mtssys).“

BTW, in his explanation, he says “Windows XP and continuing with Windows Server 2003.” One of our concerns with the explanation is that it works perfectly under XP.