Microsoft SQL Server ODBC Driver 1.0 for Linux problem

Hello! I've RedHat Linux 6 Update 1 x64 on VMware Player and MS SQL Server on real machine. My application "servernew" on RedHat. All right, but when i try connect my SQL Server:
retcode = SQLDriverConnect(hdbc,NULL,string,sizeof(string),buf,sizeof(buf),&StringLength2,SQL_DRIVER_NOPROMPT);
i get retocde = -1;
Using SQLGetDiagRec:
MessageText = Data source name not found, and no default driver specified
To make my connection i use next attempts for connection string:
//char constring[200]="Driver={Microsoft Server ODBC Driver 1.0 for Linux};Server=ARTPK2\\SQLEXPRESS2;Database=Kurs;Uid=sa;Pwd=2ef5Fese";
//char constring[200]="Driver={SQL Server Native Client 11.0};Server=ARTPK2\\SQLEXPRESS2;Database=Kurs;Uid=sa;Pwd=2ef5Fese";
//char constring[200]="Driver={Microsoft SQL Server ODBC Driver V1.0 for Linux};Server=ARTPK2\\SQLEXPRESS2;Database=Kurs;Uid=sa;Pwd=2ef5Fese";
//char constring[200]="Driver={/opt/microsoft/sqlncli/lib64/libsqlncli-11.0.so.1790.0};Server=ARTPK2\\SQLEXPRESS2;Database=Kurs;Uid=sa;Pwd=2ef5Fese";
char constring[200]="DSN={SQL Server Native Client 11.0};Uid=sa;Pwd=2ef5Fese";
but...Data source name not found, and no default driver specified .. help me

Ok. New attempts with sqlcmd:
[root@localhost ~]# sqlcmd -S 192.168.0.3 -U sa -P 2ef5Fese -d first
SqlState HYT00, Login timeout expired
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.
TCP Provider: Error code 0x6F
New error 0x6F (i turned off firewall in windows).
[root@localhost ~]# sqlcmd -S ARTPK2\\SQLEXPRESS2 -U sa -P 2ef5Fese -d first
SqlState HYT00, Login timeout expired
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.
SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
It's bad way, but...
[root@localhost ~]# sqlcmd -D -S ARTPK2\\SQLEXPRESS2 -U sa -P 2ef5Fese -d first
SqlState IM002, Data source name not found, and no default driver specified
It's like in my program!!
  retcode = SQLDriverConnect(hdbc,NULL,string,sizeof(string),buf,sizeof     (buf),&StringLength2,SQL_DRIVER_NOPROMPT);
  i get retocde = -1;
  Using SQLGetDiagRec:
  MessageText = Data source name not found, and no default driver specified
Why "SQLDriverConnect"  is looking for DNS?!

