navipartner
asked on
SQL linked server error
Hi,
I am using a linked server from a MS SQL Server 2000 server to a MS SQL Server 2005 server.
Now, I try to create a view through Enterprise Manager with the simple command:
SELECT * FROM LinkedServerName.DBName.Ow
This works when I run it in the "New View" window (with the red exclamation mark), but as soon as I save the view, this error occurs:
ODCB 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 specified transaction coordinator. ]
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoi JoinTransaction returned 0x8004d00a].
Can anyone enlighten me on this subject?
Thank you!
I am using a linked server from a MS SQL Server 2000 server to a MS SQL Server 2005 server.
Now, I try to create a view through Enterprise Manager with the simple command:
SELECT * FROM LinkedServerName.DBName.Ow
This works when I run it in the "New View" window (with the red exclamation mark), but as soon as I save the view, this error occurs:
ODCB 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 specified transaction coordinator. ]
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoi JoinTransaction returned 0x8004d00a].
Can anyone enlighten me on this subject?
Thank you!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check the Component Service Settings if you are using WINDOWS 2003 and also if SQL2005 has service pack 1 Atleast. this should solve yourproblem as i has the same error earlier.
Is this fixed?
If not, I wonder if the SQL 2000 OLEDB provider is compatible with 2005? You might try and link the server with the SQL Server ODBC driver instead.
If not, I wonder if the SQL 2000 OLEDB provider is compatible with 2005? You might try and link the server with the SQL Server ODBC driver instead.
ASKER
Hi,
Sorry for the late answer but I have been very busy the last few days.
Thank you very much for all your input. Otanas solution worked perfectly and for twoboats I can now conclude that 2000 is compatible with 2005 (or maybe the other way around, I do not know, but it works :-)
Thank you again.
Best regards!
Sorry for the late answer but I have been very busy the last few days.
Thank you very much for all your input. Otanas solution worked perfectly and for twoboats I can now conclude that 2000 is compatible with 2005 (or maybe the other way around, I do not know, but it works :-)
Thank you again.
Best regards!
Otana: Thanks
Previously, I search google and there has so many solutions -
Firewall - MS DTC etc..
But your solution is very simple and good
It work!
Previously, I search google and there has so many solutions -
Firewall - MS DTC etc..
But your solution is very simple and good
It work!