List Info

Thread: OT: jdbc to MS SQL 2005 Express - Invalid Connection ConnectionOpen (Invalid Instance())




OT: jdbc to MS SQL 2005 Express - Invalid Connection ConnectionOpen (Invalid Instance())
user name
2007-07-21 22:04:26
Hi, all. Sorry for the OT post, but I know several of you
have had much 
more experience with jdbc and MS SQL (all versions) than
I...

I'm in the process of installing SonicWALL Global Management
System 4.1 
for a client. While it's essentially a Tomcat-served applet,
it requires 
either MS SQL on the back end or Oracle (yes, Oracle is my
choice, too, 
but considering the cost of this app - $4K or so - I'm
trying to recover 
part of the budget by using MS SQL 2005 Express, which is
free - but of 
course, when we're dealing with Redmond, is anything ever
really 
"free"?). While I have a pair of  Novell servers
on the LAN, Open 
Enterprise Server (and NetWare 6 and 6.5, before that) did
not bundle 
Oracle licenses as NetWare 5.x did... Pity.

Anyway, I'm at the installation phase where the app wants to
log into 
the server instance and create its db. I have a db user
account created 
for it with the dbcreator  role assigned to it. So far, so
good. 
However, the installation panel containes the following, by
default:

Database Vendor:   SQLServer
Database host/IP:   127.0.0.1
JDBC Driver:   com.microsoft.sqlserver.jdbc.SQLServerDriver
JDBC URL:   jdbc:sqlserver://localhost:1433

In addition, I need to add the following:

Database User:   GMSUser
Database password:   *****

(The user name and password - obviously - match the
credentials I set up 
previously.)

The error I'm getting is:

Invalid Connection ConnectionOpen (Invalid Instance()).

I know that SQL Express does not allow remote connections by
default. I 
have remote connections enabled, and am listening on TCP/IP
and NP 
(though the latter should not matter). I have locked the 
port down to 
the default of 1433 (it was dynamic, and gave me fits early
on in the 
process). The activity monitor for SQL shows no connection
attempts, and 
there is nothing in the event log to indicate a problem. I
have also 
tried  explicitly stating the <servername>instance in
the url, as in:

.SQLEXPRESS
localhostSQLEXPRESS
GALAXYSQLEXPRESS

I have tried with and without the port (though the port
number alone 
should negate the need to specify the instance name,
correct?).

 From a command prompt, I can get to the server with:

c:>sqlcmd -S .SQLEXPRESS

and (obviously) I can telnet to port 1433 for the expected
result (it's 
listening).

Does anyone have any clue as to what may be missing here?

TIA

-- 
Lewis
------------------------------------------------------------

Lewis G Rosenthal, CNA, CLP, CLE
Rosenthal & Rosenthal, LLC
Accountants / Network Consultants
  New York / Northern Virginia          
www.2rosenthals.com
eComStation Consultants                 
www.ecomstation.com
Novell Users Int'l      
www.novell.com/openenterpriseserver
Need a managed Wi-Fi hotspot?              
www.hautspot.com
------------------------------------------------------------



_______________________________________________
Liphp mailing list
Liphpbuoy.com
ht
tp://www.buoy.com/cgi-bin/mailman/listinfo/liphp

Re: OT: jdbc to MS SQL 2005 Express - Invalid Connection ConnectionOpen (Invalid Instance())
user name
2007-07-22 19:56:06
Well I think part of the issue is you are using a named
instance. If
its possible to install SQL Express edition as a non named
instance I
would give that a try.

It seems that depending on which jdbc driver the tomcat app
is using
you might need to specify the instance name as a parameter
in the
connect string. However, it sounds like you can't just
specify a raw
connect string,  Regardless I think the question you need to
ask is
how do I connect thisd tomcat app to a named instance of SQL
server

Info about the jtds driver:
http://confluence.atlass
ian.com/display/JIRA/Connecting+to+named+instances+in+SQL+Se
rver

Info about the microsoft sql server driver.
http://support
.microsoft.com/kb/313225

On 7/21/07, Lewis G Rosenthal <lgrosenthal2rosenthals.com> wrote:
> Hi, all. Sorry for the OT post, but I know several of
you have had much
> more experience with jdbc and MS SQL (all versions)
than I...
>
> I'm in the process of installing SonicWALL Global
Management System 4.1
> for a client. While it's essentially a Tomcat-served
applet, it requires
> either MS SQL on the back end or Oracle (yes, Oracle is
my choice, too,
> but considering the cost of this app - $4K or so - I'm
trying to recover
> part of the budget by using MS SQL 2005 Express, which
is free - but of
> course, when we're dealing with Redmond, is anything
ever really
> "free"?). While I have a pair of  Novell
servers on the LAN, Open
> Enterprise Server (and NetWare 6 and 6.5, before that)
did not bundle
> Oracle licenses as NetWare 5.x did... Pity.
>
> Anyway, I'm at the installation phase where the app
wants to log into
> the server instance and create its db. I have a db user
account created
> for it with the dbcreator  role assigned to it. So far,
so good.
> However, the installation panel containes the
following, by default:
>
> Database Vendor:   SQLServer
> Database host/IP:   127.0.0.1
> JDBC Driver:  
com.microsoft.sqlserver.jdbc.SQLServerDriver
> JDBC URL:   jdbc:sqlserver://localhost:1433
>
> In addition, I need to add the following:
>
> Database User:   GMSUser
> Database password:   *****
>
> (The user name and password - obviously - match the
credentials I set up
> previously.)
>
> The error I'm getting is:
>
> Invalid Connection ConnectionOpen (Invalid
Instance()).
>
> I know that SQL Express does not allow remote
connections by default. I
> have remote connections enabled, and am listening on
TCP/IP and NP
> (though the latter should not matter). I have locked
the  port down to
> the default of 1433 (it was dynamic, and gave me fits
early on in the
> process). The activity monitor for SQL shows no
connection attempts, and
> there is nothing in the event log to indicate a
problem. I have also
> tried  explicitly stating the
<servername>instance in the url, as in:
>
> .SQLEXPRESS
> localhostSQLEXPRESS
> GALAXYSQLEXPRESS
>
> I have tried with and without the port (though the port
number alone
> should negate the need to specify the instance name,
correct?).
>
>  From a command prompt, I can get to the server with:
>
> c:>sqlcmd -S .SQLEXPRESS
>
> and (obviously) I can telnet to port 1433 for the
expected result (it's
> listening).
>
> Does anyone have any clue as to what may be missing
here?
>
> TIA
>
> --
> Lewis
>
------------------------------------------------------------

> Lewis G Rosenthal, CNA, CLP, CLE
> Rosenthal & Rosenthal, LLC
> Accountants / Network Consultants
>   New York / Northern Virginia          
www.2rosenthals.com
> eComStation Consultants                 
www.ecomstation.com
> Novell Users Int'l      
www.novell.com/openenterpriseserver
> Need a managed Wi-Fi hotspot?              
www.hautspot.com
>
------------------------------------------------------------

>
>
> _______________________________________________
> Liphp mailing list
> Liphpbuoy.com
> ht
tp://www.buoy.com/cgi-bin/mailman/listinfo/liphp
>

_______________________________________________
Liphp mailing list
Liphpbuoy.com
ht
tp://www.buoy.com/cgi-bin/mailman/listinfo/liphp

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )