I have java and .net applications running on an application server using Microsoft Windows Server 2003, Enterprise Edition. They migrate to another Windows 2008 application server with a 64-bit machine.
All applications connect to the same SQL Server 2005 database in a named instance.
So far, I have tried to move applications as they are, with no changes to the configuration files, from the old field to the new one.
On the new application server, neither Java nor .net applications connect to the database (named instance).
JDBC error message: "Could not connect to the named instance. Error: java.net.SocketTimeoutException: receiving timeout."
.Net error message: "A network-related or specific instance error occurred while establishing a connection to SQL Server. The server could not be found or was unavailable."
If I change the database configuration to one that is not on the named instance, it works on the new application server.
The database is configured correctly because we were able to connect to the old application server. I can ping the database server from a new application server.
Is there a reason this will not work on the new application server?
java connection string: "jdbc: microsoft: sqlserver: // [dbservername]; SelectMethod = Cursor; instanceName = [dbinstance]"
Connection string.net: "Server = [dbservername] \ [dbinstance]; Database = Risk_DB; Uid = [user]; Pwd = [pwd];"
UPDATE
. SQL Server Management Studio, . Management Studio, [_] [instancename], " SQL Server..." , [_], [ ]. , ?
# 2. network/network/network. Windows . Presto, [dbservername]\[dbinstance] Management Studio, .