> The "Class Path" for the driver is set on "Java and JVM" > page in > Administrator. Choosing "other" for driver in "Data > Sources" and using the > JDBC driver, produces this:
> Connection verification failed for data source: NorthWind > []java.sql.SQLException: No suitable driver available for > NorthWind, please > check the driver setting in resources file, error: > com.microsoft.jdbc.SQLServerDriver > The root cause was that: java.sql.SQLException: No > suitable driver available > for NorthWind, please check the driver setting in > resources file, error: > com.microsoft.jdbc.SQLServerDriver Use Matt's suggestions to fix the one above... the one below should be reasonably easy to fix. > ----- > SQL Server driver produces this: > Connection verification failed for data source: NorthWind > []java.sql.SQLException: [Macromedia][SQLServer JDBC > Driver][SQLServer]Login > failed for user '(null)'. Reason: Not associated with a > trusted SQL Server > connection. > The root cause was that: java.sql.SQLException: > [Macromedia][SQLServer JDBC > Driver][SQLServer]Login failed for user '(null)'. Reason: > Not associated > with a trusted SQL Server connection. > same error above for an Administrator as a user too. Either check the "use trusted connection" checkbox in the dsn settings (iirc I've had mixed results with this) or make sure your username and password are included in the dsn settings or in the username and password attributes of the query. I'm not sure if the 16 character limit applies -- i've never had a 17+ character sql server password. I did some dsn testing again recently and found that I was able to use username="" password="" in a cfquery tag when the username and password were specified in the cfadmin, but db drivers being what they are I don't know that I'd say that's guaranteed to always be the case, so make sure you check both the dsn and the cfquery tag. Could also be a port issue if you're using multiple instances of SQL2k like Matt says. On this machine here I'm connecting to the server using [machinename]\[sqlinstance] -- or "turing\socrates" in the server field, rather than an ip address for instance, and port 1433. I have some vague recollection of having to set that port number in sql server, but I can't remember how or why. And just to be sure, make sure you have "NorthWind" in the database field in the dsn panel in addition to the DSN field. I'm sure you do, just covering all the bases. :) The onTap framework includes some additional db metadata features which use the JDBC interfaces directly and makes it necessary to include a username and password in the framework settings rather than relying solely on the dsn (which iirc also produces this error, although it doesn't occur in a cfquery tag). In all honesty, if I could avoid the dsn all-together I would -- the more I can encapsulate into the code the better imho, as it makes the code more portable. s. isaac dealey 214.823.9345 new epoch : isn't it time for a change? add features without fixtures with the onTap open source framework http://www.turnkey.to/ontap ----------------------------------------------- To post, send email to [EMAIL PROTECTED] To unsubscribe: Send UNSUBSCRIBE to [EMAIL PROTECTED] To subscribe / unsubscribe: http://www.dfwcfug.org
