Distributed transaction

We had 3 SQL servers (S1, S2, S3). S1 and S3 are in the same domain. both S2
and S3 have views that link to S1. Recently we replaced S1 with S11. Now, we
can run views in S2 and S3 however we cannot modify the views in S2 or add
new views linked to S11.
Actually, we can modify the views and run them but when we tried to save the
changes, this error message will show up:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation
could not be performed because the OLE DB provider 'SQLOLEDB' was unable to
begin a distributed transaction.
[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
message: New transaction cannot enlist in the specific transaction
coordinator.]
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB
Provider 'SQLOLEDB' ITransactionJoinTransaction returned 0x8004d00a].
What should we do to fix this?
All servers run Windows 2000 and SQL 2000.
Thanks.Hello lwidjaya,
sounds like your using the EM tool for these changes, I would suggest using
query analyzer for this.
there are a number of things that might cause this issue, so you need to
know what is different configuration wise from s1 and s11, so do an inventor
of security and setup.
John Vandervliet...
"lwidjaya" wrote:
> We had 3 SQL servers (S1, S2, S3). S1 and S3 are in the same domain. both S2
> and S3 have views that link to S1. Recently we replaced S1 with S11. Now, we
> can run views in S2 and S3 however we cannot modify the views in S2 or add
> new views linked to S11.
> Actually, we can modify the views and run them but when we tried to save the
> changes, this error message will show up:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation
> could not be performed because the OLE DB provider 'SQLOLEDB' was unable to
> begin a distributed transaction.
> [Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
> message: New transaction cannot enlist in the specific transaction
> coordinator.]
> [Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB
> Provider 'SQLOLEDB' ITransactionJoinTransaction returned 0x8004d00a].
> What should we do to fix this?
> All servers run Windows 2000 and SQL 2000.
> Thanks.|||Hi John,
thanks for your reply.
Our IT guy just found out what happened. He needs to add the server name and
ip address in the hosts file in winnt folder.
Lisa
"John Vandervliet" wrote:
> Hello lwidjaya,
> sounds like your using the EM tool for these changes, I would suggest using
> query analyzer for this.
> there are a number of things that might cause this issue, so you need to
> know what is different configuration wise from s1 and s11, so do an inventor
> of security and setup.
> John Vandervliet...
> "lwidjaya" wrote:
> > We had 3 SQL servers (S1, S2, S3). S1 and S3 are in the same domain. both S2
> > and S3 have views that link to S1. Recently we replaced S1 with S11. Now, we
> > can run views in S2 and S3 however we cannot modify the views in S2 or add
> > new views linked to S11.
> > Actually, we can modify the views and run them but when we tried to save the
> > changes, this error message will show up:
> > ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The operation
> > could not be performed because the OLE DB provider 'SQLOLEDB' was unable to
> > begin a distributed transaction.
> > [Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
> > message: New transaction cannot enlist in the specific transaction
> > coordinator.]
> > [Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB
> > Provider 'SQLOLEDB' ITransactionJoinTransaction returned 0x8004d00a].
> >
> > What should we do to fix this?
> >
> > All servers run Windows 2000 and SQL 2000.
> >
> > Thanks.