SupportSupport

Thanks for reporting this.

Which JDBC driver do you use, and what does the URL look like?

Can you please enable debugging and post or mail the output for the connection attempt to us?

http://www.dbvis.com/products/dbvis/doc/faq/#4.14

Best Regards,
Hans

Where is the separate thread for the problem "Malformed reply from SOCKS server"?
I'm getting the same error in connecting to any SQL Server 2008 databases. Same URL, user name, password were working with v7.15 of dbvis.

Why is there a SOCKS error to start with? I specified http settings only in proxy settings of tool properties (assuming those settings are used in this context)

Please see the debug window output here:

---

Product Information

---

Product: DbVisualizer Personal 720.1638
Build: #1638 (2011/05/02 13:47)
Java VM: Java HotSpot(TM) Client VM
Java Version: 1.6.0_24
Java Vendor: Sun Microsystems Inc.
OS Name: Windows XP
OS Arch: x86
OS Version: 5.1

---

Connected Databases

---

---

Debug Printouts

---

11:03:35 [DEBUG Thread-12 G.?] Connecting: dbInstanceName_prod_userId
11:03:35 [DEBUG Thread-12 L.?] Loading class using dynamic ClassLoader: net.sourceforge.jtds.jdbc.Driver
11:03:35 [DEBUG Thread-12 L.?] Loading class using dynamic ClassLoader: net.sourceforge.jtds.jdbc.Driver
11:03:35 [DEBUG pool-2-thread-3 D.?] RootConnection: Driver.acceptsURL("jdbc:jtds:sqlserver://dbServerName:1433/dbInstanceName")
11:03:35 [DEBUG pool-2-thread-3 D.?] RootConnection: Driver.connect("jdbc:jtds:sqlserver://dbServerName:1433/dbInstanceName", {user=userId, password=userPassword, includeSynonyms=true})
java.sql.SQLException: Network error IOException: Malformed reply from SOCKS server
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:410)
at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)
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 com.onseven.dbvis.c.B.D.?(Z:1548)
at com.onseven.dbvis.c.B.F$A.call(Z:2838)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
SQLException: SQLState(08S01)
11:05:35 [DEBUG pool-2-thread-3 D.?] RootConnection: EXCEPTION -> java.sql.SQLException: Network error IOException: Malformed reply from SOCKS server

Hi,


The error message comes from the driver, and it is common that error messages from a driver when a connection cannot be made are misleading.

DbVisualizer Proxy settings are not used for setting up a connection to a database.


Have you edited the server name in the log output? If not, is it really called "dbServerName" and listens on port 1433?

One potential cause for this problem is if you switched from "Database URL" to "Server Info" in the Connection tab, and entered incorrect values in the Database Server and/or the Database Port fields. Can this be the problem in your case?

Best Regards,
Hans

Thanks Hans!

Have you edited the server name in the log output? If not, is it really called "dbServerName" and listens on port 1433?
Yes, I did edit the log output to obscure the db names, user id etc.

One potential cause for this problem is if you switched from "Database URL" to "Server Info" in the Connection tab, and entered incorrect values in the Database Server and/or the Database Port fields. Can this be the problem in your case?
I have been using Database URL only so far and came to know that I can use Server Info radio button after seeing your response However I got the same error with either of them (after duly setting the server, db names etc)

Hi Hans,

I disabled the proxy (which said to use http instead of socks), but it didn't change the inability to connect to Sybase or DB2:

That's the DB2 log.

An error occurred while establishing the connection:

Long Message:
[jcc][t4][2043][11550][3.57.82] Exception java.net.SocketException: Error opening socket to server xxx.xxx.xxx.xxx/xxx.xxx.xxx.xxx on port 50,240 with message: Malformed reply from SOCKS server. ERRORCODE=-4499, SQLSTATE=08001

Details:
   Type: com.ibm.db2.jcc.am.yn
   Error Code: -4499
   SQL State: 08001

I'm getting the same SOCKS error (Malformed reply from SOCKS server) with dbvisgui.bat.
Disabling proxy didnt have any effect on the apps launched using regular dbvis and this dbvisgui.bat file, as I got the same error again. We are behind a corporate firewall.

java.sql.SQLException: Network error IOException: Malformed reply from SOCKS server
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:410)
at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.onseven.dbvis.c.B.D.?(Z:1548)
at com.onseven.dbvis.c.B.F$A.call(Z:2838)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
SQLException: SQLState(08S01)

I sent the files to the email id you suggested.

Could it be a problem if I have both dbvis 7.15 and EAP versions installed?

I have not overriden anything except giving the command line argument -prefsdir C:\java\db\dbvis-prefs-backup\.dbvis for EAP version, and a different prefs directory for 7.15 version.

Thanks Roger

Edited by: madhav on May 6, 2011 5:57 PM

Edited by: madhav on May 6, 2011 5:57 PM

Hans,

it works with 720.1640. Thanks for the fix.

Regards,
Freewater