JDBC Error: Server has no instance named
-
Hello guys
I have to move the SQL 2000 SP3a DB from one Box to another. The Java Based Application connect with the jdbc:jtds:sqlserver Driver with following datasource:
<datasources>
<local-tx-datasource>
<jndi-name>TmoDS</jndi-name>
<connection-url>jdbc:jtds:sqlserver://<virtual_server>:<port>;instance=<named_instance>;databaseName=<database>;sendStringParameterAsUnicode=false</connection-url>
<driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
<user-name><user></user-name>
<password><password></password>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
<min-pool-size>50</min-pool-size>
<max-pool-size>50</max-pool-size>
<blocking-timeout-millis>5000</blocking-timeout-millis>
<new-connection-sql>SELECT 'X'</new-connection-sql>
<check-valid-connection-sql>SELECT 'X'</check-valid-connection-sql>
<prepared-statement-cache-size>0</prepared-statement-cache-size>
<set-tx-query-timeout>true</set-tx-query-timeout>
</local-tx-datasource>
</datasources>
If the DB <database> runs on the new Server, the application throws the Error:
java.sql.SQLException: Server <virtual_server> has no instance named <named_instance>.
telnet <virtual_server> <port> works fine
isql -S<virtual_server>\<named_instance>,<port> also works.
Any ideas??
Regards, Guido DBA
-
This was removed by the editor as SPAM
-
I am having the same problem with two instances. What's more unusual is that seven other instances on the server do not have this problem. The only thing the two instances have in common is the letters "sipr" in their instance names.
Incidentally, you can specify the instance IP port in the connection-url and leave the "instance" attribute off altogether. All you effectively do is bypass the sql server resolution service on UDP port 1434.
-
You need to Enable TCP/IP for that database server instance through SQL Server Configuration Manager
hth
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply