MSDTC and Win2K3

We have Windows 2003 OS and SQL Server 2000. We are following the following
procedure, as it is an alternate of executing a distributed transaction.
Whenever we are tying to execute the following code
begin distributed transaction
SELECT COUNT(*) FROM OPENDATASOURCE('SQLOLEDB','Data Source=
serverip;UserID=username;Password=pwd' ).AACS.dbo.edbdata
commit tran
OR
begin distributed transaction
SELECT COUNT(*) FROM OPENDATASOURCE('SQLOLEDB','Data Source=
serverip;UserID=username;Password=pwd' ).MFDATA.dbo.tbl_login
rollback
In case we are trying to execute the similar code from any other server, it
works properly but in case of our test server we receive the following error
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
We have tried using the settings given by microsoft but it did not work.Hi
Did you check out:
http://msdn.microsoft.com/library/d...ec72e00fc01.asp
and http://support.microsoft.com/kb/827805 ?
John
"Sandeep Gupta" wrote:

> We have Windows 2003 OS and SQL Server 2000. We are following the followin
g
> procedure, as it is an alternate of executing a distributed transaction.
> Whenever we are tying to execute the following code
> begin distributed transaction
> SELECT COUNT(*) FROM OPENDATASOURCE('SQLOLEDB','Data Source=
> serverip;UserID=username;Password=pwd' ).AACS.dbo.edbdata
> commit tran
> OR
> begin distributed transaction
> SELECT COUNT(*) FROM OPENDATASOURCE('SQLOLEDB','Data Source=
> serverip;UserID=username;Password=pwd' ).MFDATA.dbo.tbl_login
> rollback
>
> In case we are trying to execute the similar code from any other server, i
t
> works properly but in case of our test server we receive the following err
or
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider 'SQLOLEDB
'
> was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in th
e
> specified transaction coordinator. ]
> We have tried using the settings given by microsoft but it did not work.|||Hi John,
We have checked and tried the same but it is still not working.
Regards,
Sandeep Gupta.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Did you check out:
> http://msdn.microsoft.com/library/d...ec72e00fc01.asp
> and http://support.microsoft.com/kb/827805 ?
> John
>
> "Sandeep Gupta" wrote:
>|||Hi
I assume this select statement works without the begin distributed
transaction? Are there any other messages in the SQL Server log file or
Windows event file? Have you tried creating a linked server instead?
John
"Sandeep Gupta" wrote:
[vbcol=seagreen]
> Hi John,
> We have checked and tried the same but it is still not working.
> Regards,
> Sandeep Gupta.
> "John Bell" wrote:
>|||Hi John,
We are able to link the SQL Server through linked server but we do not have
permissions to view logs and windows event file.
Regards,
Sandeep Gupta.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> I assume this select statement works without the begin distributed
> transaction? Are there any other messages in the SQL Server log file or
> Windows event file? Have you tried creating a linked server instead?
> John
> "Sandeep Gupta" wrote:
>|||Hi
Do you still get an error when using 4 part names rather than
OPENDATASOURCE? If you do not explicitly begin and end the transactions does
it work? Have you tried removing and reinstalling MSDTC?
John
"Sandeep Gupta" wrote:
[vbcol=seagreen]
> Hi John,
> We are able to link the SQL Server through linked server but we do not hav
e
> permissions to view logs and windows event file.
> Regards,
> Sandeep Gupta.
> "John Bell" wrote:
>|||We had the same issue and found this KB article:
http://support.microsoft.com/kb/873160
This one is geared toward XP & XP Tablet, but the workaround in the KB
"fixed" our Win2003 development server after sp1 was installed (this came up
AFTER we applied sp1). Specifically it was section 2 in the workaround that
allowed it to work.
"Sandeep Gupta" <SandeepGupta@.discussions.microsoft.com> wrote in message
news:A4A64974-913C-4733-A4CD-422BC74F0005@.microsoft.com...[vbcol=seagreen]
> Hi John,
> We have checked and tried the same but it is still not working.
> Regards,
> Sandeep Gupta.
> "John Bell" wrote:
>