I want make use of SQL Server Instance, while connecting

hi,
i have developed Code using normal conditions,Like i have not checked for SQL Server Instances, my client need to b use Instances of the SQL Server, so i need to change the code.
can any one help Regarding SQL Server Instances Connection coding.
Ex: jdbc:JSQLConnect://servername\Instance_Name
can any one help out me, it would be grate help for me,
thanks.

Read the JDBC tutorial and read the SQL Server JDBC driver documentation.
http://www.google.com/search?q=jdbc+tutorial+site:sun.com
http://www.google.com/search?q=sql+server+jdbc+driver+site:microsoft.com

Similar Messages

SQL server instance not getting detected during SCOM 2012 R2 Installation

Hi All,
This is related to the below thread which i created. But i wanted to test this practically in a LAB equipment
https://social.technet.microsoft.com/Forums/en-US/96feece7-c168-4f42-b62e-4c0c20f8d525/does-scom-2012-2012-r2-setup-detect-a-sql-instance-of-a-sql-server-in-the-same-network-which-is-in?forum=operationsmanagerdeployment
So i want to install SCOM in my domain, But i want to use a SQL server in my network which is in another domain.
So i have 4 server machines as below:
SERVER_DC1 - Domain controller of 1st domain.
SERVER_DC2 - Domain controller of 2nd domain.
SERVER_SQL - SQL server 2012 Enterprise installed for SCOM but is in Domain 1
Server_SCOM - I want to install SCOM in this but which is in domain 2
I created a trust relation between 2 domains with a Forest trust 2 way transitive.
I have created a security group and added that as SQL Admin during the installation. Later i added one Domain administrator account from Domain 2 to this security group.
When i do a installation in SERVER_DC1 for testing the SQL instance is being detected as below.
When i do the installation in Server_SCOM which is in another domain then the instance is not getting detected.
I have turned off windows firewall in all the machines.
Before creating the trust i ran the setup in Server_SCOM then it was giving me a warning saying it is not able to access the SQL server due to permission issues.
After giving permissions my instance is not at all getting detected.
Can any one help plz.
Gautam.75801

Hi Yan Li,
Really a helpful post. I tested the connection. I connected to the SQL server in Domain A using a server in domain B logged in as a domain B user to whom the SQL permissions are provided. The result says It was successful.
Below is the screenshot.
I don't understand why is it not getting detected in the SCOM setup.
But 1 more important thing which i forgot to mention.
When i log on to the server in which i want to install SCOM in domain B, But by using Domain A's user account (Added as a local user in SCOM server in domain B), Then the Instance is getting detected.
Below is a screenshot of that.
So has any one faced such a type of issue ?
Gautam.75801

Problems with deploying cmproster example using ms sql server as database

hi to all,
im new to ejb and i like to learn by doing the examples given in the j2ee tutorial. i want to deploy the cmproster with a bit of modification...i want to use ms sql server as the database..i have configured the data source and connection pools correctly..and when i run the Client Application there is no error. The database seems fine it was populated correctly..only some of the values become null..
Here is the sample output from the client app:
P7 null null 777.0
P8 null null 65.0
P10 null null 100.0
P6 null null 555.0
P9 null null 100.0
The two columns should be strings...i look at the server.log and there where errors:
Error while getting value from resultset at index 2 as resultType 21columnSqlType=JDO76: 12.Exception java.sql.SQLException: [Microsoft][ODBC SQL Server Driver]Invalid Descriptor Index
I think thats the culprit...Can anyone help me on this? tnx
Note:
By the way im using sun.jdbc.odbc.JdbcOdbcDriver for the jdbc driver
Thanx
-oyam

