ODBC Connection problem with SQL Native Client driver with CR 11

I am having an issue connecting my crystal reports to an ODBC connection that uses the SQL Native Client driver (Version 2005.90.2047.00). My reports work fine when using the SQL Server driver (Version 2000.85.3006.00). The ODBC connection is setup to use Integrated Windows Authentication and is defaulted to go to the correct database. When I test the ODBC connection in the 'ODBC Data Source Adminstrator' it connects fine.
The reports are trying to connect to stored procedures on a SQL Server 2005 database. I can log onto the ODBC connection in CR X1. When I try to set the Datasource connection for one of my reports to the ODBC connection I created, I get the following error:
'Some tables could not be replaced, as no match was found in the new data source. Please specify the table required for any unmodified tables.'
When I drill down to the SP and try to update the datasource location of the SP directly I get the following errors:
'Data Object cannot be opened/accessed'
and
'Unknown Database Connector Error'
As I said, I don't have any problems when using the SQL Server 2000 driver. One other thing to mention, when I initially connect to the ODBC connection in CR X1 with the SQL Native Client driver, it asks for a username and password. I leave these blank since I'm using Windows Authentication.
Any advice would be appreciated.
System:
Windows XP
Service Pack 3
Crystal Reports XI:
Product Version 11.0.0.1282

Hi Jeff,
I just tried to create a new report using the native driver and there is no option to use Trusted Authentication. This would be why it's failing.
I don't believe we fully supported Native driver in Cr XI. Try downloading CR Xi R2 and install SP6 from this info:
Go to this link: http://www.sdn.sap.com/irj/boc and download the trial version of CR XI R2 and use your XI keycode, then apply the patches which you can get to by clicking on the BusinessObjects tab above, then Downloads.
Direct link to the Trial version: http://www.sap.com/solutions/sapbusinessobjects/sme/freetrials/index.epx
I tested it in R2 and the Trusted Authentication option is there so your reports should work.
Thank you
Don

Similar Messages

Error updating data source from SQL Server ODBC into SQL Native Client 10.0

I am converting Crystal 8.5 reports into Crystal XI release 2. The data source was ODBC using SQL Server 2000 and pointing to a stored procedure. In the new server the data source has to be ODBC again, but it uses the SQL Native Client 10.0 Driver, because the new server is SQL Server 2008. I have copied the same old stored procedure on the new server and it works fine as a data source to a brand new Crystal XI report. But when I am opening an existing 8.5 version crystal report and updating the data source to the new location I get the error message "Some tables could not be replaced, as no match was found in the new data source".
I thought I could tackle this error by creating a temporary data source using the standard ODBC SQL Driver linked to the SQL 2008 Server instead of the SQL Native Client 10 ODBC. So I first updated the crystal data source to link to this temp ODBC using SQL Driver and it worked fine. But after that, when I try to update the data source to link to the SQL Native Client 10 ODBC, I get the same error again.
So I guess that the problem is not the new server itself, but the switch between SQL Server ODBC and SQL Native Client 10 ODBC.
Does anyone know what's going on with this SQL Native Client 10 in updating crystal report data sources?

CR XI does not support that driver. Try selecting the Native driver or upgrade to CR XI R2 for free and use SP4, 5 and 6 and then FP 6.4 or upgrade to CR 2008 and SP 3 and Fix Pack 3.3
Thank you
Don

SQL Native Client 11 (ODBC) - SQL Server 2012 - MS DTC - Transaction Promotion

Hi and thanks for any help in advance,
Does the SQL Native Client (ODBC) resource manager support automatic transaction promotion? I don't see anyway to get this to work using the ODBC API or the MS DTC API.
I have a connection that enlisted into a local transaction (setting auto commit to false). Then I get another call that is part of the same transaction but to a different server. So I try to enlist the first connection handle into a new distributed
transaction but that fails with the error code 25000 - which seems to indicate that promotion is not possible. Am I missing some other API call?
Any help appreciated.

