Database connection problem: "No suitable driver"

0

I edit the configuration of a database connection and get the following error message:

"Connection failed<br/>
 Error: No suitable driver"<br/>


How to solve this?

asked 25.03.2010 at 09:53

Tamas%20KIS's gravatar image

Tamas KIS
(suspended)
accept rate: 60%

One Answer:
active answersoldestnewestmost voted
0

Check if you have configured the connectin url correctly.

A correct format for Microsoft SQL Server using the jtds driver for example looks like jdbc:jtds:sqlserver://mydbserv/ivy392db. Note that it does not work if you configure only the host name. The part jtds:sqlserver is dependent on the database and driver you want to use. See the documentation of the corresponding database and or driver.

link

answered 26.11.2013 at 09:19

SupportIvyTeam's gravatar image

SupportIvyTeam ♦♦
1.4k●102●118●122
accept rate: 77%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

learn more about Markdown

Tags:

×24

Asked: 25.03.2010 at 09:53

Seen: 2,316 times

Last updated: 25.03.2010 at 09:53

Related questions

Polling time of FileStartEventBean configurable?

How to write a file as into a database field of type VARBINARY?

How can I logoff the user if he closes the browser?

getFullname(getCurrentUserName()) does not work everytime

How to set the maximum number of records per page in a SmartTable?

How to call a web service with scriptable authentication

Microsoft SQL Server transaction log file is growing and growing?

URL-GET-Parameters with Ivy 3.9

Is there a copy protection for Xpert.ivy processes available?

Date calculation is wrong