Similar Messages

  • Connecting Oracle to MS SqlServer using Microsoft SQL Server ODBC Driver

    Hello,
    I have just downloaded the newly released Microsoft® SQL Server® ODBC Driver for Linux and trying to configure it to connect to SqlServer Database from Oracle using DG4ODBC
    Below are my config files:
    # odbcinst -j
    unixODBC 2.3.1
    DRIVERS............: /etc/odbcinst.ini
    SYSTEM DATA SOURCES: /etc/odbc.ini
    FILE DATA SOURCES..: /etc/ODBCDataSources
    USER DATA SOURCES..: /usr/oracle/.odbc.ini
    SQLULEN Size.......: 8
    SQLLEN Size........: 8
    SQLSETPOSIROW Size.: 8
    cat /etc/odbcinst.ini
    [SQL Server Native Client 11.0]
    Description = Microsoft SQL Server ODBC Driver V1.0 for Linux
    Driver = /opt/microsoft/sqlncli/lib64/libsqlncli-11.0.so.1720.0
    #UsageCount = 1
    Fileusage = 1
    Dontdlclose = 1
    [ODBC]
    Trace = ON
    Tracefile = /tmp/mstestodbc.log
    cat /usr/oracle/.odbc.ini
    [DEFAULT]
    Driver = SQL Server Native Client 11.0
    [MSTEST]
    Driver = SQL Server Native Client 11.0
    Description = Microsoft SQL Server ODBC Driver V1.0 for Linux
    Servername = ret2axxx
    Database = testdb
    Port = xxxx
    And when I am trying to do an ODBC test using isql I am getting the below error.
    # iusql -v MSTEST username password
    [unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_DBC failed
    [ISQL]ERROR: Could not SQLDriverConnect
    Any help is much appreciated!!
    Thanks,
    Steve.

    Thanks Kgronau for your response.
    I have made changes to the ODBC.ini file still getting the same error
    [MSTEST]
    Driver = /opt/microsoft/sqlncli/lib64/libsqlncli-11.0.so.1720.0
    #Driver = SQL Server Native Client 11.0
    Description = Microsoft SQL Server ODBC Driver V1.0 for Linux
    #Address = ret2axxx
    Server = ret2axxx, <port>
    Database = testdb
    and when I am trying to export odbcinst.ini export ODBCINSTINI=/etc/odbcinst.ini
    in odbcinst -j output it shows the wrong information.
    :~ $ odbcinst -j
    unixODBC 2.3.1
    DRIVERS............: /etc//etc/odbcinst.ini
    SYSTEM DATA SOURCES: /etc/odbc.ini
    FILE DATA SOURCES..: /etc/ODBCDataSources
    USER DATA SOURCES..: /usr/oracle/.odbc.ini
    SQLULEN Size.......: 8
    SQLLEN Size........: 8
    SQLSETPOSIROW Size.: 8
    And when export odbcinst.ini as export ODBCINSTINI=odbcinst.ini it shows the correct path.
    :~ $ odbcinst -j
    unixODBC 2.3.1
    DRIVERS............: /etc/odbcinst.ini
    isql -v mstest username password
    [IM005][unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_DBC failed
    [ISQL]ERROR: Could not SQLConnect
    Thanks,
    Steve.

  • Lack of TCP keepalive parameter in Microsoft SQL Server ODBC Driver for Linux

    Hello,
    the problem in the
    aforementioned driver is the lack of TCP keepalive parameter that results in hanged threads because of closed connections on the SQL Server side, but not closed
    sockets on the client side. This could happen due to network-related problems.
    The driver is used in mission critical 24/7 uptime application and due to hanged threads the application cannot continue it's work and it needs to be restarted.
    This is observed in the latest version of the driver on RHEL 5.6.
    If you need clarification please ask.
    Does anybody know any workaround to this situation or a solution that I'm not aware of?
    Thank you for your help,
    luk.s

    Find the TCP socket of the ODBC connection in your process and set the keep-alive option and keep-alive timeout on it.
    You can do that by interposing socket system call.
    Or use libkeepalive: http://www.tldp.org/HOWTO/html_single/TCP-Keepalive-HOWTO/#libkeepalive

  • Regarding Microsoft SQL Server 2000 Driver for JDBC (2.2.0019)

    I have downloaded and installed Microsoft SQL Server 2000 Driver for JDBC (2.2.0019). Now i have to configure it for my development purpose. Can i use this driver for my development purpose or not. If yes does it create any kind of problem in future when i change the platform. My development should not depend on driver and database.
    Can i use any other driver provided by sun microsystem. If yes let me know where can i download and configure it.
    Waiting for the updates ASAP

    See, the bridge, being a type 1 driver has
    river has all the inherent limitations of that type
    drivers, due to the extra levels the data must
    passthrough inthe journey between the DB and the
    client. Also the use of native code.. makes it
    unsuitable to be used in applets.. the odbc should be
    configured in the client for this driver to work. etc.
    etc.
    It may be stable and useful for some
    for some applications.. but for sccenarios where one
    needs the solution tobe platform independent, ...By definition that would be the case. Of course the odbc-bridge does work on Windows, Solaris and Linux. So what other platform were you thinking about?
    ... less dependent on the user configuration,The bridge doesn't need any configuration. Or at least not any more than any other driver. The ODBC driver of course does need configuration.
    ...needs the minimum preparations from theuser, and above all give
    the fastest response time for him, the bridge cannot
    beat type 4 drivers. You are going to have to provide a link for that particular performance quote. Given that performance is impact most severely by requirements then design and finally by round trip time to the database I doubt that for applications (rather than benchmarks) that any difference is going to be significant.
    the problem i think was my use of
    my use of 'commercial' that u pointed out..
    anyway.. u are of course right if what u intended was
    stability only. but what i intended with that word was
    different .. sorry for creating the confusion.
    And it still seems like you are implying that it is not suitable for deployment in production systems. And as I pointed out I did deploy it in a large scale production system.
    I am not saying that type 4 drivers do not have a place nor that they do not have advantages, but their mere existance does not prove that they are a better choice for all installations.

  • Error establishing socket (Microsoft SQL Server 2000 Driver for JDBC)

    I tray connect to MS-SQL2000 using JDeveloper and retrieve an error: "[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.[Microsoft][SQLServer 2000 Driver for JDBC]PC160832\NCI_DBA_01"
    I followed the steps:
    1 - Install the JDBC Driver for MS-SQL2000
    2 - Create a new AddJavaLibPath :"AddJavaLibPath C:/Program files/Microsoft SQL Server 2000 Driver for JDBC/lib"
    3 - Specify Default Project Libraries: "msbase.jar, msutil.jar and mssqlserver.jar"
    4 - Create a new connection: "Java class name: com.microsoft.jdbc.sqlserver.SQLServerDriver" "URL: jdbc:microsoft:sqlserver://PC160832\NCI_DBA_01:1433;SelectMethod=cursor"
    5 - Retrieve the error: "[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.[Microsoft][SQLServer 2000 Driver for JDBC]PC160832\NCI_DBA_01"

    Were you able to resolve this? If so could you tell me how. I have the same problem.
    Thanks!!!

  • Microsoft SQL Server JDBC driver and WLS JMS problem?

              Greetings,
              I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
              persisted to SQL Server, during WLS startup the JMS attempts to
              read the JMSStore and JMSState tables in the db, if they are
              already present (say, from a previous run) the driver kicks out:
              java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
              not re-read row data for column 1.
              If the tables are not present, then WLS creates them and
              everything proceeds fine. Now, its not a good thing to attempt
              to reread row data for a ResultSet, especially for portability. Why is WLS JMS
              doing this? is there some config I can use to adjust JMS startup behavior for
              persisted JMS stores?
              Jay Houghton
              Centiv
              [email protected]
              long exception trace follows:
              <Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory "BroadcastTopicFactory"
              is started.>
              <Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer", Opening
              JDBC store tables "JMSStore
              " and "JMSState" using connection pool "JMSConnectionPool".>
              <Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer", store
              failed to open, java.io.IOEx
              ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix = <null>:
              recover
              java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
              not re-read row data for colum
              n 1.
              at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
              at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
              at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
              at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
              at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
              at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
              at weblogic.jms.backend.BEStore.open(BEStore.java:179)
              at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
              at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
              at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
              at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
              at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
              at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
              at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
              3)
              at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
              at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
              at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
              at $Proxy40.updateDeployments(Unknown Source)
              at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
              .java:2734)
              at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
              at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
              at java.lang.reflect.Method.invoke(Native Method)
              at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
              at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
              at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
              at $Proxy57.start(Unknown Source)
              at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
              _CachingStub.java:480)
              at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
              at weblogic.management.Admin.finish(Admin.java:571)
              at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
              at weblogic.Server.main(Server.java:35)
              

              Tom,
              thanks for the info, I'll bring this to support.
              I did try the weblogic jDriver for SQL Server and it works fine, so i think it
              must be the way JMS is interacting with the MS driver.
              here are my components:
              WLS 6.1sp1
              Microsoft® SQL Server™ 2000 Driver for JDBC™ is a (Type 4 JDBC) which provides
              partial JDBC 2 support (no blobs, clobs, etc)
              MS SQL Server 2000 (sp2?)
              thanks!
              Jay Houghton
              [email protected]
              Tom Barnes <[email protected]> wrote:
              >Hi Jay,
              >
              >This is not a known issue at BEA as far as I know, perhaps it is the
              >result
              >of a new driver/database combination. Try using a different driver,
              >or a different
              >version of the current driver. Meanwhile, use a file store (just as
              >reliable but faster) and log a case with customer support, including
              >information on your version, service-pack, and what driver you are using.
              >
              >Tom, BEA
              >
              >Jay Houghton wrote:
              >
              >> Greetings,
              >>
              >> I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
              >> persisted to SQL Server, during WLS startup the JMS attempts to
              >> read the JMSStore and JMSState tables in the db, if they are
              >> already present (say, from a previous run) the driver kicks out:
              >>
              >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
              >can
              >> not re-read row data for column 1.
              >>
              >> If the tables are not present, then WLS creates them and
              >> everything proceeds fine. Now, its not a good thing to attempt
              >> to reread row data for a ResultSet, especially for portability. Why
              >is WLS JMS
              >> doing this? is there some config I can use to adjust JMS startup behavior
              >for
              >> persisted JMS stores?
              >>
              >> Jay Houghton
              >> Centiv
              >> [email protected]
              >>
              >> long exception trace follows:
              >>
              >> <Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory
              >"BroadcastTopicFactory"
              >> is started.>
              >> <Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer",
              >Opening
              >> JDBC store tables "JMSStore
              >> " and "JMSState" using connection pool "JMSConnectionPool".>
              >> <Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer",
              >store
              >> failed to open, java.io.IOEx
              >> ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix
              >= <null>:
              >> recover
              >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
              >can
              >> not re-read row data for colum
              >> n 1.
              >> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
              >> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
              >> at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
              >> at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
              >> at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
              >> at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
              >> at weblogic.jms.backend.BEStore.open(BEStore.java:179)
              >> at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
              >> at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
              >> at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
              >> at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
              >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
              >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
              >> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
              >> 3)
              >> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
              >> at java.lang.reflect.Method.invoke(Native Method)
              >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
              >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
              >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
              >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
              >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
              >> at $Proxy40.updateDeployments(Unknown Source)
              >> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
              >> java:2734)
              >> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
              >> )
              >> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
              >> at java.lang.reflect.Method.invoke(Native Method)
              >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
              >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
              >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
              >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
              >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
              >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
              >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
              >> at $Proxy57.start(Unknown Source)
              >> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
              >> _CachingStub.java:480)
              >> at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
              >> at weblogic.management.Admin.finish(Admin.java:571)
              >> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
              >> at weblogic.Server.main(Server.java:35)
              >
              

  • Microsoft SQL Server JDBC Driver problem

    Hi all,
    I've downloaded the JDBC driver for SQL Server 2000 from Microsoft website and I
    tried creating connection pool in Weblogic (WL 6.1 SP2).
    Following are the configuration from the admin console,
    Name - SQL2K
    URL - jdbc:microsoft:sqlserver://127.0.0.1:1433
    Driver Classname - com.microsoft.jdbc.sqlserver.SQLServerDriver
    ACLName - sa
    Password - tonypet
    After creating the config, I select to chose the target server from the Servers tab
    in Targets main tab in the admin console and when I click on Apply I saw in the WL
    server command prompt the following error,
    <16/07/2002 11:22:55> <Error> <JDBC> <Cannot startup connection pool "SQL2K" Cannot
    load driver class: com.microsoft.jdbc.sqlserver.SQLServerDriver>
    I have assigned the classpath env var as follows,
    CLASSPATH=;.;C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar;C:\Program
    Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar;
    C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar;c:\bea\wlserver6.1\lib\weblogic.jar
    I've tried even copying the .JAR files to the ext and lib directory of bea directory
    but I'm getting the same error.
    Can anyone help me please.
    Thanks a lot for your help
    Cheers
    Nanik

    Hi. You will also be wanting to add this property for the pool to apply to that driver:
    SelectMethod=cursor
    Joe
    Nanik Tolaram wrote:
    Hi all,
    After fiddling around I found a solution (hope this will help those who are having
    the same problem),
    1. Make sure you add the complete directory of the library of the .JAR files in the
    classpath in the STARTWEBLOGIC.CMD, I made a mistake of specifying the path in the
    CLASSPATH and NOT IN the STARTWEBLOGIC.CMD as the classpath is overriden in the STARTWEBLOGIC.CMD
    file.
    2. The other thing I found was the configuration setting. I put the full settings
    in the URL in admin console as follows,
    jdbc:microsoft:sqlserver://127.0.0.1:1433;user=nanik;password=tonypet;databasename=scriptbuilder
    When I put it individually in the Properties filed it won't work as it is not picking
    it up from there but when I moved it to the URL and put it all together it worked
    fine.
    Whew !!! it's been a looong day, hope the info will help.
    Cheers
    Nanik
    "Nanik Tolaram" <[email protected]> wrote:
    Hi all,
    I've downloaded the JDBC driver for SQL Server 2000 from Microsoft website
    and I
    tried creating connection pool in Weblogic (WL 6.1 SP2).
    Following are the configuration from the admin console,
    Name - SQL2K
    URL - jdbc:microsoft:sqlserver://127.0.0.1:1433
    Driver Classname - com.microsoft.jdbc.sqlserver.SQLServerDriver
    ACLName - sa
    Password - tonypet
    After creating the config, I select to chose the target server from the
    Servers tab
    in Targets main tab in the admin console and when I click on Apply I saw
    in the WL
    server command prompt the following error,
    <16/07/2002 11:22:55> <Error> <JDBC> <Cannot startup connection pool "SQL2K"
    Cannot
    load driver class: com.microsoft.jdbc.sqlserver.SQLServerDriver>
    I have assigned the classpath env var as follows,
    CLASSPATH=;.;C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar;C:\Program
    Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar;
    C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar;c:\bea\wlserver6.1\lib\weblogic.jar
    I've tried even copying the .JAR files to the ext and lib directory of bea
    directory
    but I'm getting the same error.
    Can anyone help me please.
    Thanks a lot for your help
    Cheers
    Nanik

  • Urgent Clarification - Microsoft SQL Server JDBC Driver Problem

    Hi,
    Can somebody tell me how to create a connection Pool in weblogic 7 using Microsoft
    SQL Server Driver for JDBC.(should be XADataSource).
    I mean the pool should be created using com.microsoft.jdbcx.sqlserver.SQLServerDataSource
    class.
    The error message i am getting is "Unknown source" during providing targets for
    the connection pool.
    Thanks in advance,
    Rahul.

    <JDBCConnectionPool
    DriverName="com.microsoft.jdbcx.sqlserver.SQLServerDataSource"
    Name="SQL2000JDBC"
    Properties="serverName=nc-answline-w2k;url=jdbc:microsoft:sqlserver;dataSourceName=SQL2000JDBC;user=test;databaseName=test;selectMethod=curosr;userName=test;password=test;portNumber=1435"
    URL="jdbc:microsoft:sqlserver"/>
    Try this is your config.xml and make sure you have mssqlsriver first thing in classpath.
    Thanks,
    Mitesh
    Rahul wrote:
    Hi,
    Can somebody tell me how to create a connection Pool in weblogic 7 using Microsoft
    SQL Server Driver for JDBC.(should be XADataSource).
    I mean the pool should be created using com.microsoft.jdbcx.sqlserver.SQLServerDataSource
    class.
    The error message i am getting is "Unknown source" during providing targets for
    the connection pool.
    Thanks in advance,
    Rahul.

  • UCCX 8.x Database access - Anyone test the Microsoft SQL Server JDBC Driver 3.0 from Microsoft ?

    2 questions come to mind.
    will it work
    will TAC support you ?
    available here
    http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a737000d-68d0-4531-b65d-da0f2a735707&displaylang=en
    Brief Description
    Download the SQL Server JDBC Driver 3.0, a Type 4 JDBC driver that provides database connectivity through the standard JDBC application program interfaces (APIs) available in Java Platform, Enterprise Edition 5 and above.

    You can test it using DBvisualizer. If you can make it work in that (actually it gives you more information about connection errors etc.), it should working in UCCX also.

  • Which version of Microsoft SQL Server 2012 OLE DB Provider for DB2 needed?

    Hello, first time posting.....
    I am developing an SSIS package that needs to connect to DB2 tables. My environment does not have the necessary providers installed (SQL Server 2012 OLE DB Provider for DB2).
    I am running SSIS on a Windows Server 2012 R2 Standard server, w/ SQL Server 2012 R2 installed.
    I noticed OLEDB Provider for DB2 v4.0 for SQL Server 2012 does not support Windows Server 2008 R2.
    Also, there appears to be a version 5 OLEDB Provider for DB2, bundled with SQL Server 2014 Feature Pack, but I am not running SQL 2014.
    Could someone please tell me which version I need to install for Windows Server 2012 R2, running SQL Server 2012 R2?
    Thanks!

    Also, there appears to be a version 5 OLEDB Provider for DB2, bundled with SQL Server 2014 Feature Pack, but I am not running SQL 2014.
    The DB2 OleDB Provider is completly independend of the used SQL Server/SSIS Version; you can use that one.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • Microsoft SQL Server JDBC Driver

    Hi everyone,
    I know it's a bit off topic but I couldn't find a related group.
    Does anyone know of the best way to access SQL Server via JDBC. I have tried
    the JDBC-ODBC bridge but it does not seem to support all types of queries
    (e.g. using a PreparedStatement).
    I have looked at Microsoft's JDBC driver but I'm not allowed to implement it
    as it is a Beta version.
    I would be very grateful if anyone could help me.
    Thanks,
    Nick.

    Neil Pike wrote:
    Nick - there are plenty of other jdbc drivers :-
    Q. Where can I get a JDBC driver for SQL Server? Do Microsoft write one?
    Which is the best one?
    A. Microsoft doesn't supply a native JDBC driver for SQL Server,Actually, yes it does, now. This is a recent thing. It is a type-4 driver built by
    DataDirect/Merant.
    It is free, now in beta, will be GA soon, and is available for download from MS's sqlserver support
    pages.
    but it does
    offer a JDBC-to-ODBC bridge that allows Java programmers to access back-end
    data sources using available ODBC drivers. The Microsoft JDBC-ODBC bridge is
    part of the core set of classes that come with the Microsoft Virtual Machine
    (Microsoft VM) for Java. For more information, see
    http://www.microsoft.com/java/.
    Avoid the jdbc-odbc bridge for use with weblogic. The JDBC-ODBC bridge is buggy,
    unsupported, and not thread-safe.
    You can get 3rd party drivers, servers, and bridges from a variety of vendors
    and some free open-source ones as well.
    Which is the best one? As I don't use any of them I can't comment from
    personal experience. The two most commonly used seem to be WebLogic and
    OpenLink - and feedback on them seems good.
    Some of the sites listed below maintain up to date lists of all vendors.
    The full list that I know of are :-
    1. WebLogic : http://weblogic.beasys.com and http://www.weblogic.com. (type
    2, 3 or 4. SQL 6.5 and 7.0). Download type-4 driver direct from
    http://www.weblogic.com/download/downloadkona.html
    2. http://www.inetsoftware.de. JDBC Type 4 drivers for the Microsoft
    SQLServer 6.5, 7.0, and 2000. JDBC 1.22 driver to use with JDK 1.1x and a JDBC
    2.0 driver (i-net Sprinta) to use with Java 2 (JKD 1.2x).
    JDBC 1.22 : http://www.inetsoftware.de/English/produkte/jdbctreiber/Default.htm
    JDBC 2.0 : http://www.inetsoftware.de/English/produkte/jdbc2/Default.htm.
    3. http://www.openlinksw.com (http://www.openlinksw.co.uk)
    4. http://www.easysoft.com and http://beta.easysoft.com. JDBC/ODBC bridge.
    5. ftp://freetds.internetcds.com/pub/freetds_jdbc. Type 4 open-source driver
    that is designed to work with SQL Server 6.5 and Sybase 11.x
    6. http://java.sun.com/products/jdbc From this page you may search or browse
    the database of JDBC technology drivers that support the JDBC 2.x and JDBC 1.x
    APIs.
    7. http://lpv.home.texas.net (LpVodbc is a multi-threaded JDBC-ODBC database
    server that runs on Windows 95, 98, and NT platforms)
    8. http://www.avenir.net/products/jdbcdrivers.htm
    9. http://www.jturbo.com
    10. http://ourworld.compuserve.com/homepages/Ken_North/jdbcvend.htm is another
    list of JDBC drivers, servers, and vendors compiled by Ken North.
    11. http://www.sco.com/java/
    12. Merant. http://www.merant.com/datadirect/products/jdbc/sl50/overview.asp
    ===
    v1.19 2000.06.13
    Applies to SQL Server versions : All
    FAQ Categories : Connectivity
    Related FAQ articles : odbcunix
    Related Microsoft Kb articles : n/a
    Other related information : n/a
    Authors : Neil Pike

  • Java.lang.OutOfMemoryError (Microsoft SQL Server JDBC driver)

    Hi everyone,
    I am getting a java.lang.OutOfMemoryError when performing a simple query to a database. The query produces only one row (and will always produce only one row). However, the statement that produces the second column in the resultset is very long (>256) characters, so could that be it?
    Also, I am executing thousands of SQL statements with no difficulty. I have double-checked that I am cleaning up all of my database resources, so I don't think that this is it. Do I have to do anything else besides closing the statement and resultset?
    There is no stack trace, otherwise I would have posted it :(
    Also, as an aside - is the Microsoft JDBC driver for SQL Server the best one to use? It seems poorly supported and slow at times. Are there any alternatives?
    Thanks for your time :)
    Ben

    It is running after thousands of other queries. I'll test to see what happens if I run it by itself.
    I am closing the connection. In fact, I am running all of these statements over the same connection and simply opening and closing resultsets.
    So a bug in the driver you think?
    Thanks for the reply :)
    Ben

  • [Microsoft][SQL Server JDBC Driver] No Rows Affected

    hi guys,
    I am getting following error when I insert a row into a Table
    TallymanDB: Error - INSERT INTO RAISEDEVENTS(Accountid,Eventid,Operationid,Date
    Time,ReviewDate,Deleted) VALUES(2,4,0,1047999439002,'16-APR-2003',null)
    java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]No rows affected.
    at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
    at com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown S
    ource)
    at com.microsoft.jdbc.base.BaseStatement.executeUpdate(Unknown Source)
    at com.sanderson.tallyman.util.TallymanDB.executeUpdate(TallymanDB.java:
    217)
    at Test.main(Test.java:14)
    java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]No rows affected.
    at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
    at com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown S
    ource)
    at com.microsoft.jdbc.base.BaseStatement.executeUpdate(Unknown Source)
    at com.sanderson.tallyman.util.TallymanDB.executeUpdate(TallymanDB.java:
    217)
    at Test.main(Test.java:14)
    I am using SQL Server 2000 as the database.
    The row is getting inserted correctly in the table. There is one trigger on this table which seems to give this error.
    The trigger calls a .dll which connects to some other program using the Sockets.
    The functionality seems to be working fine but we get the above mentioned error in the log.
    Can anyone help me regarding this.
    Regards,
    Rahul
    Does anyone has idea

    hi...
    following is the insert code:
    TallymanDB is the class which deals with the Database interaction.
    Regards,
    Rahul
    try
    psRecord = this.aTallymanDB.getPreparedStatement(
                   "INSERT INTO RaisedEvents (ACCOUNTID,EVENTID,OPERATIONID,DATETIME,REVIEWDATE) VALUES (?,?,?,?,?)");
              //Get Timestamp
              ts = this.aTallymanDB.getCurrentDate();
              if (ts == null)
                   ts = new Timestamp(System.currentTimeMillis());
              strErrorCode = "CM028";
              //Log event
    System.out.println("##### Inserting in LogEvent #### " );
              System.out.println("iAccountID: "+iAccountID+" iEventID: "+iEventID+" ts.getTime(): "+ts.getTime()+" tsReviewDate: "+tsReviewDate );
              psRecord.setInt(1, iAccountID);
              psRecord.setInt(2, iEventID);
              psRecord.setInt(3, 0);
              psRecord.setLong(4, ts.getTime());
              psRecord.setTimestamp(5, tsReviewDate);
              psRecord.executeUpdate();
    psRecord.close();
    aTallymanDB.releasePreparedStatement();
    psRecord = null;
         catch (Exception e)
              bCloseStmt = true;
              ErrorLog.log(strErrorCode,iAccountID);
              throw e;
         finally
              if (rs != null)
                   rs.close();
              if (bCloseStmt)
                   if (this.psSelect != null)
                        psSelect.close();
         }

  • Microsoft Sql server data-mining add-on for excel 2013:

    In browsing the models using excel data-mining add-on the browsing query recognized that the query times out after 60 seconds. The question is how we can increase the query time-out
    time for data-mining add-on?

    Perhaps you are meaning the timeout settings for your Analysis Server -- under Properties, General, DatabaseConnectionPoolConnectTimeout defaults to 60.   Though I doubt that browsing any model should take 60 seconds.  Try browsing the model
    from Management Studio and seeing if you also need a lot of time.
    Mark Tabladillo PhD (MVP, SAS Expert; MCT, MCITP, MCAD .NET) http://www.marktab.net

  • MS SQL Server ODBC Connection On Linux

    Hi All,
    I am badly stuck with configuration of MS SQL Server ODBC connection on SUSE Linux 10. I am almost tried everything I got from SAP notes but still getting ODBC Lib Data Direct drivers could not be loaded IES 10901.
    ENV: SAP BO 4.0 SP7, MS SQL SRV 2008
    Here is what I have tried so far:
    1) Modified env.sh under /install_dir/sap_bobj/setup and added the line in bold.
    ":${BOBJEDIR}enterprise_xi40/linux_x64/odbc/lib:${BOBJEDIR}enterprise_xi40/$SOFTWAREPATH32/odbc/lib"
    The line should look like this
    LIBRARYPATH="$LIBDIR:$LIBDIR32:$WCSCOMPONENTDIR:$PLUGINDIST/auth/secEnterprise:${CRPEPATH64}:${CRPEPATH}:${MWHOME}:$PLUGINDIST/desktop/CrystalEnterprise.Report:
    ${BOBJEDIR}enterprise_xi40/$SOFTWAREPATH32/ras:${BOBJEDIR}mysql/lib:${BOBJEDIR}enterprise_xi40/linux_x64/odbc/lib:${BOBJEDIR}enterprise_xi40/$SOFTWAREPATH32/odbc/lib”
    2) We have .odbc.ini file in the home directory of our BO user on linux. Added following DSN entry (Same DSN is created on client and odbc connection has been created on the universe using this DSN:
    boeadm01:~> vi .odbc.ini
    [DSN_NAME]
    Driver=/opt/sapboe/sap_bobj/enterprise_xi40/linux_x64/odbc/lib/CRsqls24.so
    Description=DataDirect 6.0 SQL Server Native Wire Protocol
    HostName=SQL Server Hostname
    Database=SQL DB Name
    QuotedId=Yes
    AnsiNPW=No
    3) We then added the environment variables and LIBPATH in BO user .profile file.
    boeadm01:~> vi .profile
    #Sql Server Environment
    ODBCINI=$HOME/.odbc.ini
    export ODBCINI
    LD_LIBRARY_PATH=/opt/sapboe/sap_bobj/enterprise_xi40/linux_x64/odbc/lib
    export LD_LIBRARY_PATH
    4) Did echo to check the LIBPATH
    boeadm01:~> echo $LD_LIBRARY_PATH
    /opt/sapboe/sap_bobj/enterprise_xi40/linux_x64/odbc/lib
    5) Modified sqlsrv.sbo under /install_dir/sap_bobj/enterprise_xi40/dataAccess/connectionServer/odbc
      <Parameter Name="Use DataDirect OEM Driver" Platform="Unix">Yes</Parameter>
    6) Restarted BO node.
    Tried creating a new webi report and got the error mentioned above.
    Please help!!!
    Thanks,
    Anshul

    Hi Anshul,
    Please refer the below KBA & SCN thread regarding your issue.
    Data Direct ODBC Drivers for SAP BusinessObjects Data Services
    Link:
    http://scn.sap.com/docs/DOC-8898
    Business Objects XIR2 Link:
    Link:
    http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/50eca18b-d13e-2b10-a8ab-9738927177d6?quicklink=index&overridelayout=true
    http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/20e11153-5c3f-2b10-f9be-974dc4749fd8?quicklink=index&overridelayout=true
    http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/70eabcba-5c64-2b10-6db2-ae28ae4d1295?quicklink=index&overridelayout=true
    http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/4039c80b-6b3f-2b10-64a4-e8e591292e89?quicklink=index&overridelayout=true
    KBA:
    1291142 - Web Intelligence reporting using DataDirect drivers in Unix
    1292899 - Data Direct Drivers for Crystal Report in Unix environment
    SQL Server ODBC Driver for Linux/Unix Getting Started Tutorial
    Link:
    http://www.easysoft.com/products/data_access/odbc-sql-server-driver/getting-started.html
    Step by Step: Setting up Linux ODBC driver for SQL Server
    Link:
    http://blogs.technet.com/b/sqlman/archive/2012/08/03/step-by-step-setting-up-linux-odbc-driver-for-sql-server.aspx
    Microsoft SQL Server ODBC driver for Linux
    Link:
    http://www.codesynthesis.com/~boris/blog/2011/12/02/microsoft-sql-server-odbc-driver-linux/
    Thanks,
    Daya

