Problem using production version of SQL Server 2005 JDBC drivers

A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
Regards,
Sabrina
     at ourpackage.OurMDB.onMessage(OurMDB.java:184)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
     ... 11 more
Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
     at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
     at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
     at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
     at ourpackage.OurMDB.onMessage(OurMDB.java:184)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
     at ourpackage.OurMDB.onMessage(OurMDB.java:184)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
     ... 12 more

SabrinaL wrote:
A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
Regards,
SabrinaHi. Have you done all the XA-related install for the new MS driver? (put the XA
dll in the DBMS environment etc)? Is your DBMS on a 32-bit machine or 64-bit machine?
Does the driver present a dll for each of those? You can also get good JDBC help
from MS via their microsoft.public.sqlserver.jdbcdriver newsgroup.
Joe Weinstein at BEA
>
     at ourpackage.OurMDB.onMessage(OurMDB.java:184)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
     ... 11 more
Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
     at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
     at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
     at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
     at ourpackage.OurMDB.onMessage(OurMDB.java:184)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
     at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
     at ourpackage.OurMDB.onMessage(OurMDB.java:184)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
     ... 12 more

Similar Messages

  • Using Ranking on MS SQL Server 2005

    Hello,
    We are on BOXI3.1 base version and have a universe on top of MS SQL Server 2005.
    My question is regarding use of rank functions. BO guides state that
    You can perform a database ranking only if your database supports
    it. If this is not the case, the Add a database ranking button is disabled on
    the Query Panel toolbar. Databases that support ranking are Oracle, DB2,
    Terradata and Redbrick.
    So SQL Server is not in the list. However the add database ranking button is enabled on
    my report panel. If i add a ranking the query runs for a long time and times-out.
    Is there any universe parameter i need to enable to use ranking? Has any-one mangaged to
    use ranking functionality with SQL Server 2005.
    Thanks in advance.

    Hi Bashir Awan,
    When we create this Object (using your example) at Universe level is the ranking hardcoded ?
    My questions is, say i have Product object (with values A, B, C, D, E), and sales aggregated (10, 20, 30, 40, 50, 60, 70, 80, 90, 100)
    Say the table is as follows
    Product;        sales
        A;               10
        A;                70*
        B;                 50
        B;                 20*
        C;                 30
        C;                 60*
        D;                 40
        D;                 90
        E;                 80
        E;                100
    Note: * represents Oversees sales outside US
    Case 1: Now when we rank whole data to select top 3 we should get (E, D, C in Desc order)
    Case 2: Now if I apply prompt on Country of sales as US will I get (E, B, D) or is it still (E, D, C as earlier).
    Case 3: Similarly if I apply prompt on Product (no prompt on Country) in the filter pane and select (A, D, E) will my results show (E, D, A) or (E, D) as the value of A may be restricted due to ranking formula based on sales at Universe level.
    I am sorry I may be asking a very basic question. Thanks
    Sudhir.

  • Windows Authentication using Microsoft SQL Server 2005 JDBC Driver

    Hi,
    I am using Microsoft SQL Server 2005 JDBC Driver to connect to SQL Server 2000 database, can anyone tell me the connection URL for windows authentication. SQL authentication is working fine.
    DataDirect has drivers for windows authentication but I am not using it.
    Regards
    Arup

    You can't do it with the Microsoft driver. There's a free driver called jTDS that may be able to (I don't know).
    (edit) Looking at their FAQ it looks like it does:
    http://jtds.sourceforge.net/faq.html

  • SQL Server 2005 JDBC Driver

    I am trying to set up the Master Repository with the MS SQL Server 2005 JDBC Driver. I copied the sqljdbc.jar file into the /drivers directory, but it is not appearing in the drop down list. Any ideas? Thanks in advance.
    EDIT: I have solved the problem by looking at the instructions in the Thread: "Not able to estabish connection with SQLServer2005 from the Topology Manage" At first glance I did not think this would relate to my issue.
    Edited by: user9535932 on Nov 12, 2008 3:14 PM

    Hi,
    The driver will not appear in the list, but you can do this way.
    JDBC driver MS SQL Server 2005 :
    com.microsoft.sqlserver.jdbc.SQLServerDriver
    URL MS SQL Server 2005 :
    jdbc:sqlserver://localhost:1433;selectMethod=cursor;databaseName=xyz;integratedSecurity=false
    Hopefully it solve your problem..
    Regards,
    V13N

  • New SQL Server 2005 JDBC Driver

    Dear All,
    I am grasping for straws here. I have a very strange issue with
    the new Microsoft JDBC driver (Microsoft SQL Server 2005 JDBC Driver).
    I have a couple of strange things happenning when I am using this driver,
    but the most critical one is that the application literally hangs
    executing a readObject statement:
    ExpressionBuilder trp= new ExpressionBuilder();
    Expression exp1 = trp.get("ID").equal(ID);
    getDatabaseSession().readObject(Trip.class, exp1);
    I can see that it actually executes the statement, then hangs.
    Any ideas would be greatly appreciated
    I am using 10g Release 3 (10.1.3.0.0) (Build 060118)

    Are you able to get a thread dump to see where the threads are?
    Doug

  • Microsoft SQL Server 2005 JDBC Driver

    Hi
    how can i use Microsoft SQL Server 2005 JDBC Driver to coonect to db???

    com.microsoft.jdbc.sqlserver.SQLServerDriver is a SQL Server 2000 class.
    Also the port setting in the connection url jdbc:sqlserver://localhost:<port> is not 1433 as in SQL Server 2000.
    In the connection URL, <port> is obtained from the SQL Server configuration Manager. When the SQL Server 2005 is restarted the port number changes.
    To obtain the <port> in the SQL Server Configuration Manager select the node SQL Server 2005 Network Configuration>Protocols. Right-click on TCP/IP node and select Properties. Select the IP Addresses tab. In IP ALL the TCP Dynamic Ports specifies the <port> value.

  • Different versions of SQL Server 2005 Developer Edition

    Some of our business processes still use SQL Server 2005 and I need to install Developer Edition on my desktop.
    I have following downloads available in my MSDN subscription (other than Itanium):
    SQL Server 2005 Developer Edition - DVD (English) - 1 DVD ISO
    SQL Server 2005 Developer Edition - 64-bit Extended - 2x CD ISO
    SQL Server 2005 Developer Edition - 32-bit - 2x CD ISO
    The desktop is running 64-bit OS, so I definitely want to install 64-bit version. However, I am not sure what this "Extended" version available on CD-s is. Is this the only 64-bit version  in existence? Or are there 2 different 64-bit versions
    - "Extended" and "Non-Extended" (with non-extended possibly available on DVD - I haven't downloaded any images yet)?

    SQL Server 2005 Developer Edition - DVD (English) - 1 DVD ISO
    SQL Server 2005 Developer Edition - 64-bit Extended - 2x CD ISO
    SQL Server 2005 Developer Edition - 32-bit - 2x CD ISO
    The desktop is running 64-bit OS, so I definitely want to install 64-bit version. However, I am not sure what this "Extended" version available on CD-s is. Is this the only 64-bit version  in existence? Or are there 2 different 64-bit versions - "Extended"
    and "Non-Extended" (with non-extended possibly available on DVD - I haven't downloaded any images yet)?
    SQL server 2005 is outdated so sorry if my answer is not to the point . First DVD version seems to me like installable which has both database engine and client tools present in it for installation
    For second, SQL server 2005 installable was available in 2 CD's 1st CD was to install database engine/SSIS/SSAS/ SSRS features while second CD was to install specifically clint tools,books online legacy support . Its not possible to comment further without
    looking at contents but I guess you can use 2nd one. CD 1 would have one part of installable and CD 2 would have second
    And of course 3rd one is 32 bit of 2nd one.
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • Transfer data from 2 oracle version to sql server 2005

    Hi,
    I have two database servers on different machines. They are
    1) Oracle 8.1.7.4
    2) Oracle 7.3.1.4
    I have to create agents which can transfer tables from these two databases to one machine having sql server 2005 database.
    Please tell me what are the options. What drivers i need to install on machine having sql server 2005 so that i can transfer data from both oracle versions.
    Thanks
    Rajneesh.

    You could create a linked server. Install the Oracle client on the server with SQL Server 2005, setup the TNS to your Oracle databases, create the linked server and then grab the data that way. There are migration tools as well but if the database is small in size I found linked servers to work and give me better control over the migration. This assumes that the database is not very large. If it is really large a migration tool might be a better option.

  • Problem connecting JSF page with SQL server 2005 DB

    hello guys,
    i have tried working with the visual web JSF in NET BEANS 6.1 IDE.
    i get an error connecting the jsf page witht he sql server 2005 db.
    i get an odbc:jdbc error.
    can anyone gimme the exact correct coding to connect a a jsf page with the sql server 2005 db.
    expecting a reply soon...
    thanks a lot....
    sandeep

    You need to elaborate a bit more about the problem.
    Read this to get more chance on suitable help: [http://www.catb.org/~esr/faqs/smart-questions.html].

  • (new?) performance problem using jDriver after a Sql Server 6.5 to 2000 conversion

    Hi,
    This is similar - yet different - to a few of the old postings about performance
    problems with using jdbc drivers against Sql Server 7 & 2000.
    Here's the situation:
    I am running a standalone java application on a Solaris box using BEA's jdbc driver
    to connect to a Sql Server database on another network. The application retrieves
    data from the database through joins on several tables for approximately 40,000
    unique ids. It then processes all of this data and produces a file. We tuned
    the app so that the execution time for a single run through the application was
    24 minutes running against Sql Server 6.5 with BEA's jdbc driver. After performing
    a DBMS conversion to upgrade it to Sql Server 2000 I switched the jDriver to the
    Sql Server 2000 version. I ran the app and got an alarming execution time of
    5hrs 32 min. After some research, I found the problem with unicode and nvarchar/varchar
    and set the "useVarChars" property to "true" on the driver. The execution time
    for a single run through the application is now 56 minutes.
    56 minutes compared to 5 1/2 hrs is an amazing improvement. However, it is still
    over twice the execution time that I was seeing against the 6.5 database. Theoretically,
    I should be able to switch out my jdbc driver and the DBMS conversion should be
    invisible to my application. That would also mean that I should be seeing the
    same execution times with both versions of the DBMS. Has anybody else seen a
    simlar situation? Are there any other settings or fixes that I can put into place
    to get my performance back down to what I was seeing with 6.5? I would rather
    not have to go through and perform another round of performance tuning after having
    already done this when the app was originally built.
    thanks,
    mike

    Mike wrote:
    Joe,
    This was actually my next step. I replaced the BEA driver with
    the MS driver and let it run through with out making any
    configuration changes, just to see what happened. I got an
    execution time of about 7 1/2 hrs (which was shocking). So,
    (comparing apples to apples) while leaving the default unicode
    property on, BEA ran faster than MS, 5 1/2 hrs to 7 1/2 hrs.
    I then set the 'SendStringParametersAsUnicode' to 'false' on the
    MS driver and ran another test. This time the application
    executed in just over 24 minutes. The actual runtime was 24 min
    16 sec, which is still ever so slightly above the actual runtime
    against SS 6.5 which was 23 min 35 sec, but is twice as fast as the
    56 minutes that BEA's driver was giving me.
    I think that this is very interesting. I checked to make sure that
    there were no outside factors that may have been influencing the
    runtimes in either case, and there were none. Just to make sure,
    I ran each driver again and got the same results. It sounds like
    there are no known issues regarding this?
    We have people looking into things on the DBMS side and I'm still
    looking into things on my end, but so far none of us have found
    anything. We'd like to continue using BEA's driver for the
    support and the fact that we use Weblogic Server for all of our
    online applications, but this new data might mean that I have to
    switch drivers for this particular application.Thanks. No, there is no known issue, and if you put a packet sniffer
    between the client and DBMS, you will probably not see any appreciable
    difference in the content of the SQL sent be either driver. My suspicion is
    that it involves the historical backward compatibility built in to the DBMS.
    It must still handle several iterations of older applications, speaking obsolete
    versions of the DBMS protocol, and expecting different DBMS behavior!
    Our driver presents itself as a SQL7-level application, and may well be treated
    differently than a newer one. This may include different query processing.
    Because our driver is deprecated, it is unlikely that it will be changed in
    future. We will certainly support you using the MS driver, and if you look
    in the MS JDBC newsgroup, you'll see more answers from BEA folks than
    from MS people!
    Joe
    >
    >
    Mike
    The next test you should do, to isolate the issue, is to try another
    JDBC driver.
    MS provides a type-4 driver now, for free. If it is significantly faster,
    it would be
    interesting. However, it would still not isolate the problem, because
    we still would
    need to know what query plan is created by the DBMS, and why.
    Joe Weinstein at BEA
    PS: I can only tell you that our driver has not changed in it's semantic
    function.
    It essentially send SQL to the DBMS. It doesn't alter it.

  • Problem using DG4ODBC with named SQL Server instance

    I am running DG4ODBC on a 64 bit LINUX machine with the Microsoft SQL Server driver installed. I have successfully tested this with a SQL Server instance that was not named (GENERALI_DSN).The named instance gives the following when trying to query:
    ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
    [unixODBC][Microsoft][SQL Server Native Client 11.0]Login timeout expired {HYT00}[unixODBC][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].  {08001,NativeErr = -1}[unixODBC][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. {08001,NativeErr = -1}
    ORA-02063: preceding 2 lines from DEVMISC
    odbc.ini
    [GENERALI_DSN]
    Driver                  = SQL Server Native Client 11.0
    Server                  = CLTDMJCWBYZ.eu.scor.local
    User                    = everest
    Password                = everest
    Database                = Everest_Generali
    [DEVMISC_DSN]
    Driver                  = SQL Server Native Client 11.0
    Server                  = [USVCLTDEVSQL02\DEVMISC]
    User                    = link_user
    Password                = password1
    Database                = DBA
    initDG4ODBC2.ora
    # HS init parameters
    HS_FDS_CONNECT_INFO = DEVMISC_DSN
    HS_FDS_TRACE_LEVEL = DEBUG
    HS_FDS_SHAREABLE_NAME = /usr/lib64/libodbc.so
    # ODBC specific environment variables
    set ODBCINI=/home/oracle/.odbc.ini
    listener.ora
    SID_LIST_LISTENER_GW =
       (SID_LIST =
          (SID_DESC =
           (SID_NAME=DG4ODBC)
          (ORACLE_HOME=/home/oracle/product/11.2.0)
          (ENV=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micro
    soft/sqlncli/lib)
          (PROGRAM=dg4odbc)
          (SID_DESC =
           (SID_NAME=DG4ODBC2)
          (ORACLE_HOME=/home/oracle/product/11.2.0)
          (ENVS=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micr
    osoft/sqlncli/lib)
          (PROGRAM=dg4odbc)
    LISTENER_GW =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = usvcltprdoragw)(PORT = 1521))
    tnsnames.ora
    DG4ODBC =
       (DESCRIPTION=
          (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
          (CONNECT_DATA=(SID=DG4ODBC))
          (HS=OK)
    DG4ODBC2 =
       (DESCRIPTION=
          (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
          (CONNECT_DATA=(SID=DG4ODBC2))
          (HS=OK)
    I can't figure out why the named instance does not work but the other one does. Any help would be greatly appreciated!

    Did you check with the ODBC test utility isql (it is installed by default when you install the unixODBC Driver manager) if your ODBC driver can connect at all to that named instance? I have some doubts that it will work either as there was a blog commented by a MS engineer:
    Introducing the new Microsoft ODBC Drivers for SQL Server - Microsoft SQLNCli team blog - Site Home - MSDN Blogs
    who states that named instance connections are not supported using that driver.
    - Klaus

  • JSTL = Problem in connecting to MS SQL Server 2005

    hi....i really need some help here
    I am having touble in connecting MS SQL 2005 using odbc driver. The code is as below,
    <sql:setDataSource var="datasource" driver="sun.jdbc.odbc.JdbcOdbcDriver" url="jdbc:odbc:eleavedao" user="" password=""/>
    <sql:query var="count" dataSource="${datasource}">
    SELECT * FROM hr_leave_entry where userId = ?
    <sql:param value="${userid}"/>
    </sql:query>
    <c:set var="maxrow" value="${count.rowCount}" />
    From the code, i tried printing out some output into the interface. I realised that it printed out the query statement. Is there anything that i need to set other than set the odbc?
    Your help is greatly appreciated. Thank You!
    -Regards-

    Have you imported the JSTL sql tag library
    Are the <sql> tags still on the page as well as the query?

  • Using CLR Integration in SQL Server 2005

    I have several CLR SQLProcedures in my SQL Database for performing performing complex selects with regex etc.   These work exceptionally well form with Visual Strudio for retrieving a dataset. However from within Crystal Reports I can not see these stored procedures, so cannot use the to report on, which was the whole idea of creating them.
    Also, if I create a standard sql stored procedure, but include a CLR SQLFunction, it also fails in Crystal Reports.
    Considering CLR Intergration ha sbeen around since 2004/5, I would have expected CR 2008 to ba able to make use of them, but I can find no way to make them work.
    I hope some one can assist me in this quest.

    Please post this query to the Crystal Reports Design forum:
    SAP Crystal Reports
    That forum is monitored by qualified technicians and you will get a faster response there. Also, all BOE queries remain in one place and thus can be easily searched in one place.
    Thank you for your understanding,
    Ludek

  • Java - MS SQL Server 2005 JDBC connection problem

    Hi all, i tried to set up a connection and tried the following codes and got an exception
    {color:#ff0000}--------------------Configuration: <Default>--------------------
    Got an exception!
    com.microsoft.sqlserver.jdbc.SQLServerDriver
    Process completed.{color}
    part of my codes:
    import javax.swing.*;
    import java.awt.*;
    import java.awt.event.ActionListener;
    import java.awt.event.ActionEvent;
    import java.io.*;
    import java.util.*;
    import javax.swing.event.*;
    import java.awt.event.*;
    import javax.swing.border.*;
    import java.sql.*;
    public class RFIDLogistics extends JFrame{
    //Constructor
    public RFIDLogistics () {
    clock = new SimpleClock();
    try {
    Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
    String connectionUrl = "jdbc:sqlserver://L31101;" + "databaseName=RFID Logistics;";
    Connection con = DriverManager.getConnection(connectionUrl);
    catch (Exception e) {
    System.err.println("Got an exception! ");
    System.err.println(e.getMessage());
    What does the exception mean? any1 can guide me to set up the connection please.
    Thanks!

    It means that you're an eejit that will never learn to stop soiling himself, let alone write proper Java.
    %

  • Sql server replication from SQL SERVER VERSION(7.0) to SQL SERVER 2005

    Hi All,
    We are trying to create a replication between Sql server 7.0 data to SQL server 2005 data . We tried to create a local subscription in Sql server ,when tried to connect to publisher  running in Sql server 7.0 it is showing an error message
    like "This Sql server vresion(7.0) is not supported" .
    Could any one please help us with this issue ?
    Thanks
    Sandy

    Hi CRM_Learner,
    SQL Server version 7.0 Service Pack 4 (SP4) is the earliest version that can participate in a replication topology with SQL Server 2005. We need to verify the version of SQL Server. If you configure transactional replication with updating subscribers,
    for a SQL Server 7.0 Publisher, only SQL Server 7.0 Subscribers are supported. SQL Server 7.0, 2000 was out of support in the SQL Server Forums. I suggest you install SQL Server 2005 or later version to configure the SQL Server replication.
    For more information, there is a detail about using multiple Versions of SQL Server in a replication topology.
    http://technet.microsoft.com/en-us/library/ms143241(v=sql.90).aspx
    Regards,
    Sofiya Li
    If you have any feedback on our support, please click here.
    Sofiya Li
    TechNet Community Support

Maybe you are looking for

  • IPOD NANO 4GB Can't read disc

    We tried to update the Nano with new songs we had downloaded. Kept getting message "Can't read disc". Tried to restore Nano to factory settings. Downloaded iTunes 7.0 and updated iTunes. Got the following message after iTunes updated: "The iPod "Shan

  • IPhone 5c stopped turning on after IOS  8.1 update.

    2 days ago i decided to update my iPhone 5c to IOS 8.1. There was no noticeable issues with the update, but after attempting to use the phone, i did notice that the phone was not powering on. I've contacted apple support, and have done all the troubl

  • Audio not working in CS4

    Hello people, im sorry if this issue was talked about before, i did some research and i can't find the solution for this issue: i am using Premiere Pro CS4, Windows Vista64, 8GB RAM, i have a good audio card, when i first installed premiere, everythi

  • How to move the "i" in an iPhone app

    Hi, I have been bouncing my head on this one...I am developing an iPhone app with the famous "i" icon in the lower-right corner of the screen. I need to move this icon to another area of the screen OR change its color. For the life of me, I cannot fi

  • Java EE5 Tutorial - Totally lost!

    HI I'm just working through the Java EE5 Tutorial. I'm using: Sun Java System Application Server Platform Edition 9 Update 1 Patch 1 installed in C:\Sun\SDK The tutorial/example projects are therefore in: C:\Sun\SDK\domains\domain1\docroot\javaeetuto