For .Net yes. If you are using SQL Native client and ODBC - the Enlist keyword is not supported in the connection string. For .Net System.Transaction takes care of doing the promotion for you if required. What I am asking is how that is
achieved using SQL Native client API and the MS DTC using C++?

Report fails on CE usin stored proc as data source and Native Client driver

Iu2019m using Crystal Reports 10. I have a report with a stored procedure as data source. All my other reports using views as data source. Weu2019re upgrading db from SQL Server 2000 to 2008 and start using Native Client driver.
Thereu2019s no problem to generate this report from .rpt on my local PC. But got the following error message when generate from Crystal Enterprise:
Error Message: The table could not be found. File D:\Program Files\Crystal Decisions\Enterprise 10\Data\procSched\......reportjobserver\~tmp12c06c5641c4d50.rpt.
It looks like sth related to Native Client driver. It works if I change to use old native driver in DSN on CE server.
Any ideas/advises? Appreciated to your help!

Hello,
CR 10 does not support the MS SQL Native Driver, if you want to use OLE DB then use the MS OLE DB Provider for SQL Server up to SQL 2005. SQL 2008 does not support the MDAC version so you have to install the SQL 2008 Client tools to use the SQL Native 10 driver. CR 10 does not support that Native 10 Driver.
See this MS Kbase: http://msdn.microsoft.com/en-us/library/ms131035.aspx
Convert back to the old driver for 2005 and then use ODBC if using SQL 2008, it should work...
Don

Connection problem to SQL Server 2000

I have a local installation of MSSQL 2000, that doesn't seem to use any port as a listener. when checking the log I can see that even though I said it should use a TCP/IP connection, it says it uses a shared memory (I guess the reason is that the installation I did is not for a server but only for running on my machine).
How can I define through BPEL the connection to this kind of MSSQL? can I define a connection that will run on the named pipes of the SQL server?
Thanks in advance.

