Distributed Transactions Co-ordinator

We are running MS SQL Server 2000, on Windows 2003, and the environment is
locked down to the nth degree.
We are running Distributed Transactions and Java, and are experiencing
problems. We are being told that the reason is because we have COM+
disabled. And that we are likely to experience many other inexplainable
problems if we don't enable it.
The build we have is a standard build, and we have other SQL Server
implementations running with no issue.
Is COM+ required to run SQL Server, Distributed Transactions or allow
connectivitiy in to the database through JAVA?
Thanks
BevNot COM+, you just need MSDTC a very small piece; so you do need to have:
1) The MSDTC service running (NET START MSDTC)
2) The MSDTC service enable for network transactions, which by default on
Windows Server 2003 is turned off, see
http://support.microsoft.com/default.aspx?scid=kb;en-us;817064 "How to
enable network DTC access in Windows Server 2003", you can set this with
MMC, start mmc %windir%\system32\com\comexp.msc
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2004 All rights reserved.
"Beverley" <Beverley@.discussions.microsoft.com> wrote in message
news:0D039C49-8F62-44D4-A62B-4EE31BE43862@.microsoft.com...
> We are running MS SQL Server 2000, on Windows 2003, and the environment is
> locked down to the nth degree.
> We are running Distributed Transactions and Java, and are experiencing
> problems. We are being told that the reason is because we have COM+
> disabled. And that we are likely to experience many other inexplainable
> problems if we don't enable it.
> The build we have is a standard build, and we have other SQL Server
> implementations running with no issue.
> Is COM+ required to run SQL Server, Distributed Transactions or allow
> connectivitiy in to the database through JAVA?
> Thanks
> Bev