trying to connect to MSSQL DB using D2RQ
633 views
Skip to first unread message
Jonas
Jan 5, 2013, 9:41:51 AM1/5/13
to topbrai...@googlegroups.com
Dear All,
Happy new year everyone, and congratulations on the new release.
I'm using the new Topbraid Standard version 4.1 and I try to connect topbraid to a MSSQL Database using the userguide (import -> create connection for RDBMS Source (using d2rq)). As instructed I downloaded the latest version of the jtds sql drivers, renamed it to jtds.jar and put it into my topbraid/dropins folder. I add the remaining connection information (url, username, password) but the following error pops up:
The connection string is correct, the database is running, I can access it via my own Java DB test script using the very same jtds drivers from the dropins folder. I'm working with Java 1.6, tried using older sql drivers, tried microsofts sql drivers, tried an old Topbraid version and running topbraid as an administrator with no success. Is there anybody experiencing the same problems?
Thanks a lot for your support.
kind regards,
Jonas
Happy new year everyone, and congratulations on the new release.
I'm using the new Topbraid Standard version 4.1 and I try to connect topbraid to a MSSQL Database using the userguide (import -> create connection for RDBMS Source (using d2rq)). As instructed I downloaded the latest version of the jtds sql drivers, renamed it to jtds.jar and put it into my topbraid/dropins folder. I add the remaining connection information (url, username, password) but the following error pops up:
An error has occurred. See error log for more details.
Cannot instantiate SQL Driver net.sourceforge.jtds.jdbc.Driver: please place driver file jtds.jar into folder [removed folders]\dropins\ and restart TopBraid.
Database connection to [removed connection string] failed (user: sa): No suitable driver found for [removed connection string] (E54)
The connection string is correct, the database is running, I can access it via my own Java DB test script using the very same jtds drivers from the dropins folder. I'm working with Java 1.6, tried using older sql drivers, tried microsofts sql drivers, tried an old Topbraid version and running topbraid as an administrator with no success. Is there anybody experiencing the same problems?
Thanks a lot for your support.
kind regards,
Jonas
Scott Henninger
Jan 8, 2013, 2:31:25 PM1/8/13
to TopBraid Suite Users
Jonas, have you taken a look at Help > TopBraid Composer > Working
with Data Back Ends > Working with RDF Databases > Working with
Relational Databases > Working with MySQL or Microsoft SQL Server
Databases? That page provides some guidance in how to use jTDS, which
is shipped with the product. There are also instructions for how to
wrap the SQL Server driver for use in Eqiunox, which is required to
before the jar is placed in the dropins folder.
-- Scott
with Data Back Ends > Working with RDF Databases > Working with
Relational Databases > Working with MySQL or Microsoft SQL Server
Databases? That page provides some guidance in how to use jTDS, which
is shipped with the product. There are also instructions for how to
wrap the SQL Server driver for use in Eqiunox, which is required to
before the jar is placed in the dropins folder.
-- Scott
Jonas
Jan 14, 2013, 11:09:42 AM1/14/13
to topbrai...@googlegroups.com
Hi Scott,
yes I have. But its confusing and not working :) In "Working with MySQL or Microsoft SQL Server Databases" it says we should use Microsofts SQL Driver and it needs to be wrapped by an external tool (which I have done, and succeded). But when I look at "Importing Relational Databases with D2RQ" there is only the JTDS Driver mentioned. And in the application the Microsoft Driver is not even available for choice in the Driver Class dropdown. If I add it, by typing it in manually "com.microsoft.sqlserver.jdbc.SQLServerDriver" and change the server string to "jdbc:sqlserver://[server];databaseName=[dbName]" it comes up with the error message: "driver may not be supported..."
The jTDS that is shipped with the product is creating the initial error "cannot instantiate driver".
I'm working with Java 1.6 and Win7 - 64 bit.
thanks a lot for your support.
kind regards,
jonas
yes I have. But its confusing and not working :) In "Working with MySQL or Microsoft SQL Server Databases" it says we should use Microsofts SQL Driver and it needs to be wrapped by an external tool (which I have done, and succeded). But when I look at "Importing Relational Databases with D2RQ" there is only the JTDS Driver mentioned. And in the application the Microsoft Driver is not even available for choice in the Driver Class dropdown. If I add it, by typing it in manually "com.microsoft.sqlserver.jdbc.SQLServerDriver" and change the server string to "jdbc:sqlserver://[server];databaseName=[dbName]" it comes up with the error message: "driver may not be supported..."
The jTDS that is shipped with the product is creating the initial error "cannot instantiate driver".
I'm working with Java 1.6 and Win7 - 64 bit.
thanks a lot for your support.
kind regards,
jonas
Scott Henninger
Jan 14, 2013, 11:22:47 AM1/14/13
to TopBraid Suite Users
Jonas; From the D2RQ Help page, the next step is to follow the link
titled "Working with MySQL or Microsoft SQL Server Databases.". This
takes you to Help
> Working with Data Back Ends > Working with RDF Databases > Working with Relational Databases > Working with MySQL or Microsoft SQL Server Databases that has specific instructions for wrapping your SQL Server driver jar for Equinox.
-- Scott
titled "Working with MySQL or Microsoft SQL Server Databases.". This
takes you to Help
> Working with Data Back Ends > Working with RDF Databases > Working with Relational Databases > Working with MySQL or Microsoft SQL Server Databases that has specific instructions for wrapping your SQL Server driver jar for Equinox.
-- Scott
Jonas
Jan 14, 2013, 11:40:20 AM1/14/13
to topbrai...@googlegroups.com
Hi Scott,
I did this and succeded. I created the sqljdbc4.bar file, renamed it (sqljdbc4.jar or sqljdbc4_equinox.jar) and put it in the dropins folder. I added the server string and the microsoft driver class and got an error as described in my previous answer (today: 5:09pm). Any further ideas?
kind regards,
Jonas
I did this and succeded. I created the sqljdbc4.bar file, renamed it (sqljdbc4.jar or sqljdbc4_equinox.jar) and put it in the dropins folder. I added the server string and the microsoft driver class and got an error as described in my previous answer (today: 5:09pm). Any further ideas?
kind regards,
Jonas
Scott Henninger
Jan 15, 2013, 9:50:19 AM1/15/13
to TopBraid Suite Users
Jonas; Can you send the full log for the error message you get. Also,
what version of SQL server drivers are you using.
It could work to install the driver at the application server level.
For Tomcat (TBL, EVN, etc.) copy the jar in the lib folder of the
Tomcat installation and re-start Tomcat. However, since you are using
TBC-SE, I am not sure how this can be accomplished in Jetty.
-- Scott
what version of SQL server drivers are you using.
It could work to install the driver at the application server level.
For Tomcat (TBL, EVN, etc.) copy the jar in the lib folder of the
Tomcat installation and re-start Tomcat. However, since you are using
TBC-SE, I am not sure how this can be accomplished in Jetty.
-- Scott
Jonas
Jan 20, 2013, 6:50:52 PM1/20/13
to topbrai...@googlegroups.com
Hi Scott,
Im using SQL 2008.
heres the full TBC Errorlog in case I use the Microsoft SQL Driver:
de.fuberlin.wiwiss.d2rq.D2RQException: Cannot determine and instantiate SQL Driver. This SQL Driver may or may not be supported. However, you may still try again by placing driver file into folder C:\devSoftware\topbraid\dropins\ and restarting TopBraid.
Database connection to jdbc:sqlserver://[servername]:1433;databaseName=kti failed (user: sa): No suitable driver found for jdbc:sqlserver://[servername]:1433;databaseName=kti (E54)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.connect(ConnectedDB.java:253)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.connection(ConnectedDB.java:180)
at de.fuberlin.wiwiss.d2rq.dbschema.DatabaseSchemaInspector.<init>(DatabaseSchemaInspector.java:47)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.schemaInspector(ConnectedDB.java:311)
at de.fuberlin.wiwiss.d2rq.mapgen.MappingGenerator.<init>(MappingGenerator.java:79)
at org.topbraidcomposer.d2rq.wizard.D2RQOptions.generateModelsFromDB(D2RQOptions.java:211)
at org.topbraidcomposer.d2rq.wizard.D2RQMetadataWizardPage.ensureLoad(D2RQMetadataWizardPage.java:221)
at org.topbraidcomposer.d2rq.wizard.D2RQMetadataWizardPage$1.handlePageChanging(D2RQMetadataWizardPage.java:172)
at org.eclipse.jface.wizard.WizardDialog$10.run(WizardDialog.java:1602)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1600)
at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:929)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1218)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:150)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:277)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: java.sql.SQLException: No suitable driver found for jdbc:sqlserver://[servername]:1433;databaseName=kti
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.connect(ConnectedDB.java:209)
... 60 more
do you need something else?
And if I use the JTDS Driver this is the error message in the log:
de.fuberlin.wiwiss.d2rq.D2RQException: Cannot instantiate SQL Driver net.sourceforge.jtds.jdbc.Driver: please place driver file jtds.jar into folder C:\devSoftware\topbraid\dropins\ and restart TopBraid.
Database connection to jdbc:jtds:sqlserver://[servername]:1433/kti failed (user: sa): No suitable driver found for jdbc:jtds:sqlserver://[servername]:1433/kti (E54)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.connect(ConnectedDB.java:253)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.connection(ConnectedDB.java:180)
at de.fuberlin.wiwiss.d2rq.dbschema.DatabaseSchemaInspector.<init>(DatabaseSchemaInspector.java:47)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.schemaInspector(ConnectedDB.java:311)
at de.fuberlin.wiwiss.d2rq.mapgen.MappingGenerator.<init>(MappingGenerator.java:79)
at org.topbraidcomposer.d2rq.wizard.D2RQOptions.generateModelsFromDB(D2RQOptions.java:211)
at org.topbraidcomposer.d2rq.wizard.D2RQMetadataWizardPage.ensureLoad(D2RQMetadataWizardPage.java:221)
at org.topbraidcomposer.d2rq.wizard.D2RQMetadataWizardPage$1.handlePageChanging(D2RQMetadataWizardPage.java:172)
at org.eclipse.jface.wizard.WizardDialog$10.run(WizardDialog.java:1602)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1600)
at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:929)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1218)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:150)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:277)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: java.sql.SQLException: No suitable driver found for jdbc:jtds:sqlserver://[servername]:1433/kti
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.connect(ConnectedDB.java:209)
... 60 more
kind regards,
Jonas
Im using SQL 2008.
heres the full TBC Errorlog in case I use the Microsoft SQL Driver:
de.fuberlin.wiwiss.d2rq.D2RQException: Cannot determine and instantiate SQL Driver. This SQL Driver may or may not be supported. However, you may still try again by placing driver file into folder C:\devSoftware\topbraid\dropins\ and restarting TopBraid.
Database connection to jdbc:sqlserver://[servername]:1433;databaseName=kti failed (user: sa): No suitable driver found for jdbc:sqlserver://[servername]:1433;databaseName=kti (E54)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.connect(ConnectedDB.java:253)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.connection(ConnectedDB.java:180)
at de.fuberlin.wiwiss.d2rq.dbschema.DatabaseSchemaInspector.<init>(DatabaseSchemaInspector.java:47)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.schemaInspector(ConnectedDB.java:311)
at de.fuberlin.wiwiss.d2rq.mapgen.MappingGenerator.<init>(MappingGenerator.java:79)
at org.topbraidcomposer.d2rq.wizard.D2RQOptions.generateModelsFromDB(D2RQOptions.java:211)
at org.topbraidcomposer.d2rq.wizard.D2RQMetadataWizardPage.ensureLoad(D2RQMetadataWizardPage.java:221)
at org.topbraidcomposer.d2rq.wizard.D2RQMetadataWizardPage$1.handlePageChanging(D2RQMetadataWizardPage.java:172)
at org.eclipse.jface.wizard.WizardDialog$10.run(WizardDialog.java:1602)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1600)
at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:929)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1218)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:150)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:277)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: java.sql.SQLException: No suitable driver found for jdbc:sqlserver://[servername]:1433;databaseName=kti
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.connect(ConnectedDB.java:209)
... 60 more
do you need something else?
And if I use the JTDS Driver this is the error message in the log:
de.fuberlin.wiwiss.d2rq.D2RQException: Cannot instantiate SQL Driver net.sourceforge.jtds.jdbc.Driver: please place driver file jtds.jar into folder C:\devSoftware\topbraid\dropins\ and restart TopBraid.
Database connection to jdbc:jtds:sqlserver://[servername]:1433/kti failed (user: sa): No suitable driver found for jdbc:jtds:sqlserver://[servername]:1433/kti (E54)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.connect(ConnectedDB.java:253)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.connection(ConnectedDB.java:180)
at de.fuberlin.wiwiss.d2rq.dbschema.DatabaseSchemaInspector.<init>(DatabaseSchemaInspector.java:47)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.schemaInspector(ConnectedDB.java:311)
at de.fuberlin.wiwiss.d2rq.mapgen.MappingGenerator.<init>(MappingGenerator.java:79)
at org.topbraidcomposer.d2rq.wizard.D2RQOptions.generateModelsFromDB(D2RQOptions.java:211)
at org.topbraidcomposer.d2rq.wizard.D2RQMetadataWizardPage.ensureLoad(D2RQMetadataWizardPage.java:221)
at org.topbraidcomposer.d2rq.wizard.D2RQMetadataWizardPage$1.handlePageChanging(D2RQMetadataWizardPage.java:172)
at org.eclipse.jface.wizard.WizardDialog$10.run(WizardDialog.java:1602)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1600)
at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:929)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1218)
at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:150)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:277)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: java.sql.SQLException: No suitable driver found for jdbc:jtds:sqlserver://[servername]:1433/kti
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at de.fuberlin.wiwiss.d2rq.sql.ConnectedDB.connect(ConnectedDB.java:209)
... 60 more
kind regards,
Jonas
Scott Henninger
Jan 25, 2013, 5:40:56 PM1/25/13
to TopBraid Suite Users
Jonas; We have confirmed this as a defect and are targeting the next
release for a fix. This should be next month and we will announce
here.
In the meantime, you can use other data back-ends that we support -
see http://www.topquadrant.com/products/supportedPlatforms4.1.html
-- Scott
> ...
>
> read more »
release for a fix. This should be next month and we will announce
here.
In the meantime, you can use other data back-ends that we support -
see http://www.topquadrant.com/products/supportedPlatforms4.1.html
-- Scott
>
> read more »
Scott Henninger
Jun 17, 2013, 12:09:22 PM6/17/13
to topbrai...@googlegroups.com
Stuart; Yes this has been resolved in TBS 4.2. Please place the attached jar file in the dropins folder for TBC-ME or a TBS server product.
For the connector information, use the following:
Database URL: jdbc:sqlserver://[server-name[\instanceName][:portNumber]];DatabaseName=[db-name][;other-property=value]
Driver Class: com.microsoft.sqlserver.jdbc.SQLServerDriver
Give that a try and let us know if that works for you. The trick may be that the class jar needs to be wrapped with some Equinox metadata to work with the TBS infrastructure.
-- Scott
For the connector information, use the following:
Database URL: jdbc:sqlserver://[server-name[\instanceName][:portNumber]];DatabaseName=[db-name][;other-property=value]
Driver Class: com.microsoft.sqlserver.jdbc.SQLServerDriver
Give that a try and let us know if that works for you. The trick may be that the class jar needs to be wrapped with some Equinox metadata to work with the TBS infrastructure.
-- Scott
On 6/12/2013 11:42 AM, Stuart Williams
wrote:
Scott,
Has this problem been resolved. I have exactly the same problem using both TBC-ME 3.7.0 and 4.2.1 (both 64 bit versions).
Many thanks
Stuart Williams.
--
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live,
TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
topbrai...@googlegroups.com
To unsubscribe from this group, send email to
topbraid-user...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Stuart Williams
Jun 18, 2013, 7:12:26 AM6/18/13
to topbrai...@googlegroups.com
On Monday, 17 June 2013 17:09:22 UTC+1, Scott Henninger wrote:
Stuart; Yes this has been resolved in TBS 4.2. Please place the attached jar file in the dropins folder for TBC-ME or a TBS server product.
For the connector information, use the following:
Database URL: jdbc:sqlserver://[server-name[\instanceName][:portNumber]];DatabaseName=[db-name][;other-property=value]
Driver Class: com.microsoft.sqlserver.jdbc.SQLServerDriver
Give that a try and let us know if that works for you. The trick may be that the class jar needs to be wrapped with some Equinox metadata to work with the TBS infrastructure.
-- Scott
Hello Scott,
I'm still suffering from this problem. I've attached a file with some screenshots of the D2RQ form panels I filled in and the response I received on hitting 'next'. For good measure you can see that I've also deployed the sqlserver.jar file exactly as you suggested :-(. The detail from the error message is below - and seems indicate a failure to either find or load the jdbc driver.
Still stuck.
Stuart
--
An error has occurred. See error log for more details.
Cannot determine and instantiate SQL Driver. This SQL Driver may or may not be supported. However, you may still try again by placing driver file into folder C:\tbc-me-4.2.1\dropins\ and restarting TopBraid.
Database connection to jdbc:sqlserver://localhost:51723;DatabaseName=ICM-RFF failed (user: cps): No suitable driver found for jdbc:sqlserver://localhost:51723;DatabaseName=ICM-RFF (E54)
Scott Henninger
Jun 23, 2013, 7:51:45 PM6/23/13
to topbrai...@googlegroups.com
Stuart; Thus far we have not been able to reproduce the problem. Is it the case that
your TQ license is up-to-date and that you
have re-started TBC-ME (multiple times, I
suspect)?
A potential issue is that the error message could mean that the driver cannot be found or that they syntax is not recognized by the driver. I.e. the message could be somewhat misleading. In terms of the syntax, take a look at this MSDN article to see if it helps:
http://msdn.microsoft.com/en-us/library/ms378428(v=sql.90).aspx
Let us know if you have any success, and if you'd like someone to contact you on troubleshooting, we'd be happy to do that.
-- Scott
A potential issue is that the error message could mean that the driver cannot be found or that they syntax is not recognized by the driver. I.e. the message could be somewhat misleading. In terms of the syntax, take a look at this MSDN article to see if it helps:
http://msdn.microsoft.com/en-us/library/ms378428(v=sql.90).aspx
Let us know if you have any success, and if you'd like someone to contact you on troubleshooting, we'd be happy to do that.
-- Scott
Stuart Williams
Jul 4, 2013, 10:02:15 AM7/4/13
to topbrai...@googlegroups.com
On Monday, 24 June 2013 00:51:45 UTC+1, Scott Henninger wrote:
Stuart; Thus far we have not been able to reproduce the problem. Is it the case that your TQ license is up-to-date and that you have re-started TBC-ME (multiple times, I suspect)?
Yes... AFAIK my license key is up-to-date and I have indeed restarted mutiple times, both TBC-ME and my whole PC.
A potential issue is that the error message could mean that the driver cannot be found or that they syntax is not recognized by the driver. I.e. the message could be somewhat misleading. In terms of the syntax, take a look at this MSDN article to see if it helps:
http://msdn.microsoft.com/en-us/library/ms378428(v=sql.90).aspx
I have a standalone installation of D2RQ on the same machine and the following works just fine:
./generate-mapping -w3c -u cps -p cps "jdbc:sqlserver://localhost:51723;databaseName=ICM-RFF"
That's exactly the same jdbc: 'URL', username and password that I've been trying to use with TBC without success.
./generate-mapping -w3c -u cps -p cps "jdbc:sqlserver://localhost:51723;databaseName=ICM-RFF"
That's exactly the same jdbc: 'URL', username and password that I've been trying to use with TBC without success.
Let us know if you have any success, and if you'd like someone to contact you on troubleshooting, we'd be happy to do that.
That would be great... I'll respond offlist with some contact details.
-- Scott
Thanks,
Stuart Williams
--
R Wiethorn
Dec 23, 2013, 9:28:17 AM12/23/13
to topbrai...@googlegroups.com
Hello,
I'm trying to connect also to a local Instance of MS SQL 2008.
Has anyone been able to do so?
I'm getting the error:
An error has occurred. See error log for more details.
Cannot instantiate SQL Driver net.sourceforge.jtds.jdbc.Driver: please place driver file jtds.jar into folder C:\tbcme-win32.win32.x86_64-4.3.1.v20131101-1317R\tbcme\dropins\ and restart TopBraid
Database connection to jdbc:jtds:sqlserver://6LJV9T1-X7:1433/Movie failed (user: tbc): No suitable driver found for jdbc:jtds:sqlserver://6LJV9T1-X7:1433/Movie (E54)
I'm attaching the screen shot of my connection object.
I've made my own sqljdbc4.bar file using the utility, and I've also downloaded the one found in this thread, but it still doesn't work.
I've also tried using LocalHost in the connection string versus the PC name (6LJV9T1-X7)
My Version: : 4.3.1.v20131101-1317R
Any other suggestions?
Thanks,
Rocky
Scott Henninger
Dec 23, 2013, 10:41:07 AM12/23/13
to topbrai...@googlegroups.com
Rocky, please take a look at the Composer Help file
at > Working with Data Back Ends > Working with Relational
Databases > Importing Relational Databases with D2RQ, and
follow the link for working with MySQl and SQL server databases.
You will need to install the driver jar for these databases, and the SQL Server jar requires an Equinox wrapper. There are instructions and pointers for downloads in the instructions.
-- Scott
You will need to install the driver jar for these databases, and the SQL Server jar requires an Equinox wrapper. There are instructions and pointers for downloads in the instructions.
-- Scott
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
Wiethorn, Robert
Dec 23, 2013, 11:14:41 AM12/23/13
to topbrai...@googlegroups.com
Hello Scott,
Yes, I’ve done that already
To connect to Microsoft SQL Server databases, you need to prepare Microsoft's JDBC Driver for SQL Server for use with the Eclipse environment using the bnd utility available here or from TopQuadrant's Resources page. The download is a zip file that includes the biz.aQute.bnd.jar utility. To use it, the following command creates a file called sqljdbc4.bar:
java -jar biz.aQute.bnd.jar wrap sqljdbc4.jar
Rename the sqljdbc4.bar file to have a .jar extension (for example, sqljdbc4_equinox.jar) and put it in the dropins folder of your TopBraid installation
Additionally, I thought I may have screwed the .bar file up, so I found one in this thread from June 17th.
To let you know, the Studio did not give the option for the connection type: jdbc:jtds:sqlserver:<server……> until I added the modified jar file.
I’ve tried different driver classes also.
-Rocky
Reply all
Reply to author
Forward
0 new messages