|
Problem(Abstract) |
Test Connection failed for datasource WebSphere embedded
ConnectJDBC for SQL Server DataSource on server <servername> at node
<nodename> with the following exception: java.lang.Exception:
java.sql.SQLException: [IBM][SQLServer JDBC Driver]Error establishing
socket. Connection refused: connectDSRA0010E: SQL State = 08001, Error
Code = 0. |
|
|
|
Cause |
In the SQL Server logs, ERRORLOG file, you should find an
entry that list the protocols 'listening' for SQL Server: "SQL server
listening on Shared Memory, Named Pipes."
Note that TCP is not listed in the log entry above. |
|
|
Resolving the
problem |
Run the SQL Server Network Utility and make sure TCP/IP is
configured in the Enabled protocols box:
It is also a good idea at this point to click on the Properties button and
verify the TCP port configured. This port number must match the port
configured in your Websphere datasource.
Once TCP/IP is enabled, your SQL Server ERRORLOG entry should list TCP as
an active protocol: "SQL server listening on TCP, Shared Memory, Named
Pipes."
If TCP/IP is configured as an enabled protocol but is not being logged in
the ERRORLOG as an active protocol, install the latest Microsoft SQL
Server service pack. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|