Re: SQL Server 2000 on Win 2003 and DTC
From: mikeram (mikeram_at_discussions.microsoft.com)
Date: 04/27/05
- Next message: Paul: "Inactive record"
- Previous message: Shark Bait: "Is this a security risk?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 27 Apr 2005 07:39:02 -0700
Another reach-around which I found worked from a Windows Server 2000 client
application trying to talk to a Windows Server 2003 / SQL Server 2000 machine
was: change the Security Configuration of MSDTC from Mutual Authentication
to Caller or No authentication required. That would seem to open a security
hole, so maybe more detailed instructions can come from Microsoft on how to
configure this.
-- Mike Ramsey IT Manager "Tomas" wrote: > > Finally, I found it my self. I post it here since it might > be interesting for you to know. In the release notes of > Windows XP SP2, there are a couple of lines that also > affect Windows 2003 server with MSDTC and SQL Server 2000. > > You have to reaed this to make it work in a distributed > env. with Transactions. > > http://www.microsoft.com/technet/prodtechnol/winxppro/maint > ain/sp2otech.mspx#EBAA > > You have to add the three enties in the registry > (menitioned in the article) to make it work with a Win2000 > COM+ server. > > >-----Original Message----- > >Thany you for your quick answer. I was maby to quick > >posing my question...but now I have additional > >information. > > > >When we applied the latest 10 security updates on > Win2003, > >then it stopped working. Before that everything worked > >fine on Win2003. If I now change the COM+ server > >to "point" on an SQL Server on Win 2000, the COM+ server > >work, but then again "pointing" it to the "updated" > >Win2003 server the DTC fails. When I remove the updates > >the server configuration still do not work. > > > > > >>-----Original Message----- > >>See: > >>http://support.microsoft.com/default.aspx?scid=kb;en- > >us;817065 > >>http://support.microsoft.com/default.aspx?scid=kb;en- > >us;817064 > >> > >>And if you are running a cluster also see: > >>http://support.microsoft.com/default.aspx?scid=kb;en- > >us;301600 > >> > >>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. > >> > >>"Tomas W" <anonymous@discussions.microsoft.com> wrote in > >message > >>news:283e01c4a52c$593caff0$a501280a@phx.gbl... > >>> We have an env. with a distributed COM+ application on > a > >>> Win2003 server and a SQL Server 2000 on a Win 2003 > >server, > >>> connecting through ODBC. > >>> > >>> In this env. we always get "Failed to enlist > Distributed > >>> transaction..." ODBC error, when doing a transaction in > >>> COM+. If we switch the ODBC to point towards an SQL > >Server > >>> 2000 on a Windows 200 server, everything works just > >fine. > >>> > >>> Any ideas what can be the difference between Win2000, > >and > >>> Win 2003 in this aspect? > >> > >> > >>. > >> > >. > > >
- Next message: Paul: "Inactive record"
- Previous message: Shark Bait: "Is this a security risk?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
