JDBC Connectivity for SQL Server 2005 Windows Authentication Mode

Hi Everyone,
In my Scenario we are using SQL Server 2005 with Mixed Mode Authentication. Now we are planning to move only with Windows Authentication Mode.
We have configured DB with Window authentication mode & user id have been configured in PI channels however we are getting error. We checked microsoft site, which says Windows Authentication mode DB can not be connected using JDBC drivers.
http://support.microsoft.com/kb/313100
In this above link see Basic Connectivity Troubleshooting Section.
Please let me know if someone confirued JDBC Channel Successfuly with Windows Authentication Mode.
Thanks In Advance
Regards,
Bharathi.

I think this issue is related to the way that Vista, Windows 7 and Windows 2008 / 2008 R2 treat users who are logged on to the system with an account that is a member of the local administrators group when SQL is running locally.
If your SQL setup has left you with BUILTIN\Administrators being a member of the sysadmin server role and you start up SQL Management Studio you'd expect to be mapped to the sysadmin role if your user account is in the local administrators group, however
these OS disable this ability and when you try to connect to the database engine SQL server doesn't know you are a member of the local administrators group.
To get round this, close all your open SQL management studio windows and then start a new window by right clicking the icon in the start menu and chosing to run as administrator. This time when you try to connect to the SQL database engine, windows doesn't
"hide" the fact that you are an administrator. If you need to do this a lot you can go to the compatibility tab on the properties of the shortcut and set it to always run as administrator.
Alternatively you can install the admin tools remotely and you don't get this effect.
Tim

Similar Messages

Deploying JDBC driver for SQL Server 2005 on PI 7.1

How to Deploy JDBC driver for SQL Server 2005 on PI 7.1 on Windows 2003 server
We are in NW PI 7.1 and third party db is sql server 05.
Found How-to Guide SAP NetWeaver u201804 but unable to find for NW PI 7.1
Can any one help me on this? (looking for guide step by step procedure)
Regards
Mahesh