Maybe you are looking for

  • Cheap Audigy SE for Recording with a Microphone?

    Would the Audigy SE work for recording guitar? Is it a full duplex card? (i.e. can I record a track in a multitrack program while listening to another track?) Every store you go, its the same 4 cards available- Audigy SE, $30; XFI Music, $70, XFI Gam

  • Mail configuration and background job scheduling for ST22 Data

    Experts, I want to know how can i schedule a background job in SAP to extract data from ST22 and send a automated mail for the same? Any help will be appreciated, Thanks!!! Regards, Vinit Pagaria

  • Can't propagate Cache-Control headers with Surrogate-Control header

    My application may set the following response header to cause webcache to process the esi:include's: Surrogate-Control: content=ORAESI/9.0.4, max-age=3600 It and also may set the following intended for the browser cache: Cache-Control: private or say

  • JSF general query regarding UISelectItem and UISelectItems

    I am seeing a couple of peculiar behavior and i have no explanation for them at the moment . It would be great if someone can explain the apparently different behavior of JSF in general. Whenever there is 'n' number of UISelectItem components inside

  • Not Able To Install After Effects Cs6 Trial

    I am currently using a macbook pro 13 inch with mountain lion software at version 10.8.2 I am not able to install the after effects cs6 trial I tried to turn off my proxies and vpn, but it still does not work I also tried to restart my computer and t