Hi Michael,
At this time SQL Server 2000 is not certified for WLCS 3.5. Since the
schema has changed between 3.2 and 3.5, running the 3.2 scripts is not a
good idea.
I can tell you that certification is in progress for SQL Server 2000. Your
best bet is to contact your Sales Representative to get an idea of when
certification might be coming.
I hope this helps.
- Ginny
"Michael Schulz" <[email protected]> wrote in message
news:[email protected]..
I'm using WebLogic 6.0sp1 with Commerce Server 3.5 and I've successfully
installed the demo. I would like to create another commerce server
installation, this time using Microsoft SQL Server 2000 as the database
instead of Cloudscape. I've downloaded and installed the BEA jDriver
for MS SQL 7/2000 and tested it using dbping. My question is: where are
the db scripts for creating and populating the commerce database? I've
found the WLCS_320_DB_DDL_1.1.zip file on the BEA downloads site, but
I'm concerned that this schema is for Version 3.20 of Commerce Server.
Is there a similar file for WLCS 3.50? If not, is it safe to use this
one?
If this is posted in the wrong place, please let me know and I'll repost
to the appropriate newsgroup as required.
Sincerely,
Michael Schulz

TF400525: Make sure the SQL Server Reporting Services service for this instance is running.

I am trying to install TFS 2012 update 4 on single server installation.
I am getting below error:
TF400525: Make sure the SQL Server Reporting Services service for this instance is running.

Hi CFSA,
Thanks for your post.
If you want install TFS 2012 Server with Reporting Server, you must ensure the provided Reporting Services is running first.
As Daniel said, please check that in SQL Server Configuration Manager to ensure Reporting Services is installed and running.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Using a SQL Server database instance for repository

Hi,
My customer is using a non-default instance on SQL server as their database and want to place the repository here. There are no problems creating and connecting to the repository from the Designer. I simply define the server as "SERVER\INSTANCE" and I can connect OK.
The problem occurs in the Management Console, when I try to create an entry for this new repository. The Add process returns a Java error, telling me that the connection is being refused. I have checked, and re-checked, that all of the inputs are correct. I believe that this has something to do with the fact that the repository is an instance, rather than just the default database instance.
I have tried various differing ways of entering the server and database strings, with no positive result. I tried entering the following in the Server and Database entry fields:
SERVER\INSTANCE with DATABASENAME
SERVER
INSTANCE with DATABASENAME
SERVER/INSTANCE with DATABASENAME
INSTANCE@SERVER with DATABASENAME
SERVER.INSTANCE with DATABASENAME
SERVER with INSTANCE\DATABASENAME
SERVER with INSTANCE.DATABASENAME
All give an error - some return a "connection refused", some return a "server not found" error.
Any recommendation short of re-installing the database as a default instance would be appreciated.
DI and SQL Server reside on the same server running Windows 2003 Server R2 SE with SP2. Management Console runs in Apache Tomcat 5.5 on the same box.
Regards,
Derek.
Edited by: Derek Stobbart on Oct 1, 2008 5:14 PM

Hi Derek,
The Management Console does not support the \INSTANCE syntax -- the reason is that it uses JDBC to connect to repositories. When you add a SQL Server repository to the Management Console, note that it is asking you for hostname, port, and database name. You will need to provide it the port that the instance is running on (e.g. default=1433). You can get this from the person who administers the SQL Server instance.
Thanks,
~Scott

Problem using DG4ODBC with named SQL Server instance

