SQL Server JDBC Connectivity Error

Hello All,

I am using a 64 bit Windows 7 machine. I have installed SQL Server 2008 and post that SP1.
I have configured a data source using the data source ODBC Administrator.

Below is the code and and i am also attaching one image which is the screenshot of the exception !.Its been from 5,6 hours i have been trying to find the solution for this
but i am not getting one.Then thought of java ranch as it always does.I hope you guys might find once more one solution for me ! Thanks in advance !
When i test the Data Source here, it works fine. "TESTS COMPLETED SUCCESSFULLY"

However while working from Java, i get an error.

Below is the code i am using.

<%@page contentType="text/html"%>
<%@page pageEncoding="UTF-8"%>
<%@page import="java.sql.*" %>
<%@page import="java.io.*"%>

Error Message is as below :-

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception 
org.apache.jasper.JasperException: An exception occurred processing JSP page /insertcode.jsp at line 22

19:         String str2=request.getParameter("std");
20:          
21:         Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
22:         Connection con=DriverManager.getConnection("jdbc:odbc:svis");
23:         Statement stmt=con.createStatement();
24:         PreparedStatement ps=con.prepareStatement("insert into code values(?,?,?)");
25:         ps.setString(1,code);

Stacktrace:
	org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:568)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:455)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:722)

root cause 
javax.servlet.ServletException: java.sql.SQLException: [Microsoft][ODBC Driver Manager] Invalid string or buffer length
	org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:911)
	org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:840)
	org.apache.jsp.insertcode_jsp._jspService(insertcode_jsp.java:107)
	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:722)

root cause 
java.sql.SQLException: [Microsoft][ODBC Driver Manager] Invalid string or buffer length
	sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6957)
	sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7114)
	sun.jdbc.odbc.JdbcOdbc.SQLGetDataString(JdbcOdbc.java:3907)
	sun.jdbc.odbc.JdbcOdbcResultSet.getDataString(JdbcOdbcResultSet.java:5698)
	sun.jdbc.odbc.JdbcOdbcResultSet.getString(JdbcOdbcResultSet.java:354)
	sun.jdbc.odbc.JdbcOdbcConnection.buildTypeInfo(JdbcOdbcConnection.java:1503)
	sun.jdbc.odbc.JdbcOdbcConnection.initialize(JdbcOdbcConnection.java:381)
	sun.jdbc.odbc.JdbcOdbcDriver.connect(JdbcOdbcDriver.java:174)
	java.sql.DriverManager.getConnection(DriverManager.java:582)
	java.sql.DriverManager.getConnection(DriverManager.java:207)
	org.apache.jsp.insertcode_jsp._jspService(insertcode_jsp.java:86)
	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:722)

note The full stack trace of the root cause is available in the Apache Tomcat/7.0.25 logs.

Any alternate solutions using some other jdbc drivers would also be appreciated.

I don't know the answer, but here's someone with the same error. You may want to watch that thread.