 |
|
 |
|
Next: Wrong data from: getMetadata().getTableName(i) me..
|
| Author |
Message |
External

Since: Mar 25, 2008 Posts: 37
|
(Msg. 1) Posted: Tue Mar 25, 2008 10:38 pm
Post subject: Cannot connect to my SQL 2005 server using JDBC - can any diagnostic tool tell me what the problem is? Archived from groups: microsoft>public>sqlserver>jdbcdriver (more info?)
|
|
|
Gurus,
Running SQL Server 2005 SP2 and using named instances. I have an
application which uses JDBC to connect to my SQL server. Connectivity using
ODBC works just fine as I can test it successfully using a UDL file.
However, this application fails to connect to my server every time and I am
not sure what troubleshooting tool I can use to narrow the problem. To
clarify, I can connect remotely to my SQL server using a UDL file by any
combination of name or IP, named pipes or TCP/IP, SQL or Windows
Authentication. In sum, I cannot connect to my SQL 2005 server using JDBC -
can any diagnostic tool tell me what the problem is?
--
Spin >> Stay informed about: Cannot connect to my SQL 2005 server using JDBC - can any .. |
|
| Back to top |
|
 |  |
External

Since: Nov 21, 2006 Posts: 24
|
(Msg. 2) Posted: Tue Apr 01, 2008 9:00 pm
Post subject: RE: Cannot connect to my SQL 2005 server using JDBC - can any diagnostic tool tell me what the problem is? [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
Hey Spin,
All JDBC drivers are limited to using TCP/IP, so if you can connect properly with a UDL specifying tcp:servername, then you should be OK.
However, I have seen some scenarios where not every JDBC drivers handles problems with the UDP broadcast from the SQL Browser service
appropriately. What driver are you using?
What happens if you hard code the port number in the connection string?
Evan
--------------------
>From: "Spin"
>Newsgroups: microsoft.public.sqlserver.jdbcdriver
>Subject: Cannot connect to my SQL 2005 server using JDBC - can any diagnostic tool tell me what the problem is?
>Date: Tue, 25 Mar 2008 22:38:47 -0400
>Lines: 15
>Message-ID:
>Reply-To: "Spin"
>Mime-Version: 1.0
>Content-Type: text/plain;
> format=flowed;
> charset="iso-8859-1";
> reply-type=original
>Content-Transfer-Encoding: 7bit
>X-Trace: individual.net /j9PrmZkEIFfhIEEN3Z2BAdFjD3GXFZeFrLt+/VLF2I8TYoW2t
>Cancel-Lock: sha1:KuDO2DK97g+arT3aofLOly6EP2k=
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
>Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!newsfeed-0.progon.net!
progon.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.jdbcdriver:476
>X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
>
>Gurus,
>
>Running SQL Server 2005 SP2 and using named instances. I have an
>application which uses JDBC to connect to my SQL server. Connectivity using
>ODBC works just fine as I can test it successfully using a UDL file.
>However, this application fails to connect to my server every time and I am
>not sure what troubleshooting tool I can use to narrow the problem. To
>clarify, I can connect remotely to my SQL server using a UDL file by any
>combination of name or IP, named pipes or TCP/IP, SQL or Windows
>Authentication. In sum, I cannot connect to my SQL 2005 server using JDBC -
>can any diagnostic tool tell me what the problem is?
>
>--
>Spin
>
>
Evan T. Basalik
This posting is provided “AS IS” with no warranties, and confers no rights. >> Stay informed about: Cannot connect to my SQL 2005 server using JDBC - can any .. |
|
| Back to top |
|
 |  |
External

Since: Jan 19, 2008 Posts: 206
|
(Msg. 3) Posted: Tue Apr 01, 2008 9:46 pm
Post subject: RE: Cannot connect to my SQL 2005 server using JDBC - can any dia [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
Evan;
Do you have any references on which version of the Microsoft JDBC driver
works with SQLBrowser from Linux/Unix? I don't know if KB article
http://support.microsoft.com/kb/313225 is dated. But it says the following:
> To connect to a named instance through the Microsoft SQL Server
> 2000 Driver for JDBC, you must specify the port number that is
> associated with the named instance, instead of the name of the
> named instance as shown earlier.
This seems to suggest that whatever version of the JDBC driver the article
is talking about doesn't talk to UDP 1434 to retrieve the port automatically.
Linchi
"Evan T. Basalik (MSFT)" wrote:
> Hey Spin,
>
> All JDBC drivers are limited to using TCP/IP, so if you can connect properly with a UDL specifying tcp:servername, then you should be OK.
>
> However, I have seen some scenarios where not every JDBC drivers handles problems with the UDP broadcast from the SQL Browser service
> appropriately. What driver are you using?
>
> What happens if you hard code the port number in the connection string?
>
> Evan
>
>
> --------------------
> >From: "Spin"
> >Newsgroups: microsoft.public.sqlserver.jdbcdriver
> >Subject: Cannot connect to my SQL 2005 server using JDBC - can any diagnostic tool tell me what the problem is?
> >Date: Tue, 25 Mar 2008 22:38:47 -0400
> >Lines: 15
> >Message-ID:
> >Reply-To: "Spin"
> >Mime-Version: 1.0
> >Content-Type: text/plain;
> > format=flowed;
> > charset="iso-8859-1";
> > reply-type=original
> >Content-Transfer-Encoding: 7bit
> >X-Trace: individual.net /j9PrmZkEIFfhIEEN3Z2BAdFjD3GXFZeFrLt+/VLF2I8TYoW2t
> >Cancel-Lock: sha1:KuDO2DK97g+arT3aofLOly6EP2k=
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
> >Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!newsfeed-0.progon.net!
> progon.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
> >Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.jdbcdriver:476
> >X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
> >
> >Gurus,
> >
> >Running SQL Server 2005 SP2 and using named instances. I have an
> >application which uses JDBC to connect to my SQL server. Connectivity using
> >ODBC works just fine as I can test it successfully using a UDL file.
> >However, this application fails to connect to my server every time and I am
> >not sure what troubleshooting tool I can use to narrow the problem. To
> >clarify, I can connect remotely to my SQL server using a UDL file by any
> >combination of name or IP, named pipes or TCP/IP, SQL or Windows
> >Authentication. In sum, I cannot connect to my SQL 2005 server using JDBC -
> >can any diagnostic tool tell me what the problem is?
> >
> >--
> >Spin
> >
> >
>
> Evan T. Basalik
> This posting is provided “AS IS” with no warranties, and confers no rights.
>
>
> >> Stay informed about: Cannot connect to my SQL 2005 server using JDBC - can any .. |
|
| Back to top |
|
 |  |
External

Since: Mar 25, 2008 Posts: 37
|
(Msg. 4) Posted: Wed Apr 02, 2008 12:42 pm
Post subject: Re: Cannot connect to my SQL 2005 server using JDBC - can any dia [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"Linchi Shea" wrote in message
> Evan;
>
> Do you have any references on which version of the Microsoft JDBC driver
> works with SQLBrowser from Linux/Unix? I don't know if KB article
> http://support.microsoft.com/kb/313225 is dated. But it says the
> following:
>
>> To connect to a named instance through the Microsoft SQL Server
>> 2000 Driver for JDBC, you must specify the port number that is
>> associated with the named instance, instead of the name of the
>> named instance as shown earlier.
>
> This seems to suggest that whatever version of the JDBC driver the article
> is talking about doesn't talk to UDP 1434 to retrieve the port
> automatically.
>
> Linchi
JDBC driver - this is unrelated to Java correct? Just doing a sanity check
here. >> Stay informed about: Cannot connect to my SQL 2005 server using JDBC - can any .. |
|
| Back to top |
|
 |  |
External

Since: Nov 21, 2006 Posts: 24
|
(Msg. 5) Posted: Tue Apr 08, 2008 8:00 pm
Post subject: RE: Cannot connect to my SQL 2005 server using JDBC - can any dia [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
That article was specific to the SQL Server 2000 JDBC driver. The SQL Server 2005 JDBC driver will talk to SQL Browser just fine (assuming the correct
ports are opened up).
Evan
--------------------
>Thread-Topic: Cannot connect to my SQL 2005 server using JDBC - can any dia
>thread-index: AciUfHL7n6GoC2poQGa6q15tSHrQFw==
>X-WBNR-Posting-Host: 67.84.177.208
>From: =?Utf-8?B?TGluY2hpIFNoZWE=?=
>References:
>Subject: RE: Cannot connect to my SQL 2005 server using JDBC - can any dia
>Date: Tue, 1 Apr 2008 21:46:00 -0700
>Lines: 77
>Message-ID:
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
>Newsgroups: microsoft.public.sqlserver.jdbcdriver
>Path: TK2MSFTNGHUB02.phx.gbl
>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.jdbcdriver:481
>NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
>X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
>
>Evan;
>
>Do you have any references on which version of the Microsoft JDBC driver
>works with SQLBrowser from Linux/Unix? I don't know if KB article
>http://support.microsoft.com/kb/313225 is dated. But it says the following:
>
>> To connect to a named instance through the Microsoft SQL Server
>> 2000 Driver for JDBC, you must specify the port number that is
>> associated with the named instance, instead of the name of the
>> named instance as shown earlier.
>
>This seems to suggest that whatever version of the JDBC driver the article
>is talking about doesn't talk to UDP 1434 to retrieve the port automatically.
>
>Linchi
>
>"Evan T. Basalik (MSFT)" wrote:
>
>> Hey Spin,
>>
>> All JDBC drivers are limited to using TCP/IP, so if you can connect properly with a UDL specifying tcp:servername, then you should be OK.
>>
>> However, I have seen some scenarios where not every JDBC drivers handles problems with the UDP broadcast from the SQL Browser service
>> appropriately. What driver are you using?
>>
>> What happens if you hard code the port number in the connection string?
>>
>> Evan
>>
>>
>> --------------------
>> >From: "Spin"
>> >Newsgroups: microsoft.public.sqlserver.jdbcdriver
>> >Subject: Cannot connect to my SQL 2005 server using JDBC - can any diagnostic tool tell me what the problem is?
>> >Date: Tue, 25 Mar 2008 22:38:47 -0400
>> >Lines: 15
>> >Message-ID:
>> >Reply-To: "Spin"
>> >Mime-Version: 1.0
>> >Content-Type: text/plain;
>> > format=flowed;
>> > charset="iso-8859-1";
>> > reply-type=original
>> >Content-Transfer-Encoding: 7bit
>> >X-Trace: individual.net /j9PrmZkEIFfhIEEN3Z2BAdFjD3GXFZeFrLt+/VLF2I8TYoW2t
>> >Cancel-Lock: sha1:KuDO2DK97g+arT3aofLOly6EP2k=
>> >X-Priority: 3
>> >X-MSMail-Priority: Normal
>> >X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
>> >Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!newsfeed-
0.progon.net!
>> progon.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
>> >Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.jdbcdriver:476
>> >X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
>> >
>> >Gurus,
>> >
>> >Running SQL Server 2005 SP2 and using named instances. I have an
>> >application which uses JDBC to connect to my SQL server. Connectivity using
>> >ODBC works just fine as I can test it successfully using a UDL file.
>> >However, this application fails to connect to my server every time and I am
>> >not sure what troubleshooting tool I can use to narrow the problem. To
>> >clarify, I can connect remotely to my SQL server using a UDL file by any
>> >combination of name or IP, named pipes or TCP/IP, SQL or Windows
>> >Authentication. In sum, I cannot connect to my SQL 2005 server using JDBC -
>> >can any diagnostic tool tell me what the problem is?
>> >
>> >--
>> >Spin
>> >
>> >
>>
>> Evan T. Basalik
>> This posting is provided “AS IS” with no warranties, and confers no rights.
>>
>>
>>
>
Evan T. Basalik
This posting is provided “AS IS” with no warranties, and confers no rights. >> Stay informed about: Cannot connect to my SQL 2005 server using JDBC - can any .. |
|
| Back to top |
|
 |  |
External

Since: Nov 21, 2006 Posts: 24
|
(Msg. 6) Posted: Tue Apr 08, 2008 8:03 pm
Post subject: Re: Cannot connect to my SQL 2005 server using JDBC - can any dia [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
Maybe I don't understand the question, but...
The JDBC driver is what Java uses to talk to databases. There are different JDBC drivers out there for all the different databases.
Evan
--------------------
>From: "Spin"
>Newsgroups: microsoft.public.sqlserver.jdbcdriver
>Subject: Re: Cannot connect to my SQL 2005 server using JDBC - can any dia
>Date: Wed, 2 Apr 2008 12:42:37 -0400
>Lines: 25
>Message-ID:
>References: <033DEBFD-87A2-4761-8547-2BFFAECCC547
@microsoft.com>
>X-Trace: individual.net hQaueHn23cpzwx67rWEO8w6DdehdDDdInBkCHGjRui333x6vKN
>Cancel-Lock: sha1:Evah25caL63ImEj61VmN7EYs8Io=
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
>X-RFC2646: Format=Flowed; Original
>Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!news-out.cwix.com!newsfeed.cwix.com!image.surnet.ru!fu-
berlin.de!uni-berlin.de!individual.net!not-for-mail
>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.jdbcdriver:482
>X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
>
>"Linchi Shea" wrote in message
>
>> Evan;
>>
>> Do you have any references on which version of the Microsoft JDBC driver
>> works with SQLBrowser from Linux/Unix? I don't know if KB article
>> http://support.microsoft.com/kb/313225 is dated. But it says the
>> following:
>>
>>> To connect to a named instance through the Microsoft SQL Server
>>> 2000 Driver for JDBC, you must specify the port number that is
>>> associated with the named instance, instead of the name of the
>>> named instance as shown earlier.
>>
>> This seems to suggest that whatever version of the JDBC driver the article
>> is talking about doesn't talk to UDP 1434 to retrieve the port
>> automatically.
>>
>> Linchi
>
>JDBC driver - this is unrelated to Java correct? Just doing a sanity check
>here.
>
>
>
>
Evan T. Basalik
This posting is provided “AS IS” with no warranties, and confers no rights. >> Stay informed about: Cannot connect to my SQL 2005 server using JDBC - can any .. |
|
| Back to top |
|
 |  |
External

Since: Mar 25, 2008 Posts: 37
|
(Msg. 7) Posted: Tue Apr 08, 2008 11:00 pm
Post subject: Re: Cannot connect to my SQL 2005 server using JDBC - can any dia [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
|
|
| Back to top |
|
 |  |
| Related Topics: | JDBC 1.2 client against SQL 2005 JDBC 2.0 server? - We need to the server-side of this driver by running xa_install.sql. The client app running on WebSphere (on an app server) will be using version 1.2 of the JDBC driver. Is it safe to install the 2.0 version on the database server, or should we stick...
2005 JDBC Driver: Integreated Authentication - Good evening, I am trying to get the new 2005 JDBC driver to use integrated authentication. I have tried adding the parameter -Djava.library.path=C:\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_<version>\enu\auth\x86 to the vm but I get an er...
JDBC Driver Support for SQL 2005 Schemas? - Anyone know if the JDBC driver supports SQL 2005 schemas? If so, which version. When we use the JDBC driver, it seems to report back database roles instead of schemas, SQL 2000 style. Thanks
Codepage 850 and MS SQL 2005 JDBC 1.1 Driver - This apparently is not supported in 1.1 (using JDK 1.4): (com.microsoft.sqlserver.jdbc.SQLServerException) com.microsoft.sqlserver.jdbc.SQLServerException: Codepage 850 is not supported by the Java environment. Our datatbase is required to use this..
Which Jdbc for SQL Server 2000? - I thought I asked this question before, but I can't find it in the list so I'm trying again. I'm developing an application on Java JDSE 1.5 for Windows from Sun Microsystems. I need to connect and interact with an MS SQL Server 2000. Who's JDBC package... |
|
You can post new topics in this forum You can reply to topics in this forum You can edit your posts in this forum You can delete your posts in this forum You can vote in polls in this forum
|
|
|
|
 |
|
|