I am running DG4ODBC on a 64 bit LINUX machine with the Microsoft SQL Server driver installed. I have successfully tested this with a SQL Server instance that was not named (GENERALI_DSN).The named instance gives the following when trying to query:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[unixODBC][Microsoft][SQL Server Native Client 11.0]Login timeout expired {HYT00}[unixODBC][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. {08001,NativeErr = -1}[unixODBC][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. {08001,NativeErr = -1}
ORA-02063: preceding 2 lines from DEVMISC
odbc.ini
[GENERALI_DSN]
Driver                  = SQL Server Native Client 11.0
Server                  = CLTDMJCWBYZ.eu.scor.local
User                    = everest
Password                = everest
Database                = Everest_Generali
[DEVMISC_DSN]
Driver                  = SQL Server Native Client 11.0
Server                  = [USVCLTDEVSQL02\DEVMISC]
User                    = link_user
Password                = password1
Database                = DBA
initDG4ODBC2.ora
# HS init parameters
HS_FDS_CONNECT_INFO = DEVMISC_DSN
HS_FDS_TRACE_LEVEL = DEBUG
HS_FDS_SHAREABLE_NAME = /usr/lib64/libodbc.so
# ODBC specific environment variables
set ODBCINI=/home/oracle/.odbc.ini
listener.ora
SID_LIST_LISTENER_GW =
   (SID_LIST =
      (SID_DESC =
       (SID_NAME=DG4ODBC)
      (ORACLE_HOME=/home/oracle/product/11.2.0)
      (ENV=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micro
soft/sqlncli/lib)
      (PROGRAM=dg4odbc)
      (SID_DESC =
       (SID_NAME=DG4ODBC2)
      (ORACLE_HOME=/home/oracle/product/11.2.0)
      (ENVS=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micr
osoft/sqlncli/lib)
      (PROGRAM=dg4odbc)
LISTENER_GW =
(DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = usvcltprdoragw)(PORT = 1521))
tnsnames.ora
DG4ODBC =
   (DESCRIPTION=
      (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
      (CONNECT_DATA=(SID=DG4ODBC))
      (HS=OK)
DG4ODBC2 =
   (DESCRIPTION=
      (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
      (CONNECT_DATA=(SID=DG4ODBC2))
      (HS=OK)
I can't figure out why the named instance does not work but the other one does. Any help would be greatly appreciated!

Did you check with the ODBC test utility isql (it is installed by default when you install the unixODBC Driver manager) if your ODBC driver can connect at all to that named instance? I have some doubts that it will work either as there was a blog commented by a MS engineer:
Introducing the new Microsoft ODBC Drivers for SQL Server - Microsoft SQLNCli team blog - Site Home - MSDN Blogs
who states that named instance connections are not supported using that driver.
- Klaus

I want to use the SQL Toolkit of NI and SQL Server as my databasis on a server. Do I need to install a client in each computer I want to handle the data into SQL tables or I need only a ODBC driver?

I want to use the SQL Toolkit of NI and SQL Server as my databasis on a server. Do I need to install a client in each computer I want to handle the data into SQL tables or I need only a ODBC driver?

You only need the ODBC driver on each computer. If you are distributing the SQL Toolkit app as an executable and do not install the whole toolkit on each computer, you'll need the SQL Toolkit support files. This is about a dozen files. You can get the list at http://digital.ni.com/public.nsf/websearch/b814be005f9da9258625658700550c75?OpenDocument.

Is it possible to have different authentication mode for SQL Server Database Engine and corresponding SQL Server instance?

Hi,
I have installed the x64 SQL Server 2008 R2 Express with default settings and run MBSA 2.3 (using default settings too). It shows three SQL Server instances: MSSQL10_50.SQLEXPRESS, SQLEXPRESS and SQLEXPRESS (32-bit). For the first, authentication
mode is Windows, for the rest two - mixed. Here https://social.msdn.microsoft.com/Forums/sqlserver/en-US/03e470dc-874d-476d-849b-c805acf5b24d/sql-mbsa-question-on-folder-permission?forum=sqlsecurity question
about such multiple instances was asked and the answer is that "MSSQL10.TEST_DB
is the instance ID for the SQL Server Database Engine of the instance, TEST_DB", so in my case, it seems that MSSQL10_50.SQLEXPRESS is the instance ID for SQL Server Database Engine of the SQLEXPRESS instance.
I have two questions:
1) How can it be that SQL Server DB Engine instance has different authentication mode than corresponding SQL Server Instance?
2) Why 32-bit instance reported although I installed only 64-bit version?
Also, this https://social.technet.microsoft.com/Forums/security/en-US/6b12c019-eaf0-402c-ab40-51d31dce968f/mbsa-23-reporting-sql-32bt-instance-is-running-in-mixed-mode-when-it-is-set-to-integrated?forum=MBSA question seems to be related to this
issue, but there is no answer :(.
Upd: Tried on clean Windows 8 installation and Windows 7 with the same result.

Because I DO NOT want the three people who will be having access to the production SQL Server to also have access to the primary host ProductionA. Since I have to allow them to RDC into the box to manage the SQL Server, I figure why not create
a separate VM for each one of them and they can RDC into those instead.
Does this make any sense?
Any tips are greatly appreciated. The main reason for doing this is because the three people who will be accessing the box, I need to isolate each one of them and at the same time keep them off of the primary ProductionA.
Thanks for your help.
M
Hello M,
Since you dont want the 3 guys to have access to Production machine A.You can install SQL Server client .By client i mean SQL server management studio(SSMS) on there local desktop and then create login for them in SQL Server.Open port on which your SQL server
is running for three of the machines so that they can connct.Now with SSMS installed on each machine each can connect to SQL server from there own machine.
I would also like you to be cautious with giving Sysadmin privilege to all three of them ,first please note down what task they would do and then decide what rights to be provided.
Your option will also work but you need to create 3 VM for that .Which is more tedious task.
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Connecting to a specific SQL Server instance?

Hi all,
I create a new connection for SQL Server, specify the host and the port number that SQL Browser is listening on (my servers have dynamic ports, not static), and I can connect succesfully to the local SQL Server Instance on that machine, which is SQL Server 2000. However, I also have a SQL Server 2005 and 2008 running on that machine as well, and wish to connect to them.
The SQL Server tab doesn't ask for an instance name at all, so I don't know how to do that. I suppose I could make my ports static for each instance, but the point of using SQL Browser is that you don't need to do that. SQL Browser acts almost like a DNS server for any sql requests coming to that machine.
Is there any way to specify which instance name you want to connect to rather than a port #?

Ok, that worked. Now for another question, why isn't the connection retreiving the database I selected in the SQL Server tab? It's only retrieving the master database if I connect as sa (master is the default database for SA). How do I set it up to use a different database, or do cross database queries? I suppose I could make a user for each database, but that doesn't fix the second issue.
I think I might just be stuck using two different tools for these two very different products.

I want to use the SQL query IF EXIST to update or insert data in a ms access table, but it doesn´t work

Hi,
I want to use the SQL query IF EXIST to update or insert data in a ms access table, but it doesn´t work
(fault number -2147217900)
I want to search for a value in a ms access table , if it exist i want to update it, if not i want to insert a new row.
Working with LabView 7.1, database con. toolset.
Who can HELP?
Thanks a lot
Marco

Hello,
I think that If exist is not a standar SQL command (I know it exists I think in Oracle and SQL server), MS access doesn't support it, so I think the best way to do it is first make a Select and then either an Update or an insert, sorry...
Paulo

Query used by SQL Server Management Pack for monitoring database backups

I use SCOM 2012 R2 and the SQL Server Management Pack to monitor SQL Server database backups. I believe I am getting false positives. SCOM reports database are not backuped, while in fact they are. So I need to troubleshoot this. I suspect SCOM is querying
the backup history in the msdb database. I want to know which query SCOM uses.
I have tried looking in the monitor's definition but I suspect the query is embedded in the management pack files which are binary. I have also tried running a trace using the SQL Server Profiler on my test environment and overriding the interval to 60 seconds,
but I don't see a relevant query being executed. I also don't see the alert reappear so I suspect SCOM does not honor the interval in a way I would expect.
What query, or other method, does SCOM use to check database backups?
Thanks in advance.

Thank you both Ivan and Michael,
I only saw your messages by email and didn't see your screen shot before I extracted the query myself. In my own queries I calculate the backup age in hours instead of days because of daily full backups. Perhaps It will be a good idea to create my own monitors
from scratch like I used to do with Nagios.
I will study the vbscripts and might create my own version which allows the query to be entered as an parameter and move all code to a .Net class which can be called from vbscript as an COM object. This way I hope to reduce the vbscript code to an minimum
while keeping the flexibility of the SCOM Operations Console and the robustness of .Net. I suspect I want to make more non standard monitors in the future.
Regards,
Arjen

SQL ENTERPRISE: The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database

The error below makes absolutely no sense! I'm using Enterprise Core...yet I'm being told I can't use remote data sources:
w3wp!library!8!03/05/2015-19:08:48:: i INFO: Catalog SQL Server Edition = EnterpriseCore
w3wp!library!8!03/05/2015-19:08:48:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "The edition of Reporting
Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database." is not supported in this edition of Reporting Services.;
Really? This totally contradicts the documentation found here:
https://msdn.microsoft.com/en-us/library/ms157285(v=sql.110).aspx
That article says remote connections are completely supported.
ARGH! Why does this have to be so difficult to setup?!?

Hi jeffoliver1000,
According to your description, you are using Enterprise Core edition and you are prompted that you can’t use remote data sources.
In your scenario, we neither ignore your point nor be doubt with what you say. But actually we have met the case before that even though the SQL Server engine is Enterprise but the reporting services is still standard. So I would recommend you to find the
actual edition of reporting services you are using. You can find Reporting Services starting SKU in the Reporting Service logs ( default location: C:\Program Files\Microsoft SQL Server\<instance name>\Reporting Services\LogFiles). For more information,
please refer to the similar thread below:
https://social.technet.microsoft.com/Forums/en-US/f98c2f3e-1a30-4993-ab41-acbc5014f92e/data-driven-subscription-button-not-displayed?forum=sqlreportingservices
By the way, have you installed the other SQL Server edition before?
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

Cannot connect to the specified SQL Server instance

I am trying to install Microsoft System Center 2012 R2 Virtual Machine Management.
I am getting the following error:
Setup cannot connect to the specified SQL Server instance.
Ensure that the server name, isntance name, and, if speceified, port number are correct. If you are installing VMM remotely, ensure that remote connections are set up correctly, and then try Setup again.
I have installed the
Microsoft® SQL Server® 2008 R2 Command Line Utilities
but have not set up any SQL Server instances.
how should i proceed?
Edit:
The followign fields are configured:
Server Name: The name of the machine i am using
Port: <empty>
Use the following credentials <NOT ticked>
Instance name <empty> (the drop down is empty)
New Database <Ticked> : VirtualManagerDB

Is SQL server is properly installed on the system?
Are you able to connect with SQL server instance?
As per the given details looks, only client utilities installed and trying to create the database which needs SQL server.
Make sure you are able to connect with the "ServerName\InstanceName,PortNumber" and hope installing the system as per below article:
http://technet.microsoft.com/en-us/library/gg610656.aspx
Hope it help!
Please click the Mark as answer button and vote as helpful if this reply solves your problem

Cannot not connect to SQL Server instance.

Hello,
I have SQL Server 2012 installed and when I run this command:
sc query mssql$MSSQLSERVER
I get this error:
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:
The specified service does not exist as an installed service.
I run this command on the same server where SQL Server is installed. Databases are on the same server too. TCP/IP is enabled for the instance and port 1433 is open on the server's firewall. SQL Server Browser is running.
Many errors in the SQL Server error logs like:
SQLServer Error: 11001, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct.
SQLServer Error: 11001, TCP Provider: No such host is known. [SQLSTATE 08001]
Any ideas what could have gone wrong?
Thanks,
Paul
Paul

Hi Paul,
According to your description, you fail to connect to SQL Server 2012 instance. According to the SQL Server error log, based on my research, your issue could be due to that
the client cannot resolve the name of the SQL Server instance.
Are the errors from the SQL Server error log solved? If the errors are not solved, please follow the steps below to troubleshoot the issue.
1. Make sure you are able to ping the physical server where SQL Server is installed from the client machine. If not, you can try to connect to the SQL Server using an IP Address (for default instance) or IP Address\Instance Name
for a named instance.
2. Make sure you are using the correct instance name. When you connect to a default instance, machine name is the best representative for the instance name and when you connect to a named instance such as sqlexpress, you should
specify machinename\instancename according to
Niting123’s post. And you could verify if you use the right instance name in SQL Server configuration manager according to
Niting123’s post.
3. Check that SQL Server is in the network. You can use the SQLCMD -L command to retrieve the list of SQL Server installed in the network. Note that this will only return SQL Servers if the SQL Server Browser service is running.
4. Make sure that you enable Named Pipes besides TCP/IP protocol.
5. Check to see if remote connections is enabled. Right click on the server name in SSMS and select Properties. Go to the Connections tab and make sure Allow remote connection to this server is checked.
6. Locally connect to SQL Server and check the error log for the port entry.
7. To connect to SQL Server instance using TCP/IP from another computer, on the SQL Server computer, you must configure the firewall to allow connections to the TCP port used by the Database Engine. If you are connecting to a named
instance or a port other than TCP port 1433, you must also open the UDP port 1434 for the SQL Server Browser service according to pasquale’s post.
For step by step instruction on opening a port in the Windows firewall, see
How to: Configure a Windows Firewall for Database Engine Access
For more information about the process, please refer to the article:
http://www.mssqltips.com/sqlservertip/2340/resolving-could-not-open-a-connection-to-sql-server-errors/
In addition, you mention that there are many other errors, so please provide the SQL Server error log for analysis.
Regards,
Michelle Li

Certificate empty in registry. No IP connected to SQL Server instance

Hello,
I have a SQL Server 2008r2 instance running on Windows 2008 clustered physical server. The instance starts, then fails with the following:
2014-01-02 08:41:28.82 Server      Error: 26054, Severity: 16, State: 1.
2014-01-02 08:41:28.82 Server      Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources
is correct, and that the IP addresses on which this SQL Server instance depends are available. Error code: 0x103.
2014-01-02 08:41:28.82 Server      Error: 17182, Severity: 16, State: 1.
2014-01-02 08:41:28.82 Server      TDSSNIClient initialization failed with error 0x103, status code 0xa. Reason: Unable to initialize the TCP/IP listener. No more data is available.
2014-01-02 08:41:28.82 Server      Error: 17182, Severity: 16, State: 1.
2014-01-02 08:41:28.82 Server      TDSSNIClient initialization failed with error 0x103, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. No more data is available.
2014-01-02 08:41:28.82 Server      Error: 17826, Severity: 18, State: 3.
2014-01-02 08:41:28.82 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-01-02 08:41:28.82 Server      Error: 17120, Severity: 16, State: 1.
2014-01-02 08:41:28.82 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I found: http://support.microsoft.com/kb/2023869. I believe this will resolve my issue, however the command is not quite right. I cannot execute as in the article, but I can run certutil
-store.   There are 4 certificates in the file. Which do I use? Excerpt of file below - there are 0-3 Certificates in the file.
CA
================ Certificate 0 ================
Serial Number: 06376c00aa00648a11cfb8d4aa5c53f4 (numbers changed to protect the innocent)
Issuer: CN=Root Agency
NotBefore: 5/28/1996 4:02 PM
NotAfter: 12/31/2039 5:59 PM
Subject: CN=Root Agency
Signature matches Public Key
Root Certificate: Subject matches Issuer
Template:
Cert Hash(sha1): fe e4 49 ee 0e 39 65 a5 24 6f 00 0e 87 fd e2 a0 65 fd 98 d4 ((numbers changed to protect the innocent)
No key provider information
Cannot find the certificate and private key for decryption.
My certificate value under this registry key is empty.
Any help appreciated,
Dianne
Dianne

Hello ,
Please check below link
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/cc39d8cb-bc64-48e6-8368-24886481dd4f/sql-server-cluster-sql-server-resource-not-coming-online?forum=sqlsetupandupgrade
http://blogs.technet.com/b/taraj/archive/2009/01/07/could-not-find-any-ip-address-that-this-sql-server-instance-depends-upon.aspx
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

I want make use of SQL Server Instance, while connecting

Similar Messages

Maybe you are looking for