This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Hello, When i like to make a JDBC connection, i have recived the next error: I have the .jar's in my CLASSPATH. *********** Exception occurred ************ at 12:06 PM on Nov 22, 2006 java.lang.NoClassDefFoundError: com/microsoft/jdbc/base/BaseDriver at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at org.netbeans.modules.db.explorer.DbDriverManager.getDriverInternal(DbDriverManager.java:210) at org.netbeans.modules.db.explorer.DbDriverManager.getConnection(DbDriverManager.java:97) at org.netbeans.modules.db.explorer.DatabaseConnection$2.run(DatabaseConnection.java:500) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:499) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:932) Bye.
Created attachment 36204 [details] log of NetBeans
Reporter: if you are unsure which component to use when filing a bug, please use 'ide' and it will be reassigned for you.
The Microsoft JDBC driver is made of three jar files (msbase, mssqlserver and msutil). Have you addem them all when registering the driver in the Runtime tab? Also note that NetBeans recommends the jTDS driver for Microsoft SQL Server. If you prefer a Microsoft driver use the 2005 driver.
Probably caused by user error as described in desc4, so closing.