Hi Ophir,
I tried this exercise of connecting to SQL Server myself via jdbc and I wrote a new section for the developer's guide based on it. It was not completely painless. For your specific question the SQL Server Express install sets up connectivity by either 'shared memory' or 'named pipes' by default, but you can easily add a TCP/IP listener (for me via the SQL Server Configuration Manager), which is mandatory for jdbc access. Please see the section 'TCP Port' below.
Not sure if you have it, I am cutting and pasting from the 10.1.2.0.2 DBAdapter guide:
(Oracle® Application Server Adapters for Files, FTP, Databases, and Enterprise Messaging User's Guide
10g Release 2 (10.1.2))
Using a Microsoft SQL Server Database
When using a Microsoft SQL Server database, follow the database connection steps in Chapter4, "Design Time" and use the following information:
MS JDBC Driver
URL: jdbc:microsoft:sqlserver://localhost\NAME:1433;SelectMethod=cursor;databasename=???
Driver Class: com.microsoft.jdbc.sqlserver.SQLServerDriver
Driver Jar: .\SQLServer2000\msbase.jar, msutil.jar, mssqlserver.jar
DataDirect Driver
URL: jdbc:oracle:sqlserver://localhost
Driver Class: com.oracle.ias.jdbc.sqlserver.SQLServerDriver
Driver Jar: .\DataDirect\YMbase.jar, YMoc4j.jar, YMutil.jar, YMsqlserver.jar
Note the following when connecting to a SQL Server database:
User name and password
o
SQL Server 2005 installs with Windows authentication as the default. Therefore, you do not log in with a user name and password; rather, your Windows user account either has privilege or does not. JDBC requires you to provide a user name and password.
According to support.microsoft.com, "Microsoft SQL Server 2000 driver for JDBC does not support connecting by using Windows NT authentication." See
http://support.microsoft.com/default.aspx?scid=kb;en-us;313100
However, the DataDirect driver specification states that it does.
If you use your Windows user name and password, you may see something like the following:
[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Login failed for user
'DOMAIN\USER'. The user is not associated with a trusted SQL Server
connection.[Microsoft][SQLServer 2000 Driver for JDBC]
An error occured while attempting to log onto the database.
You must select mixed mode authentication on a clean installation.
o
On a Microsoft SQL Server 2000 Express Edition installation, the system username is su and the password is whatever you provide.
Connect string
From the sqlcmd login, you can infer your connect string, as in the following examples:
Example 1:
sqlcmd
1>
jdbc:microsoft:sqlserver://localhost:1433
Example 2:
sqlcmd -S user.mycompany.com\SQLExpress
1>
jdbc:microsoft:sqlserver://user.mycompany.com\SQLExpress:1433
Example 3:
sqlcmd -S user.mycompany.com\SQLExpress -d master
1>
jdbc:microsoft:sqlserver://user.mycompany.com\SQLExpress:1433;databasename=
master
A full URL is as follows:
jdbc:microsoft:sqlserver://serverName[\instanceName]:tcpPort[;SelectMethod=cursor][;databasename=databaseName]
Database name
If you must explicitly supply the database name, but do not know it, go to
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
If you see a file named master.mdf, then one of the database names is master.
TCP port
Make sure that SQL Server Browser is running and that your SQL Server service has TCP/IP enabled and is listening on static port 1433. Disable dynamic ports. In SQL Native Client Configuration/Client Protocols, make sure that TCP/IP is enabled and that the default port is 1433.
JDBC drivers
You must download the JDBC drivers separately. From www.microsoft.com, click Downloads and search on jdbc. You can also try using the DataDirect driver.
Thanks
Steve

MS-SQL Server 2005 SP1 vs MS-SQL Native Client 2008 or 2012

Hello,
I woud like to know if it's possible to use on a computer Windows Seven, the MS-SQL Native Client 2008 or 2012, and connect it on a MS-SQL Server 2005 (under Windows 2003 enterprise).
Regards,

Hello,
Yes, the SQL Server Native client is backward compatible, means you can use Client 2008 or higher to connect to a SQL Server 2005.
With some limitations the client is also forward compatible, means you can use a client 2005 to connect to SQL Server 2008 and higher; but the client isn't aware of new server features.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Odbc connectivity problem

Hi all,
when i am installing ECC 5.0 i got below error.
"odbc connectivity problem, error executing sql command"
what may be the reason.
plz give me some solution.
vinnu.

Hi Vinay
Check if your database is up and running.

How to set default SQL Native Client in SAP BO?

Hello,
is there any possibility to set default SQL Native Client? We must have two SQL NC installed unfortunately, 2005 and 2008. Issue is, that SAP BO chooses the 2008 by default and user must manually switch to 2005 to see pre-defined instances. Is there any way how to select SQL NC 2005 as default? Many thanks
Best regards,
Joe

Hi,
Try this procedures.
1. Dont open your SBO program.
2. Goto C:\Program Files\SAP\SAP Business One\Conf\ folder
3. Delete file b1-local-machine.xml
4. Log to SBO program.
5. Apply all necessary authentication then select SQL_2008 then log.
6. After logging exit to SBO program.
7. Re-log again if SQL_2008 is already in default.
Thanks.
Clint

Error 1603 installing microsoft sql native client

error 1603 installing microsoft sql native client
Sagar Chavan

have a look at this link
http://support.microsoft.com/kb/834484
Satheesh
My Blog |
How to ask questions in technical forum

Problem in SQL Server 2000 Driver for Java Database Connectivity

Hi,
I have problem with MS SQL 2000 JDBC driver. I am using Type-4 driver for my application. I can able to connect through DSN. If I use Type-4 Driver to connect database means it gives the following exception.
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
     at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
     at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
     at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
     at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
     at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
     at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
     at java.sql.DriverManager.getConnection(Unknown Source)
     at java.sql.DriverManager.getConnection(Unknown Source)
     at test.TestDB.main(TestDB.java:17)
My Java Code :
String driver = "com.microsoft.jdbc.sqlserver.SQLServerDriver";
Class.forName(driver);
Connection con = DriverManager.getConnection("jdbc:microsoft:sqlserver://192.168.48.90:1433;User=sa;Password=sa;DatabaseName=GWCANADA");
Statement st = con.createStatement();
ResultSet rs = st.executeQuery("select * from emp");Do we have any other jdbc driver to connect MS SQL 2000 aprt from the Microsoft JDBC driver.
Plese help me to resolve this problem
Thanks
---Suresh

Same problem is here: http://forum.java.sun.com/thread.jspa?threadID=419214&tstart=135
Check that your server is running (telnet <hostname> 1433)
--Xapp

Visio Database Wizard fails - ODBC connection to MS SQL

When I try to create an ODBC connection in Visio's 2010's Database wizard I get the error: "Cannot set the database context information. Additional error information:ODBC Error: s1009. Database cxweba does not exist."
Note that the database name is cxwebapp_bkk. I get the same error if I connect to any database on that server, and it always truncates the name in the error message (if that is a hint to the error).
Using Visio 2013, after connecting to the database: when I select the database object I get the error message: "The selected table has only one field or contains no definition information. The Database Wizard requires a minimum of one key field
and one additional data field."
I have this problem using both SQL Server driver (6.02.9200.116384 and SQL Server Native Client 11.0 (2011.1102.2100.60).
I do not have this problem connecting to a MYSQL database with either version of Visio, nor do I have this problem when I link link to the same SQL database in a drawing and link shapes in that drawing using the "Link Data to Shapes" under the
Data tab.

Hello,
What's the version of the SQL Server instance you connect to? It seems that the Database Wizard in Visio 2010 not work well with the Microsoft SQL Server ODBC driver. Did you try to use the Generic OLEDB Provider for SQL Server?
Since the issue is more related to office Visio, please post the question in the following forum. More experts there will assist you:
Visio General Questions and Answers for IT Professionals
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

SQL 2000 ODBC CONNECTION STRING FOR SQL 2008

i have vb 6 application. Database is SQL server 2000.
my connection string is (using odbc driver),
        .ConnectionString = "Driver={SQL Server};SERVER=" & mServer & ";DATABASE=mydb;UID=" & mLogin.Username & ";pwd=" & mLogin.Password & ";"
Now i have tried this application with SQL server express 2008 R2
Can i still keep the old connection string? will there be any problem in future?
(if i have to change then have to change at so many places.....)
I can run application without any problem for now (not changed connection string to new one)
otherwise i have to use ODBC or OLEDB which are,
        .ConnectionString = "Driver={SQL Server Native Client 10.0};SERVER=" & mServer & ";DATABASE=mydb;UID=" & mLogin.Username & ";pwd=" & mLogin.Password & ";"
or
        .ConnectionString = "Provider=SQLNCLI10;SERVER=" & mServer & ";DATABASE=mydb;UID=" & mLogin.Username & ";pwd=" & mLogin.Password & ";"
if i have to change to new connection string Which one is better to use odbc or oledb.
h2007

personally I favor ODBC as it is easy to use sometime. Additionally you can check the link below:
http://social.msdn.microsoft.com/Forums/en/sqlintegrationservices/thread/19e0c306-0be4-46b5-b207-0937931d63a7
cheers!!!
Vatsa
www.objectiveprogramming.com

SWING GUI blockes when doing a DB action with microsoft nativ JDBC driver

hi,
in a bigger project i have the problem that if i perform a DB action the GUI is blocked. It does not matter if i do the DB Action in invokeLater or
in a SwingWorker or in a new Thread if i call the DB Action and i move another window over my window it is not refreshed.
normally the GUI shouln�t be blocked if i use invokeLater. maybe it
has something to do that i use the native DB driver? I am using JDK
1.4. has anyone ever encounterd the same problem?
alex
package swingtest;
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
import java.sql.*;
public class GUIProblem extends JDialog {
// this method does a simple DB call to generate some load
public void doMyDBCall()
try {
Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
Connection con = DriverManager.getConnection ("jdbc:microsoft:sqlserver://abgvdr71:1433;databasename=v52li;","sa","");
Statement question0 = con.createStatement();
ResultSet rs0=null;
rs0 = question0.executeQuery("select * from intercept_24");
boolean more=rs0.next();
while (more) {    more=rs0.next();}
catch (Exception sql)
{ sql.printStackTrace(); }
public void doItinvokeLater()
SwingUtilities.invokeLater(new Runnable(){    public void run(){
doMyDBCall();
public void doItSwingWorker()
SwingWorker worker = new SwingWorker() {
public Object construct() {
System.out.println("worker start");
doMyDBCall();
return null;
worker.start();
System.out.println("finished .....");
Object view = (Object) worker.get();
public GUIProblem (){
super((JFrame)null,"",true);
JButton button = new JButton("do it");
button.addActionListener(new ActionListener() {
public void actionPerformed(ActionEvent event)
// calls it direct -> GUI blocked
//doMyDBCall();
// with invoke later -> GUI blocked
//doItinvokeLater();
// with the swingWorker -> GUI also blocks
doItSwingWorker();
getContentPane().add(button);
setSize(200,200);
setVisible(true);
public static void main(String [] args)
{ new GUIProblem(); }
}

The invokeLater runs the Runnable in the event thread, so yes, that will block your GUI. You ALMOST got the SwingWorker right. DB call in the construct() method -- the construct() method executes outside the event thread, the finished() method executes in the event thread. The only problem is, you did a worker.get() method in your event thread (right after worker.start(0, and get() blocks until result is ready from construct() -- so, bingo, you're jammed up waiting in you event thread.

RPAS ODBC connection problem

I’m working on integration of OBIEE and RPAS, and I could use some help. Could anyone help me with a problem?
I’m trying to connect the RPAS ODBC driver from my pc to the RPAS running in a Linux Virtual Machine.
I’ve already connected that to the Management Console and, when I create an ODBC connection the Service Data Source names are presented to me (I think the connection is working). But, when I try to test the connection, I receive a message telling the connection was closed(dropped?) unexpectedly.
any ideia of whats happening?

Hi Jeff,
I just tried to create a new report using the native driver and there is no option to use Trusted Authentication. This would be why it's failing.
I don't believe we fully supported Native driver in Cr XI. Try downloading CR Xi R2 and install SP6 from this info:
Go to this link: http://www.sdn.sap.com/irj/boc and download the trial version of CR XI R2 and use your XI keycode, then apply the patches which you can get to by clicking on the BusinessObjects tab above, then Downloads.
Direct link to the Trial version: http://www.sap.com/solutions/sapbusinessobjects/sme/freetrials/index.epx
I tested it in R2 and the Trusted Authentication option is there so your reports should work.
Thank you
Don

Sql Exception on Testing Configuration with SQL Server JDBC driver for XA

I have a requirement of analyzing the behavior of SQL Server JDBC data sources for XA transactions in our application.We have been using Non-XA drivers for both Oracle and SQL Server as we had no requirement for transactions spanning across multiple databases in past.I have setup and tested the XA driver for Oracle (Oracle Driver (Thin XA) for Instance Connections 9.0.1,9.2.0,10,11) in Weblogic 11g and its working perfectly for transactions spanning across two databases.No when I am trying to configure weblogic 11g R1 for Sql server JDBC driver to support XA transactions with driver details as follows,
Server:Weblogic 11g R1
Driver Type: MS Sql Server
Database Driver :Oracle's MS SQL Server Driver(Type 4 XA) Version:7.0,2000,2005)
Database:SQL Server 2005(Single Instance)
and try to create a new data source and select "Test Configuration" and following error is thrown ,
<Mar 17, 2011 4:49:49 PM GMT+05:30> <Error> <Console> <BEA-240003> <Console encountered the following error java.sql.SQLException: [OWLS][SQLServer JDBC Driver][SQLServer]xa_open (0) returns -3
at weblogic.jdbc.sqlserverbase.BaseExceptions40.createAppropriateSQLExceptionInstance(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseExceptions40.createSQLException(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseExceptions.createException(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseExceptions.getException(Unknown Source)
at weblogic.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
at weblogic.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
at weblogic.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source)
at weblogic.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
at weblogic.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseStatement.commonTransitionToState(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseStatement.postImplExecute(Unknown Source)
at weblogic.jdbc.sqlserverbase.BasePreparedStatement.postImplExecute(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseStatement.commonExecute(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseStatement.executeUpdateInternal(Unknown Source)
at weblogic.jdbc.sqlserverbase.BasePreparedStatement.executeUpdate(Unknown Source)
at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.executeXaRpc(Unknown Source)
at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.executeXaRpc(Unknown Source)
at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.open(Unknown Source)
at weblogic.jdbcx.sqlserverbase.BaseXAConnection.init(Unknown Source)
at weblogic.jdbcx.sqlserverbase.BaseXAConnection40.init(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseClassCreatorForJDBC40.createXaConnection(Unknown Source)
at weblogic.jdbcx.sqlserverbase.BaseXADataSource.getXAConnection(Unknown Source)
at com.bea.console.utils.jdbc.JDBCUtils.testConnection(JDBCUtils.java:550)
at com.bea.console.actions.jdbc.datasources.createjdbcdatasource.CreateJDBCDataSource.testConnectionConfiguration(CreateJDBCDataSource.java:450)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870)
at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809)
at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478)
at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306)
at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336)
at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:64)
at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:184)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:50)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:58)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:87)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:261)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:686)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:106)
at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225)
at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:47)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
I followed the instruction in weblogic jdbc drivers guide to configure the JTA Transactions to support XA on SQL Server machine and weblogic server which included,
1.Copying sqljdbc.dll copied to SQL_Server_Root/bin directory from WL_HOME\server\lib.
2.Copied instjdbc.sql to sql server machine and executed the script with following output,
Changed database context to 'master'.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_open', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_open2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_close', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_close2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_start', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_start2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_end', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_end2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_prepare', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_prepare2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_commit', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_commit2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_rollback', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_rollback2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_forget', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_forget2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_recover', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_recover2', because it does not exist or you do not have permission.
creating JDBC XA procedures
instxa.sql completed successfully.
3.Verified that MSDTC service is running on both SQL Server and weblogic machines with XA Transaction enabled and DTC option enabled for both inbound and outbound connections.
4.Copied sqljdbc.jar (version 3.0 downloaded from msdn portal) to "C:\Oracle\Middleware\wlserver_10.3\server\ext\jdbc\sqlserver" directory and updated weblogic_classpth variable in commEnv.cmd file.
set WEBLOGIC_CLASSPATH=%JAVA_HOME%\lib\tools.jar;%BEA_HOME%\utils\config\10.3\config-launch.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%FEATURES_DIR%\weblogic.server.modules_10.3.2.0.jar;%WL_HOME%\server\lib\webservices.jar;%ANT_HOME%/lib/ant-all.jar;%ANT_CONTRIB%/lib/ant-contrib.jar;C:\Oracle\Middleware\wlserver_10.3\server\ext\jdbc\sqlserver\server\ext\jdbc\sqlserver\sqljdbc.jar
Can some one please provide some input on whats causing this and any other steps needs to be followed to implement XA support using SQL Server JDBC driver.

You seem to have done everything correctly and diligently. I would ask that you open
an official support case.

ODBC Connection problem with SQL Native Client driver with CR 11

Similar Messages

Maybe you are looking for