Re: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.

I just noticed that your error message is "...DB provider 'SQLOLEDB' was unable to begin a distributed transaction.". That makes it sound like you are using
JDBC to run a query against a linked server that uses our SQLOLEDB provider.

I would suggest narrowing down the troubleshooting and trying your query through Query Analyzer. If the error reproduces in Query Analyzer, then it is not
related to the JDBC driver. If it doesn't reproduce, then I go back to my first set of questions.

Evan
--------------------
X-Tomcat-ID: 441702354
References: <1157704482.677667.289820@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1157726270.569774.104610@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: evanba@xxxxxxxxxxxxxxxxxxxx (Evan T. Basalik (MSFT))
Organization: Microsoft
Date: Tue, 12 Sep 2006 18:15:53 GMT
Subject: Re: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The operation could not be performed because the OLE
DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
Message-ID: <syUOEep1GHA.4464@xxxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.sqlserver.jdbcdriver
Lines: 75
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.jdbcdriver:8074
NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122

Which version of SP of SQL Server 2000 are you using? Also, which version of the SQL Server 2000 driver are you using? Are you able to reproduce the
problem outside of WebSphere?

Evan
--------------------
From: "joeNOSPAM@xxxxxxx" <joe.weinstein@xxxxxxxxx>
Newsgroups: microsoft.public.sqlserver.jdbcdriver
Subject: Re: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The operation could not be performed because the OLE
DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
Date: 8 Sep 2006 07:37:50 -0700
Organization: http://groups.google.com
Lines: 24
Message-ID: <1157726270.569774.104610@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <1157704482.677667.289820@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 75.18.188.191
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1157726275 32741 127.0.0.1 (8 Sep 2006 14:37:55 GMT)
X-Complaints-To: groups-abuse@xxxxxxxxxx
NNTP-Posting-Date: Fri, 8 Sep 2006 14:37:55 +0000 (UTC)
In-Reply-To: <1157704482.677667.289820@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@xxxxxxxxxx
Injection-Info: p79g2000cwp.googlegroups.com; posting-host=75.18.188.191;
posting-account=ARdH_Q0AAAAQPpQQrDWWzZVdIRw6poO7
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!newsfeed.cw.net!cw.net!news-FFM2.ecrc.de!
newsfeed.gamma.ru!
Gamma.RU!postnews.google.com!p79g2000cwp.googlegroups.com!not-for-mail
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.jdbcdriver:8070
X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver


qumar hussain wrote:
Hello All,

I am facing following issue:
The application flow is:

Application[ on BEA Weblogic8.1SP3]-------[create connection using
connection pool]-----> MS SQL Data base[ on windows 2003]-------[fetch
some data, using the same connection pool]------> MS SQL Data Base[On
Windows 2000].
I get following exception:

SQLException: SQLState(HY000) vendor code(7391)
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
JDBC][SQLServer]The operation could not be performed because the OLE DB
provider 'SQLOLEDB' was unable to begin a distributed transaction.

Also post this error message to the comp.databases.ms-sqlserver group
because the message does come from the DBMS and may not have
anything to do with the JDBC driver...

Joe Weinstein at BEA Systems




--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.




--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

.

Relevant Pages

  • Re: Paging - ADO.NET 2.0
    ... I was under the impression that additional information was sent to server ... from the provider when such a query is made. ... Thus allowing the database engine server-side to move the cursor to whatever ...
    (microsoft.public.dotnet.framework.adonet)
  • Error in IE when running ASP Page.
    ... an ASP page. ... oConn.Open "Ads Provider" ... ' Next we will build the LDAP query that will be used to retrieve the ... ' We will specify which server we want to run the query against, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Server: Msg 7399
    ... linked server, but when I query them the below error occurs. ... server works fine on my development server. ... OLE DB provider 'MSDAORA' reported an error. ...
    (microsoft.public.sqlserver.connect)
  • Distributed query does not work between 64bit and 32bit servers
    ... OLE DB provider 'SQLOLEDB' reported an error. ... supplied with the ODBC setup disk for the SQL Server driver). ...
    (microsoft.public.sqlserver.odbc)
  • Re: Linked servers OLEDB Error
    ... I run this statement against the linked server and it still fails with error: ... OLE DB provider 'SQLOLEDB' reported an error. ... >> happens.When quering the same table with no image column works fine. ...
    (microsoft.public.data.oledb)