Skip to Content
author's profile photo Former Member
Former Member

JDBC connection to MS Access DB

Hi guys,

I have a problem with a JDBC connection to a MS Access DB

I am using the JDBC driver "sun.jdbc.odbc.JdbcOdbcDriver". And when I have my mdb file on the XI server directly and use connection parameter "jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//<xiserver>/folder/TESTXI.mdb" I can write data into the DB without problems.

But when I have my Access mdb file on a different server which is not the XI Server I get the error "Cannot establish connection to URL 'jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//<IP>/Share/TESTXI.mdb': SQLException: [Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x1df0 Thread 0x4b0 DBC 0x887502c Jet'.'"

Do you have any ideas?

I would be grateful for every information.

Thanks

sven

Add comment
10|10000 characters needed characters exceeded

7 Answers

  • Posted on Aug 01, 2006 at 11:33 AM

    Hi Sven,

    Have u gone through this weblog..

    /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn

    Thanks and Regards,

    Sridhar

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 01, 2006 at 11:44 AM

    Hi,

    The directory specified must be accessible by the service user of the Adapter engine, with appropriate read/write permissions..The same applies to any adapter whether it is a File or JDBC.Actually in the first case your directory is accessible by service user whereas in the second case its not.

    Regards,

    Sudheer.

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 01, 2006 at 12:35 PM

    Hi,

    thanks for the replies but unfortunately the access rights are set up properly there should be no issue. But still doesn't work. Do you have any other idea?

    Thanks,

    Sven

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 01, 2006 at 12:50 PM
    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 01, 2006 at 02:01 PM

    Hi,

    thanks again for the replies. Unfotunately I already went thru all this stuff .IUSR_* has proper rights, etc.

    Is there no one who already implemented a JDBC call to an Access DB which is not located on XI server directly?

    Br,

    Sven

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 01, 2006 at 02:06 PM

    Hi Sven,

    Just check if you are able to connect to this IP from the XI server with the user id and password. I'm not sure how but I think you will probably have to use the run command (telnet IP address) and try to ping and see the connection between these two servers. Because, I think that only when this connection is successful, you will be able to access the DB.

    Regards,

    Sushumna

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 01, 2006 at 02:13 PM

    Hi Sushumna,

    pinging the other server is no problem, also accessing the folder directly from the XI server is no problem. Just if I try to do it with the JDBC adapter... 😔

    Br,

    Sven

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Check if you are giving the format of the Connection URL corectly.

      From help documentation:-

      <i>6. Specifications for database access

      db.connectionURL=<jdbc_driver_connection_url>

      Specify the address with which you can establish a database connection using the JDBC driver. The exact format of the address can vary; see documentation from the respective provider for more details. This specification is mandatory.</i>

      Regards,

      Sushumna