error 7391 in distributed transaction

I have a procedure running locally on my server A. This procedure does an
insert into a table after getting a return value from a select done on
another server say B . Server B is set up as linked server on server A. th
error i get shows as
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. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
Has anyone seen this before? Is there any solution to this or any setting
that needs to be changed to get this working? any help will be greatly
appreciated.
TIA
Message posted via http://www.webservertalk.comFor distributed transaction you need to have a Primary key on updated table.
So pLease add primary key to resolve your issue. Please let me know if
doesn't work.
Regards,
Jagan Mohan
MCDBA
"ishaan99 via webservertalk.com" wrote:

> I have a procedure running locally on my server A. This procedure does an
> insert into a table after getting a return value from a select done on
> another server say B . Server B is set up as linked server on server A. th
> error i get shows as
> 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. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> Has anyone seen this before? Is there any solution to this or any setting
> that needs to be changed to get this working? any help will be greatly
> appreciated.
> TIA
> --
> Message posted via http://www.webservertalk.com
>|||I've had this same error, mine only happened during times when transactions
were high on the system, I think there is a setting to increase the number o
f
concurrent distributed transactions, don't know what else you could do, I
know it has to do with MSDTC.
"ishaan99 via webservertalk.com" wrote:

> I have a procedure running locally on my server A. This procedure does an
> insert into a table after getting a return value from a select done on
> another server say B . Server B is set up as linked server on server A. th
> error i get shows as
> 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. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> Has anyone seen this before? Is there any solution to this or any setting
> that needs to be changed to get this working? any help will be greatly
> appreciated.
> TIA
> --
> Message posted via http://www.webservertalk.com
>sql

Error 53

I have SQL Server 8 running locally on my networked XP pc. I would like to have users connect to the database there through the network. Each time they try to connect, the following error occures:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection open(CreateFile()).
Connection failed:
SQLState:'08001'
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
When a user tries to connect, are they to use my IP address, my computer name, my SQL Server Group name? I think I've tried all ways, but they can't connect (myself included).
</scratching head>
tia,
JMorrell
Could be an error with authentication. Make sure that they are using named
pipes protocol and are authenticated to your PC with an ID that has
permissions for SQL server. Try having them map a drive first with this ID.
"JMorrell" wrote:

> I have SQL Server 8 running locally on my networked XP pc. I would like to have users connect to the database there through the network. Each time they try to connect, the following error occures:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection open(CreateFile()).
> Connection failed:
> SQLState:'08001'
> SQL Server Error: 6
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
> When a user tries to connect, are they to use my IP address, my computer name, my SQL Server Group name? I think I've tried all ways, but they can't connect (myself included).
> </scratching head>
> tia,
> --
> JMorrell

Error 53

I have SQL Server 8 running locally on my networked XP pc. I would like to
have users connect to the database there through the network. Each time the
y try to connect, the following error occures:
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection open(
CreateFile()).
Connection failed:
SQLState:'08001'
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server do
es not exist or access denied.
When a user tries to connect, are they to use my IP address, my computer nam
e, my SQL Server Group name? I think I've tried all ways, but they can't co
nnect (myself included).
</scratching head>
tia,
--
JMorrellCould be an error with authentication. Make sure that they are using named
pipes protocol and are authenticated to your PC with an ID that has
permissions for SQL server. Try having them map a drive first with this ID.
"JMorrell" wrote:

> I have SQL Server 8 running locally on my networked XP pc. I would like t
o have users connect to the database there through the network. Each time t
hey try to connect, the following error occures:
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection ope
n(CreateFile()).
> Connection failed:
> SQLState:'08001'
> SQL Server Error: 6
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server
does not exist or access denied.
> When a user tries to connect, are they to use my IP address, my computer n
ame, my SQL Server Group name? I think I've tried all ways, but they can't
connect (myself included).
> </scratching head>
> tia,
> --
> JMorrell

error 40. Get the error locally, but not remotely!

I've got a windows 2003 server running sql server 2005. When I run a web sit
e
on a desktop machine, there is no problem connecting to the database.
But, when I run the same web site with the same connection string on the
2003 server, I get the following error:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
Obviously remote connections and tcp are enabled. My guess is that there is
something stopping IIS from connecting to the databse. The firewall is
disabled (not that it should interfere with local activities anyway).
I've been struggling with this one for a couple days. Any help would be
greatly appreciated.The problem seemed to have fixed itself after I upgraded to Service Pack 1
for SQL 2005. I don't know if that was the problem.
"Trevor Murphy" wrote:

> I've got a windows 2003 server running sql server 2005. When I run a web s
ite
> on a desktop machine, there is no problem connecting to the database.
> But, when I run the same web site with the same connection string on the
> 2003 server, I get the following error:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: Named Pipes Provider, error: 40 - Could not open a connection t
o
> SQL Server)
> Obviously remote connections and tcp are enabled. My guess is that there i
s
> something stopping IIS from connecting to the databse. The firewall is
> disabled (not that it should interfere with local activities anyway).
> I've been struggling with this one for a couple days. Any help would be
> greatly appreciated.

error 40. Get the error locally, but not remotely!

I've got a windows 2003 server running sql server 2005. When I run a web site
on a desktop machine, there is no problem connecting to the database.
But, when I run the same web site with the same connection string on the
2003 server, I get the following error:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
Obviously remote connections and tcp are enabled. My guess is that there is
something stopping IIS from connecting to the databse. The firewall is
disabled (not that it should interfere with local activities anyway).
I've been struggling with this one for a couple days. Any help would be
greatly appreciated.
The problem seemed to have fixed itself after I upgraded to Service Pack 1
for SQL 2005. I don't know if that was the problem.
"Trevor Murphy" wrote:

> I've got a windows 2003 server running sql server 2005. When I run a web site
> on a desktop machine, there is no problem connecting to the database.
> But, when I run the same web site with the same connection string on the
> 2003 server, I get the following error:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: Named Pipes Provider, error: 40 - Could not open a connection to
> SQL Server)
> Obviously remote connections and tcp are enabled. My guess is that there is
> something stopping IIS from connecting to the databse. The firewall is
> disabled (not that it should interfere with local activities anyway).
> I've been struggling with this one for a couple days. Any help would be
> greatly appreciated.