linked server from SQL2000/WIN2003 to SQL2000/WIN2000

Hi NG,
I have a problem with distributed transactions between 2 SQL2000-Servers.
2 SQL2000-Server (details see below), one runs at Win2000 as named instance,
the other at Win2003 as default, both in the same domain controlled by a
Win2000-Server
=> distributed transaction works fine in both directions in
4-Part-Naming-Convention, including UPDATE and INSERT.
I didn't change anything in any way on these 2 Servers. The only thing to
mention is that the Sysads changed the DC-Server from Win2000 to Win2003.
Since this upgrade I get the following error (in both directions):
SQL-Error 7391 [blabla...] [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a]
The SQL:
UPDATE localtbl
SET field = 1
FROM localtbl INNER JOIN remotesrv.remotedb.dbo.remotetbl rtbl ON rtbl.fk_id
= localtbl.id)
But I have no problems with the following SELECT:
SELECT *
FROM localtbl INNER JOIN remotesrv.remotedb.dbo.remotetbl rtbl ON
localtbl.id = rtbl.fk_id)
I tested the same sqls successfully between the Win2000-SQL2000 from above
and another Win2000-SQLServer2000.
I executed INSCAT.SQL on the Win2000-System with no effect. On Win2003 I
can't do this yet because it is a production server. I may do so on weekend.
Concerning my DTs, my special need is Win2003 as the leading Server.
Here the results from @.@.version and the MDAC-Version from the registry:
Win2003
MDAC: 2,80,1022,0
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: )
Win2000
MDAC: 2,71,9040,2
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack
3)
Is there anybody with some hints?
Thanks a lot
Patrick
HI
Verify in Add or Remove Programs-->Windows Comonents-->Application Server--> Details
The Enable network DTC access must installed. (Not default!)
JBandi
|||Hi
"Andras Jakus" <andras.jakus@.vodafone.hu> schrieb im Newsbeitrag
news:C2B10F53-781A-4360-93BF-689532E32469@.microsoft.com...
> HI
> Verify in Add or Remove Programs-->Windows Comonents-->Application
Server--> Details
> The Enable network DTC access must installed. (Not default!)
> JBandi
it is installed, on both Server.
As described before everything worked fine just to the moment when the
DC-Server get an upgrade to Win2003.
|||Hello NG,
I solved the problem myself.
The win2003-server had a problem with the changed/upgraded domain
controller.
Detaching the server from the domain and re-attaching it to the domain with
deleting the computeraccount in ADS solved my problem!
However, the win2003-server didn't recognize the DC-Change "fully",
something got wrong and this caused the described problems with distributed
transaction. The sysads can't explain this behavior, nor do I.
You will mention by the way i describe this "solution" that i doesn't really
understand it.
I don't know which of those things like authentification, trusting,
locator-service etc. has what influence on the SQLOLEDB provider or the
MSDTC.
I hope there is anybody out there with a brief explanation concerning the
function of linked server / MSDTC / Network!? That would be great!
Best regards
Patrick
"Patrick Haubold" <phaubold@.zeb.de> wrote in
news:c49r3k$2geour$1@.ID-152493.news.uni-berlin.de...
> Hi NG,
> I have a problem with distributed transactions between 2 SQL2000-Servers.
> 2 SQL2000-Server (details see below), one runs at Win2000 as named
instance,
> the other at Win2003 as default, both in the same domain controlled by a
> Win2000-Server
> => distributed transaction works fine in both directions in
> 4-Part-Naming-Convention, including UPDATE and INSERT.
> I didn't change anything in any way on these 2 Servers. The only thing to
> mention is that the Sysads changed the DC-Server from Win2000 to Win2003.
> Since this upgrade I get the following error (in both directions):
> SQL-Error 7391 [blabla...] [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a]
> The SQL:
> UPDATE localtbl
> SET field = 1
> FROM localtbl INNER JOIN remotesrv.remotedb.dbo.remotetbl rtbl ON
rtbl.fk_id
> = localtbl.id)
> But I have no problems with the following SELECT:
> SELECT *
> FROM localtbl INNER JOIN remotesrv.remotedb.dbo.remotetbl rtbl ON
> localtbl.id = rtbl.fk_id)
> I tested the same sqls successfully between the Win2000-SQL2000 from above
> and another Win2000-SQLServer2000.
> I executed INSCAT.SQL on the Win2000-System with no effect. On Win2003 I
> can't do this yet because it is a production server. I may do so on
weekend.
> Concerning my DTs, my special need is Win2003 as the leading Server.
> Here the results from @.@.version and the MDAC-Version from the registry:
> Win2003
> MDAC: 2,80,1022,0
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: )
> Win2000
> MDAC: 2,71,9040,2
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack
> 3)
> Is there anybody with some hints?
> Thanks a lot
> Patrick
>