Hi,
Check these:
Re: Installing JDBC Drivers for PI 7.1
how to deploy MS Sql Server 2005 and 2008 jdbc driver
Mention of a SAP Note in the first link or refer this note [831162|https://service.sap.com/sap/support/notes/831162]
Regards,
Abhishek.

Deploy JDBC driver for SQL server 2005 on PI 7.1

How to deploy JDBC driver for SQL server 2005 on PI 7.1
We are in SAP NetWeaver 7.1 Oracle 10G
Third party system is SQL server 2005
There are different JDBC versions are available to download for SQL server 2005.
I am not sure about the applicable version for the PI 7.1 SP level. Again JMS Adapter needs to be deploy along with this.
Please help

Hi,
Hope this How to Guide help you.
How To Install and Configure External Drivers for the JDBC & JMS Adapters from
www.sdn.sap.com/irj/sdn/howtoguides
Regards,
Karthick.
Edited by: Karthick Srinivasan on Apr 13, 2009 4:07 PM

Error deploying JDBC driver for SQL Server 2005

Hi all
I'm trying to deploy a JDBC driver for MS SQL Server 2005 (downloaded [here|http://www.microsoft.com/downloads/details.aspx?familyid=C47053EB-3B64-4794-950D-81E1EC91C1BA&displaylang=en]). When I try to deploy it according to the instructions found [here|http://help.sap.com/saphelp_nwce10/helpdata/en/51/735d4217139041e10000000a1550b0/frameset.htm] it fails.
The error in the logs doesn't give any useful information though. It only says Error occurred while deploying component ".\temp\dbpool\MSSQL2005.sda".
Has anyone else deployed a driver for SQL Server 2005, or perhaps have any suggestions of what else I could try?
Thanks
Stuart

Hi Vladimir
That's excellent news! Thanks for the effort you've put into this. I'm very impressed with how seriously these issues are dealt with, specifically within the Java EE aspects of SAP.
May I make two suggestions on this topic:
1. Given that NWA has such granular security permissions, please could the security error be shown when it is raised? This would help immediately identify that the problem isn't actually a product error, but rather a missing security permission (and thus save us time and reduce your support calls).
2. Please could the role permissions be clearly documented (perhaps they already are, and I just couldn't find the docs?) so we know what is and isn't included in the role. The name is very misleading, as a "superadmin" is generally understood to have no limitation on their rights - so clear documentation on what is in-/excluded would be most helpful.
On a related topic, I came across another issue like this that may warrant your attention (while you're already looking into NWA security issues). I logged a support query about it (ref: 0120025231 0000753421 2008) in case you can retrieve details there (screenshots, logs, etc.). It's basically a similar security constraint when trying to create a Destination. I'm not sure if this is something you would like to include as standard permissions within the NWA_SUPERADMIN role or not, but I think it's worth consideration.
Thanks again for your help!
Cheers
Stuart

How do I install the jdbc driver for sql server 2005, in sql developer 4.0 ?

Hallo together
I need access to tables in a MS SQL Server 2005 database.
One possibility is the JDBC driver.
How do i install this driver ?
Thank you very much for your postings.

Hi,
This is from the documentation -
Database: Third Party JDBC Drivers
The Third Party JDBC Drivers pane specifies drivers to be used for connections to third-party (non-Oracle) databases, such as IBM DB2, MySQL, Microsoft SQL Server, or Sybase Adaptive Server. (You do not need to add a driver for connections to Microsoft Access databases.) To add a driver, click Add Entry and select the path for the driver:
For Microsoft SQL Server or Sybase Adaptive Server: jtds-1.2.jar, which is included in the jtds-1.2-dist.zip download
To find a specific third-party JDBC driver, see the appropriate website (for example, http://www.mysql.com for the MySQL Connector/J JDBC driver for MySQL, http://jtds.sourceforge.net/ for the jTDS driver for Microsoft SQL Server and Sybase Adaptive Server, or search at http://www.teradata.com/ for the JDBC driver for Teradata). For MySQL, use the MySQL 5.0 driver, not 5.1 or later, with SQL Developer release 1.5.
You must specify a third-party JDBC driver or install a driver using the Check for Updates feature before you can create a database connection to a third-party database of that associated type. (See the tabs for creating connections to third-party databases in the Create/Edit/Select Database Connection dialog box.)
Alternative:
As an alternative to using this preference, you can click Help, then Check for Updates to install the JTDS JDBC Driver for Microsoft SQL Server and the MySQL JDBE Driver as extensions.
Regards,
Mike

JDBC connection for SQL Server 2000

How to connect SQL Server 2000 from java?
If i can get any sites where i can get examples also fine.
Thanks in advance
Praveen.

Developer's Daily Java Education
front page | java | perl | unix | DevDirectory
Front Page
Java
Education
Pure Java
   Articles
JDBC 101: How to connect to an SQL database with JDBC
Introduction
If you're interested in connecting your Java applets and applications to standard SQL databases like Oracle, Informix, Sybase, and others, JDBC is your ticket to paradise. The combination of Java's JDBC and standard SQL makes a simple and powerful database solution. JDBC makes the simple things easy -- without making the complex tasks too difficult either.
In this first article in our series, we'll show you step-by-step how to establish a connection from your Java programs to an SQL database using JDBC. In the process we'll show you how to connect to two different databases -- Mini SQL (mSQL), and Interbase -- just so you can see how the code changes when you switch from one database to another.
Obtaining the JDBC driver
Before you start working with JDBC, you'll need a copy of the Java JDK. If you don't have it already, you can get the JDK for free at Sun's Java web site, or it will also be included with many IDE's that you can purchase, such as JBuilder or Visual Cafe.
Once you have the JDK, the next thing you need to do is to get the correct JDBC driver for your database. In most cases the JDBC driver will be provided by your database vendor. For instance, if you purchase the Interbase database, the driver will be provided with the software, or you can obtain the most recent version at http://www.interbase.com/.
(An exception to this rule is Mini SQL, or mSQL. Because it's a very low-cost database, the JDBC driver has actually been developed by a separate group of people, led by George Reese at imaginary.com. You can download the mSQL JDBC driver from the imaginary.com web site.)
Once you have the correct JDBC driver for your database, install it according to the instructions that came with it. Installation instructions will vary somewhat for each vendor.
Establishing a connection is a two-step process
Once you have the correct JDBC driver installed, establishing a connection from your Java programs to your SQL database is pretty easy.
Regardless of whether you're trying to connect to Oracle, Sybase, Informix, mSQL, or Interbase (or any other JDBC data source), establishing a connection to an SQL database with Java JDBC is a simple two-step process:
Load the JDBC driver.
Establish the connection.
We'll show you two examples just so you can see how easy it is, and how little the code changes when you migrate from one database server to another.
A Mini SQL Example
Listing 1 provides the full source code required to establish a connection to a mSQL database on a server named "www.myserver.com".
// Establish a connection to a mSQL database using JDBC.
import java.sql.*;
class JdbcTest1 {
    public static void main (String[] args) {
        try {
            // Step 1: Load the JDBC driver.
            Class.forName("com.imaginary.sql.msql.MsqlDriver");
            // Step 2: Establish the connection to the database.
            String url = "jdbc:msql://www.myserver.com:1114/contact_mgr";
            Connection conn = DriverManager.getConnection(url,"user1","password");
        } catch (Exception e) {
            System.err.println("Got an exception! ");
            System.err.println(e.getMessage());
Listing 1: This source code example shows the two steps required to establish a connection to a Mini SQL (mSQL) database using JDBC.
An Interbase Example
Listing 2 provides the full source code required to establish a connection to an Interbase database. In this example, we're connecting to a local Interbase server (i.e., the server is running on the same PC that we're running the Java code on).
// Establish a connection to an Interbase database using JDBC.
import java.sql.*;
class JdbcTest1 {
    public static void main (String[] args) {
        try {
            // Step 1: Load the JDBC driver.
            Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
            // Step 2: Establish the connection to the database.
            String url = "jdbc:odbc:contact_mgr";
            Connection conn = DriverManager.getConnection(url,"user1","password");
        } catch (Exception e) {
            System.err.println("Got an exception! ");
            System.err.println(e.getMessage());
Listing 2: This source code example shows the two steps required to establish a connection to an Interbase database using JDBC.
What's the difference?
The difference between the two source code listings is very small, so we highlighted them in a dark blue color. The only difference between connecting to the two databases is:
The name of the JDBC driver.
The URL used to connect to the database.
Everything else in the two source code listings -- except for the comment at the top -- is identical. Here's a slightly more detailed discussion of the two differences:
1. The JDBC Driver
The name of the JDBC driver will be supplied to you by your database vendor. As you can see in the class.forName() statements, these names will vary. In the first case we're using the mSQL-JDBC driver. In the second case we're using the JDBC-ODBC Bridge driver supplied with the Interbase server.
2. The URL
The syntax of the DriverManager.getConnection() method is:
DriverManager.getConnection(String url, String username, String password);
The username and password are the normal names you use to log into your database. The URL you use will again vary with the database you use. In both examples shown, we're establishing a connection to a database named contact_mgr. (We'll use this database for all of our examples in this series of JDBC articles.)
If you stick with standard SQL commands, it can be very easy to switch from one database server to another. In fact, I've heard from several developers who are using mSQL to prototype their software (because it's so inexpensive), and then switching to another commercial vendor when it's time to take their product "live".
Conclusion
Establishing a connection to an SQL database with Java JDBC is a simple, two-step process. The process is nearly identical for all SQL databases, and the only real differences are (a) the driver name, and (b) the URL used to connect to the database. Your database vendor will provide this information in their documentation.
Resources mentioned in this article
Here are a few links to resources we mentioned in this article:
Interbase
The Mini SQL (mSQL) database
The mSQL-JDBC driver at imaginary.com
[an error occurred while processing this directive]

Using SQL Server in Window Authentification mode from Coldfusion

I've received the following private message and don't know
how to answer. Can anyone else help?
quote:
Is there any some simple way to use the sql server in windows
authentication mode from coldfusion??? Other the creating the ODBC
Socket.

Hi Colum,
get these quite often, which is why I turn PM off most of the
time.
Just send them to the right forum:
http://www.adobe.com/cfusion/webforums/forum/index.cfm?forumid=1
Cheers
Craig

JDBC driver for SQL Server 2000 with windows authentication

Does anyone know of a JDBC driver for SQL Server 2000 that supports Windows Authentication, that is that a username and password does not need to be supplied when connecting to the database.

You can use the JDBC-ODBC-Bridge.
ODBC provides windows-authentication.
Hope it helps.
Freddy

JDBC driver for SQL Server

Does anyone know of a JDBC driver for SQL Server 2000 that supports Windows Authentication?
Meaning a username and password does not need to be supplied when connecting to the database.
Thanks,
James.

Yes.
JDBC-ODBC.

How Crystal Report XI connect o sql server 2005

hi
i am tring to create a report connecting to sql server 2005, however, i could not find a proper provider to connect sql server 2005, and i found Microsoft OLE DB provider for sql is only suited for sql server 2000 and earlier version, and i dont want to use ODBC connecting, so my question if there is other way to connect sql 2005 in the Crystal report XI?

Hi
Due to timing of product release dates, Crystal Reports XI was not tested with Microsoft SQL Server 2005. The changes made to connectivity drivers for MS SQL Server 2005 are significant and have been addressed in Crystal Reports XI Release 2.
As per Supported platforms document of CR XI only the below SQL servers are supported:
Microsoft SQLServer 2000 SP3 with
- ODBC MDAC 2.8
-JDBC SQLServer 2000
- OLEDB MDAC 2.8
Microsoft SQLServer 7.0 SP4 with
-ODBC MDAC 2.7
-OLEDB MDAC 2.7
However MS SQL Server 2005 is mentioned as supported in CRXIR2 as below:
MS SQL Server 2005 with
- Microsoft ODBC MDAC 2.8
-Microsoft ODBC SNAC (Native Client)
-Microsoft OLEDB MDAC 2.8
-Microsoft OLEDB SNAC (Native Client)
Contact your sales representative to obtain a copy of Crystal Reports XI Release 2. A minor product update is required for CR XI Release 2 to enable reporting off MS SQL Server 2005.
For more information regarding changes in CRXI and CRXIR2 please refer to the documentations in the link provided by Amit.
Hope this helps!!
Regards
Sourashree

JDBC connection to SQL Server 2000 Service Pack 4

Hello Everyone,
I'm trying to do a simple application which save some values into a MS SQL Server 2000 Database's Table.
The source code I've written is:
package Logging;
import com.brekeke.net.sip.sv.session.*;
import com.brekeke.net.sip.sv.session.plugins.*;
import java.io.*;
import java.util.*;
import java.sql.*;
public class Logging extends AccountingBase {
public int eventSessionStart( EventStat evstat, String[] argprm )
int ris =0;
int line=999;
try {
EventStat a;
a = evstat ;
String username;
username=a.urlCaller;
String callee;
callee=a.urlCallee;
Statement stmt = null;
try {
line=1;
Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
line=2;
Connection conn = DriverManager.getConnection("jdbc:microsoft:sqlserver://BSSQL:1433;DataBaseName=Test;User=sa;Password=biesse");
line=3;
// Create and execute an SQL statement that returns some data.
String SQL = "INSERT INTO log VALUES ('" + a.urlCaller + "','" + a.urlCallee + "')";
line=4;
stmt = conn.createStatement();
line=5;
line=stmt.executeUpdate(SQL);
line=10;
catch (Exception e) {
e.printStackTrace();
finally {
if (stmt != null) try { stmt.close(); } catch(Exception e) {}
File f = new File("c:/prova.txt");
FileOutputStream fos=new FileOutputStream(f);
PrintStream ps=new PrintStream(fos);
ps.println(line);
ps.println(a.urlCaller);
ps.println(a.urlCallee);
fos.close();
catch ( Exception ex ) {
return ris;
The problem is that into the Table no value is written, no problem compiling it and into the file prova.txt I can see only the value line=1 written!
So there should be something wrong in the connection.
I've already installed the JDBC drivers for SQL Server 2000 and I've addedd into the libraries the "msbase.jar, the mssqlserver.jar and the msutil.jar".
But nothjng written into the Database :-(
Can you help me please?
Thank you very much in advance,
Best Regards
Francesco

Hi,
Yes i am able to connect from ISQL. Only connecting from JDBC is a problem.

JDBC Driver for SQL Server 7

Is there a free JDBC Driver for SQL Server 7 available? If so, where? I created a server program that listens to a port and inserts records based on information it receives. It uses sun's JDBC:ODBC Bridge but it crashes randomly (sometimes weeks, sometimes days, sometimes hours after starting program). Each time it crashes it generates a error log file like this:
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x77f821e1
Function name=RtlEnterCriticalSection
Library=C:\WINNT\System32\ntdll.dll
Current Java thread:
     at sun.jdbc.odbc.JdbcOdbc.driverConnect(Native Method)
     at sun.jdbc.odbc.JdbcOdbc.SQLDriverConnect(Unknown Source)
     at sun.jdbc.odbc.JdbcOdbcConnection.initialize(Unknown Source)
     at sun.jdbc.odbc.JdbcOdbcDriver.connect(Unknown Source)
     at java.sql.DriverManager.getConnection(Unknown Source)
     at java.sql.DriverManager.getConnection(Unknown Source)
     at com.xxxxx.data.DataAccess.connect(DataAccess.java:20)
     at com.xxxxx.xxx.server.Broadcaster.insertOrder(POSServer.java:71)
     at com.xxxxx.xxx.server.ClientListener.run(POSServer.java:298)
Dynamic libraries:
0x00400000 - 0x00405000      C:\WINNT\system32\java.exe
0x77F80000 - 0x77FFB000      C:\WINNT\System32\ntdll.dll
0x77DB0000 - 0x77E0C000      C:\WINNT\system32\ADVAPI32.dll
0x77E80000 - 0x77F35000      C:\WINNT\system32\KERNEL32.DLL
0x77D40000 - 0x77DB0000      C:\WINNT\system32\RPCRT4.DLL
0x78000000 - 0x78046000      C:\WINNT\system32\MSVCRT.dll
0x6D420000 - 0x6D4F0000      C:\Program Files\JavaSoft\JRE\1.3.1_02\bin\hotspot\jvm.dll
Local Time = Mon May 06 10:36:33 2002
Elapsed Time = 124
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.3.1_02-b02 mixed mode)
Or this:
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x77f821e1
Function name=RtlEnterCriticalSection
Library=C:\WINNT\System32\ntdll.dll
Current Java thread:
     at sun.jdbc.odbc.JdbcOdbc.freeConnect(Native Method)
     at sun.jdbc.odbc.JdbcOdbc.SQLFreeConnect(Unknown Source)
     at sun.jdbc.odbc.JdbcOdbcDriver.closeConnection(Unknown Source)
     at sun.jdbc.odbc.JdbcOdbcConnection.close(Unknown Source)
     at sun.jdbc.odbc.JdbcOdbcConnection.finalize(Unknown Source)
     at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
     at java.lang.ref.Finalizer.runFinalizer(Unknown Source)
     at java.lang.ref.Finalizer.access$100(Unknown Source)
     at java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source)
Dynamic libraries:
0x00400000 - 0x00405000      C:\Program Files\JavaSoft\JRE\1.3.1_02\bin\javaw.exe
0x77F80000 - 0x77FFB000      C:\WINNT\System32\ntdll.dll
0x77DB0000 - 0x77E0C000      C:\WINNT\system32\ADVAPI32.dll
0x77E80000 - 0x77F35000      C:\WINNT\system32\KERNEL32.DLL
0x77D40000 - 0x77DB0000      C:\WINNT\system32\RPCRT4.DLL
Local Time = Mon May 06 10:13:59 2002
Elapsed Time = 137
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.3.1_02-b02 mixed mode)
I think this error occurs because I'm using sun's JDBC:ODBC Bridge. I'm hoping that using a different driver will solve the problem.
Thanks,
Dan

I used Sun's jdbc odbc driver for a while, with no problems, with Sql Server 7. But anyways, if you want a free type 4 driver, you can get the freetds driver at
https://sourceforge.net/projects/jtds/

Using JSP & JDBC driver for SQL Server 2000 on Red Hat

I successfully have a .jsp app running on windows server 2000 using JDBC
driver for SQL Server 2000. Which I installed in order to the following
Red Hat:
http://msdn.microsoft.com/MSDN-FILES/027/001/779/install.htm
I moved the .jsp app over to the Red Hat 9 server running Tomcat, while
keeping the MS SQL 2000 on windows. The issue I have is setting up the
JDBC driver for SQL Server 2000 on the Red Hat server.
I created a folder called /usr/java/MSSQLdriver and unzipped the tar file with
the driver for SQL Server 2000. And ran the install.ksh script.
The /usr/java/MSSQLdriver/lib has the following files within it:
msbase.jar, msutil.jar, & mssqlserver.jar
I chmod 0777 each of the *.jar files.
I then went into /etc/profile.d/tomcat.sh and adding the following:
CLASSPATH=.;/opt/msSQLjdbc/lib/msbase.jar;/opt/msSQLjdbc/lib/msutil.jar;/opt/msSQLjdbc/lib/mssqlserver.jar
Each time I login and pull up the termial I get the following error:
bash: /opt/msSQLjdbc/lib/msbase.jar: cannot execute binary file
bash: /opt/msSQLjdbc/lib/msutil.jar: cannot execute binary file
bash: /opt/msSQLjdbc/lib/mssqlserver.jar: cannot execute binary file
And can't connnect to the database within the .jsp app.
Is there anyone out there using DBC driver for SQL Server 2000 on the Red Hat server?
Michael

Sorry, I needed to correct some information of where the drivers were installed.
I created a folder called /usr/java/MSSQLdriver/new and untar the Microsoft file with the driver for SQL Server 2000. I ran the install.ksh script "sh install.ksh"
installed the driver into the default directory "/opt/msSQLjdbc".
The /opt/msSQLjdbc/lib has the following files within it:
msbase.jar, msutil.jar, & mssqlserver.jar
Michael

HotFix4 for SQL Server 2005 doesn't work

I am having problems getting a machine running SQL Server 2008 R2 (Express) to connect to a SQL Server 2005 (Full Standard Edition) DB on another machine via the LAN. It times out when connecting from a C# application. SSMS on the SQL 2008 machine
connects fine, but SSMS on the 2005 machine (connecting to a copy of the same DB on the 2008 machine) says it isn't supported and I need a hotfix.
I downloaded the hotfix link from Microsoft, but when I paste it into the Browser I get a DNS name failure for the Hotfix4 server. I don't want to paste the full link here because it is not made public by MS and you need to request it. However, the
first part of the URL is: http://hotfix4.microsoft.com/SQL%20Server%202005...etc.
I have checked out all of the obvious things in both instances (2005 AND 2008)... Both instances are configured to accept remote connections, both have TCP/IP and named pipes protocols enabled, both are running fine for local connections, both have the SQL
Browser enabled and the Computer Browser Service running on the network.
As the hot fix doesn't install, I am kind of out of ideas.
Any suggestions?
Thanks,
Pete
I used to write COBOL... now I can do anything.

SQL 2005 is out of
mainstream support:
SQL Server
2005
SP4
04/12/2011
04/12/2016
Technical support continues till 04/12/2016, yet mainstream (hotfix) support ends as of 04/12/2011; options
for hotfix support after 04/12/2011:
ð  Continue
with self-help
ð  Upgrade
to the latest supported service pack for SQL Server 2005 or SQL Server 2008 or SQL Server 2008 R2
ð  Extended
hotfix support agreement
SP4 and CU3 are still available for download, if this helps...
http://support.microsoft.com/kb/2507769
http://www.microsoft.com/en-US/download/details.aspx?id=7218
But you should update your SQL-Server..... SQL 2014 is the latest version

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider,

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider,
error: 40 - Could not open a connection to SQL Server)

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named
Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Hello,
Make sure your SQL Server service is started.
Make sure TCP\IP and names pipes protocol is enabled
Make sure you have made an exception in firewall for SQL Server connection
Make sure SQL Server browser service is enabled
Make sure you connect with correct name hostname\instance name for named instance,MSSQLSERVER for default instance and Hotname\SQLEXPRESS for express edition.
Please make sure you use port no when connecting to SQL server listeing on different port (hostname\instance ,portno)
http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

JDBC Connectivity for SQL Server 2005 Windows Authentication Mode

Similar Messages

Maybe you are looking for