Cannot Connect to Remote Named Instance of SQL Server

We have 3x instances of SQL Server 2012 installed on a single remote server - there's the default MSSQLSERVER instance, then \INSTANCE01 and \INSTANCE02. I can remotely connect to the default MSSQLSERVER instance through SSMS, but I cannot connect to
either of the additional named instances (\INSTANCE01 or \INSTANCE02).
For example, if I try to connect to "sql.domain.com", I can successfully access the default instance on the remote server. If I try to connect to "sql.domain.com\INSTANCE01", I get an error stating
"A network-related or instance-specific error occurred while establishing a connection to SQL Server".
HOWEVER - if I try to connect to "sql.domain.com\INSTANCE01, 49301" (where 49301 is the TCP Port for the TCP/IP Protocol for this SQL Server instance), I am able to successfully connect.
This leads me to think that there's a communication issue with the SQL Server Browser service running on the remote SQL Server and my workstation.
The following items have been verified:
SQL Server Browser is running on the remote SQL Server
Windows Firewall has been disabled on the SQL Server
TCP Ports 1433, 1434, 1954, and 49301 have been opened up on the remote destination's firewall
UDP Port 1434 has been opened up on the remote destination's firewall
Thoughts? Did I miss something?

Hi brgnewman,
Use computername\instancename to connect to the database engine. Please try again. I think the configuration is OK.
Refer to Connecting from Another Computer:
http://msdn.microsoft.com/en-us/library/ms345343.aspx.
Thanks.
Maggie Luo
TechNet Community Support

Similar Messages

Error"Failed to open the connection" - Named Instance of SQL Server 2005

"Failed to open the connection" error, when connecting to the Named Instance of SQL Server 2005
The report is throwing error, when changing the logon information dynamically through C#.
Code
     string reportPath = @"D:\NET\TestReport\TestReport.rpt";
     ReportDocument reportDocument = new ReportDocument();
     reportDocument.Load(reportPath);
     foreach(CrystalDecisions.CrystalReports.Engine.Table table in tables)
          TableLogOnInfo tableLogonInfo = table.LogOnInfo;
          tableLogonInfo.ConnectionInfo.ServerName = @"TestServer\Instance1"; //Connnecting to Named instance of SQL Server 2005
          tableLogonInfo.ConnectionInfo.UserID = "sa";
          tableLogonInfo.ConnectionInfo.Password = "password";
          tableLogonInfo.ConnectionInfo.DatabaseName = "TEST_DB";
          table.ApplyLogOnInfo(tableLogonInfo);
     crystalReportViewer1.ReportSource = reportDocument;
Error Message
     Failed to open the connection.
     Failed to open the connection.
     C:\DOCUME1\PUGALE1\LOCALS~1\Temp\{DF9593A5-5C80-4CBC-ABC3-EC4EF204A7EB}.rpt
The error is occuring only whenever i am connecting to the Named Instance of SQL Server 2005.
Thanks in Advance
Edited by: pugalendran p on Feb 2, 2009 10:32 AM
Edited by: pugalendran p on Feb 2, 2009 10:43 AM

Hi,
Following solution might help you to resolve the issue.
Solution1:
Issue happens because universe connection to the Database is not responding and the Data Source Name is not configured to write SQL Server 2005 database.
Resolution
Created new DSN connection under SYSTEM DSN to SQL Server 2005 Database.
Import the universe from the designer.
Go to File->Parameters.
Edit Connection.
On the Database Middleware Page expand SQl Server 2005->Select SQL Server 2005 driver.
Change the DSN to new DSN connection
Test the connection.
Save the Universe and Export it to the repository.
Solution2:
I am taking Oracle as an example over here.
This can be caused when the SQLNET.ora is located in a remote location using mapped drives.
Resolution
To resolve,
check the registry [HKLM\SOFTWARE\ORACLE] you should see a folder called HOME0
look for any paths that contain a mapped drive partition
Change the mapped drive letter to a UNC path (
server\folder)
Open a command prompt and do a tnsping using the tnsname and verify the location of the SQLNET.ora or TNSNAMES.ora
If the path is not updated to the new path
Reboot the server
Regards,
Sarbhjeet Kaur

Cannot connect to a named instance using SSMS from a remote machine

Hi all,
SQL Server.....: 2012 EE
OS...................: Windows Server 2008 R2
I have a desktop machine, that i am using to administrer SQL Server (via SSMS) and to develop my SSIS solutions, but i can't connect to a named instance of my SQL Server. When i try to connect using SSMS to my named instance (myhost\DWSERVER)
i get a huge error message:
A network-related or instance-specific error occurred while establisinh a connection to SQL Server. The server was not found or was not accessible. Verify that the instance is correct and that SQL Server is configured to allow remote connections.
(provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
Locally, i am able to access that named instance using SSMS, just when i try to access from another machine, the above error pops-up to me.
I am using the SQL Server Authentication mode to connect to the named instance.
What am i doing wrong?
Thanks in advance.
Fabrício Pedroso Jorge Database Administrator - Belém, Pará, Brazil

Hi,
thanks for your attention.
That's correct, i can connect to my default instance both locally and remotelly. The default instance in on port 1433. I cannot find the port used by the named instance (DWSERVER).
Actually, i found this on the errorlog from the named instance:
2015-03-22 10:10:45.80 spid13s Server is listening on [ 'any' <ipv6> 49411].
2015-03-22 10:10:45.80 spid20s Server is listening on [ 'any' <ipv6> 5023].
2015-03-22 10:10:45.81 spid20s Server is listening on [ 'any' <ipv4> 5023].
2015-03-22 10:10:45.81 spid20s The Database Mirroring endpoint is now listening for connections.
2015-03-22 10:10:46.12 spid13s Server is listening on [ 'any' <ipv4> 49411].
2015-03-22 10:10:46.25 spid13s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\DWSERVER ].
2015-03-22 10:10:46.26 spid13s Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$DWSERVER\sql\query ].
2015-03-22 10:10:46.26 Server Server is listening on [ ::1 <ipv6> 49412].
2015-03-22 10:10:46.26 Server Server is listening on [ 127.0.0.1 <ipv4> 49412].
I can ping normally to the remote server.
Fabrício Pedroso Jorge Database Administrator - Belém, Pará, Brazil

Cannot connect to remote SSRS instance with SSMS

I recent installed a named instance of SSRS 2005 on a remote server. The server has a side by side install of SSRS 2000 and SSRS 2005, with the SSRS 2005 being a named instance. The server also has SSL and MS Sharepoint Portal Server installed.
When I try and connect to the SSRS 2005 instance with my client install of Mangement Studio, I get the error message:
"The underlying connection was closed: Could not establish a trust relationship for the SSL/TLS secure channel. (System.Web.Services)
Additional Information: The remote certificate is invalid according to the validation procedure. (System)."
Obviously, this is a SLL issue, but, not being a security guru, I have no clue on how to fix this. I do know the certificate is valid, not expired and properly working. Both installs of SSRS are set up using the SSL certificate. Also, I am not connecting to SSIS with Management Studio, as I heard there is a bug connecting to both SSRS and SSIS at the same time.
Anyone have any ideas?
Thanks!!
Jeff

I know this is an old topic, but I just had a similar issue on SSRS 2008R2 and trying to connect to it with SSMS 2008R2.
The SSRS is using a self-signed certificate. The problem then is how to allow SSMS to accept this untrusted certificate.
I found success with the following steps in the SSMS connection dialogue:
Server Type: Reporting Services
Server name: the exact server name on the certificate does not appear to be required (e.g., "localhost" is fine for a local connection)
On the Options>Connection tab, check
Always Use SSL
On the Options>Additional Connections Parameters
tab, enter the following text:
encrypt=true;trustServerCertificate=true
Click Connect and you should connect without any further certificate trust issues
for that session. Note that these steps must be repeated each time a new connection is made between SSMS and SSRS.

Cannot connect to Oracle 11gR2 database from SQL Server 2005

Both SQL Server (Windows) and Oracle (Linux) are in 64bit environments.
I have done the following on a Windows 2008 R2 with SQL Server 2005:
Install InstantClient from Oracle Database 11g Release 2 Client (11.2.0.1.0) for Microsoft Windows (x64) to C:\Oracle
Install oledb from 64-bit ODAC 11.2 Release 3 (11.2.0.2.1) for Windows x64 by executing install.bat oledb c:\oracle odac
Note: Not sure whether 11.2.0.2.1 version of ODAC will cause any problem since I cannot find 11.2.0.1.0 version.
I have checked the Allow inprocess of OraOLEDB.Oracle provider in SSMS.
I have executed sp_addlinkedserver @server = 'ORACLE_TEST', @srvproduct = 'Oracle', @provider = 'OraOLEDB.Oracle', @datasrc = '##.##.##.##:1521/TEST'
The ##.##.##.## is the ip address of the Linux server which has the Oracle 11gR2 database TEST.
I have executed sp_addlinkedsrvlogin @rmtsrvname = 'ORACLE_TEST', @useself = 'FALSE', @rmtuser = 'xxxx', @rmtpassword = 'yyyy'
The xxxx is the oracle username and yyyy is the password for the oracle user xxxx.
I know the oracle database TEST is up since I have setup connection in Oracle SQL Developer having:
##.##.##.## as the hostname
1521 as the Port
xxxx as the username
yyyy as the password
TEST as the service name
When I click Test Connection for the linked server ORACLE_TEST in SSMS, it just hang.
When I issue a query like select count(*) from oracle_test..xxxx.table1, it just run forever. I'm not so sure how to query an oracle table. I have also tried select count(*) from oracle_test.xxxx.xxxx.table1.
When I retype the password in the Linked Server Properties, it just run forever.
Do I need to create a tnsnames.ora on the Windows machine?
Do I need to change the tnsnames.ora on Linux machine?
I'm very new to Oracle.

This forum is dealing with connections from an Oracle database to SQL Server - so the Oracle database is the driving site and this is the way round from your linked server set up.
As you're suing the instant client you might post your issue in the instant client forum:
Instant Client

Connectivity issue with local instance of sql server

hi everbody,
well for the last couple of days i have almost taken my head out to get this issue resolved.
but still i am no where. i have already referred to so many tips available online but still can't fix the prob.
i am trying to connect a C# ( .net 2005) program to connect to the integrated sql server 2005 instance on my local computer.
i have got windows 7 home basic on my pc with .net frame work 2.0 sp2 and have also upgraded to sql server 2005 sp3 as per some online study.
i have also tried all these steps but still getting the error 40.
1. Check Whether the SQL Server is running or not.
Because the trial to connect to the stopped server may also cause this problem.
2. Check the name of the SQl Server.
For example, if we try to connect to SQL server using .NET application, for some SQL Server, the name of the server "localhost" works, but for some server, we may need to mention "(local)".
3. Check Whether the SQL Browser Service is running
4. Check Whether the TCP/IP is enabled for SQL Server Configuration
* Expand SQL Server Configuration Manager
* Enable TCP/IP
5. Firewall Settings
You may need to add the port of Sql server to the Firewall if it is other than the default port(1433).
Go to Control Panel | Windows Firewall | Change Settings | Exceptions | Add Port
6. Enable the Remote Connection
Goto SQL Server Management Studio.
Right Click on Server node
Click On Properties
Check the Allow Remote connections to Server Check Box
7. Enable Named Pipes
- Open the "SQL Server Configuration Manager" (under Configuration Tools)
- Expand the "SQL Server 2005 Network Configuration"
- Select the "Protocols for "
- Set the Named Pipes To Enabled
8. Create Exception of Sqlbrowser.exe
kindly provide me some help with your valuable suggestions.

Hi Mukesh Devrani,
Thank you for posting.
Your question is more like SQL. I suggest that you can ask your question in SQL forum.
http://social.msdn.microsoft.com/Forums/en/category/sqlserver/
Best Regards,
Larcolais
MSDN Subscriber Support in Forum
If you have any feedback of our support, please contact [email protected]
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

Named Instance in SQL Server 2000

We recently switched to SQL Server 2000 and are now having some
problems. Our SQL Farm set up named instances so we could take
advantage of active/active clustering. In doing this, they set up 2
Named Instances, and therefore both cluster nodes are identically
configured. To avoid a single point of failure, we'd like to take
advantage of the active/active clustering when we call into the SQL
Server 2000 database and not have to specify the exact port of either
instance.
Based on some information from a colleuge that is familiar with
accessing SQL Server from the MicroSoft environment, we should be able
to specify server=servername\instance:1434. This in turn would
determine the correct port for one of the instances and the driver
should handle forwarding our request to that instance.
Does the WebLogic driver handle this? If so, does anyone know the
proper syntax for the connection string?

Hi. Our driver will only connect to a DBMS by being given it's
machine name and port. If there are two DBMSes on the one machine,
then they will be distinguished (only) by different port numbers.
Our driver will not automatically switch from one port to another.
Joe Weinstein
Julie Burnard wrote:
>
We recently switched to SQL Server 2000 and are now having some
problems. Our SQL Farm set up named instances so we could take
advantage of active/active clustering. In doing this, they set up 2
Named Instances, and therefore both cluster nodes are identically
configured. To avoid a single point of failure, we'd like to take
advantage of the active/active clustering when we call into the SQL
Server 2000 database and not have to specify the exact port of either
instance.
Based on some information from a colleuge that is familiar with
accessing SQL Server from the MicroSoft environment, we should be able
to specify server=servername\instance:1434. This in turn would
determine the correct port for one of the instances and the driver
should handle forwarding our request to that instance.
Does the WebLogic driver handle this? If so, does anyone know the
proper syntax for the connection string?--
B.E.A. is now hiring! (12/14/01) If interested send a resume to [email protected]
DIRECTOR OF PRODUCT PLANS AND STRATEGY San Francisco, CA
E-SALES BUSINESS DEVELOPMENT REPRESENTATIVE Dallas, TX
SOFTWARE ENGINEER (DBA) Liberty Corner, NJ
SENIOR WEB DEVELOPER San Jose, CA
SOFTWARE ENGINEER (ALL LEVELS), CARY, NORTH CAROLINA San Jose, CA
SR. PRODUCT MANAGER Bellevue, WA
SR. WEB DESIGNER San Jose, CA
Channel Marketing Manager - EMEA Region London, GBR
DIRECTOR OF MARKETING STRATEGY, APPLICATION SERVERS San Jose, CA
SENIOR SOFTWARE ENGINEER (PLATFORM) San Jose, CA
E-COMMERCE INTEGRATION ARCHITECT San Jose, CA
QUALITY ASSURANCE ENGINEER Redmond, WA
Services Development Manager (Business Development Manager - Services) Paris, FRA; Munich, DEU
SENIOR SOFTWARE ENGINEER (PLATFORM) Redmond, WA
E-Marketing Programs Specialist EMEA London, GBR
BUSINESS DEVELOPMENT DIRECTOR - E COMMERCE INTEGRATION San Jose, CA
MANAGER, E-SALES Plano, TX

Upgrading DPM 2012 SP1 to DPM 2012 R2 fails (DPM Setup is unable to connect to the specific instance of SQL Server Reporting Service (ID: 33431)

The Background:
1. DPM 2012 SP1 was originally installed on a server with local SQL 2008 R2 instance (SQL was installed as part of DPM)
2. SQL database was upgraded to SQL 2012 SP1
Now I want to upgrade DPM 2012 SP1 CU3 to R2. It is throwing the following error. Any help would be appreciated.

This absolutely fixed my issue. I had upgraded my version of SQL and was then trying to upgrade DPM 2012 to 2012R2 and I could not figure out where the installation was querying old version of the reporting services.
DPM Log Before:
[6/4/2014 2:53:32 PM] Information : Query WMI provider for path of configuration file for SQL Server 2008 Reporting Services.
[6/4/2014 2:53:32 PM] Information : Querying WMI Namespace: \\DPMServer\root\Microsoft\SqlServer\ReportServer\RS_MSDPM2012\v10\admin for query: SELECT * FROM MSReportServer_ConfigurationSetting WHERE InstanceName='MSDPM2012'
[6/4/2014 2:53:32 PM] * Exception : => System.Management.ManagementException: Provider load failure
DPM Log After:
[6/4/2014 3:25:36 PM] Information : SQL Server 2008 R2 SP2 instance MSDPM2012 is not present on this system.
[6/4/2014 3:25:36 PM] Information : Query WMI provider for SQL Server 2008.
[6/4/2014 3:25:36 PM] Information : Querying WMI Namespace: \\DPMServer\root\Microsoft\SqlServer\ComputerManagement11 for query: Select * from SqlServiceAdvancedProperty where ServiceName='MSSQL$MSDPM2012' and PropertyName='Version'
[6/4/2014 3:25:36 PM] Information : SQL Server 2008 R2 SP2 instance MSDPM2012 is present on this system.
[6/4/2014 3:25:36 PM] Information : Inspect context initialized with
SQL Server namespace: \\{0}\root\Microsoft\SqlServer\ComputerManagement11
Reporting namespace: \\{0}\root\Microsoft\SqlServer\ReportServer\RS_{1}\v11\admin
SqlServerDetected: True
[6/4/2014 3:25:36 PM] Information : Check if SQL Server 2012 Service Pack 1 Tools is installed.
[6/4/2014 3:25:36 PM] Information : Inspect.CheckSqlServerTools : MsiQueryProductState returned : INSTALLSTATE_DEFAULT
[6/4/2014 3:25:36 PM] Information : **********************************************************************************
Thanks for This FIX!

What range TCP/IP Port should be give to default or named instance of sql server for security purpose to sql server ?

Hi
i am following technet article for Configure SQL Server security for SharePoint 2013 environments
https://technet.microsoft.com/en-us/library/ff607733?f=255&MSPPError=-2147217396
i want to change default TCPIP port from 1433 to which ports to change is securable for sql server
i mean in what range
for example can i change to 1500 or 2000 or 1450 etc .
if i assign like these portnos it will not affect to other ports in windows server 2012?
adil

I agree with Erland. (Always a good idea.) Changing the port doesn't help much to prevent attacks. If you decide to do that see Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager)
http://msdn.microsoft.com/library/ms177440.aspx. Note
"When selecting a port number, consult
http://www.iana.org/assignments/port-numbers for a list of port numbers that are assigned to specific applications."
It's important that you pick a number that isn't used by some other application.
Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

Problem with a JDBC Adapter when connect to Instance on SQL Server

Hi,
Currently I'm setting up a communication channel with the JDBC adapter to work on a SQL Server database. When I use a string without specifying the connection instance, the JDBC driver takes the default instance and connects to a database without problems.
jdbc: sqlserver: / / Server01; databaseName = IntegraSAP1
The problem is when I need to connect to another instance of it server.
jdbc: sqlserver: / / Server01; instanceName = SAP; databaseName = IntegraSAP2
The JDBC driver, in short, send me the following error:
Cause Exception: 'Error when attempting
to get processing resources: com.sap.aii.af.lib.util.concurrent.ResourcePoolException:
Unable to create new pooled resource: DriverManagerException:
Can not establish connection:: com.microsoft.sqlserver.jdbc.SQLServerException:
The connection to the named instance has failed. Error:
java.net.UnknownHostException: .
I appreciate your help,
Regards,
Johnny

Not sure, might be port number is not required in case using instance. Give one more try with :
jdbc:sqlserver:/ /Server01\SAP; databaseName = IntegraSAP2
A comment from http://msdn.microsoft.com/en-us/library/ms378428.aspx
"SQL Server 2000 and SQL Server 2005 allow for the installation of multiple database instances per server. Each instance is identified by a specific name. To connect to a named instance of SQL Server, you can either specify the port number of the named instance (preferred), or you can specify the instance name as a JDBC URL property or a datasource property."
Regards,
Sunil Chandra

SSAS 2012 (SP2) - Connecting to a Named Instance in a Failover Cluster

I posted this question some months ago and never got a resolution...still having the same problem. (http://social.msdn.microsoft.com/Forums/sqlserver/en-US/4178ba62-87e2-4672-a4ef-acd970ac1011/ssas-2012-sp1-connecting-to-a-named-instance-in-a-failover-cluster?forum=sqlanalysisservices)
I have a 3 node failover cluster installation (active-passive-passive) configured as follows:
Node1: DB Engine 1 (named instance DB01)
Node2: DB Engine 2 (named instance DB02)
Node3: Analysis Services (named instance DBAS)
Obviously, the node indicated is merely the default active node for each service, with each service able to fail from node to node as required.
Strangely, when I attempt to connect to the SSAS node using the cluster netbios "alias" (dunno, what else it would be called, so I apologize if I am mixing terminology or somesuch), I am only able to do so by specifying the the alias _without_ the
required named instance. If I issue a connection request using an external program or even SSMS using Node3\DBAS or Node3.domain\DBAS, it appears that the SQL Server Browser is offering up a bogus TCP port for the named instance (in my case TCP/58554), when
in reality, the SSAS service is running on TCP/2383 (confirmed with netstat) -- which if I understand correctly after much, much reading on the subject is the only port that can be used in a failover cluster. In any case, I'm puzzled beyond words. As I think
through it, I believe I've seen this issue in the past, but never worried about it since it wasn't necessary to specify the named instance when I had SSAS requirements... It's only a showstopper now because I'm finalizing my implementation of SCVMM/SCOM 2012
R2, and for some strange reason the PRO configuration in VMM gets all butthurt if you don't offer up a named instance...
Thank you much for reading. I appreciate any help to get this resolved.
POSSIBLY NOT RELEVANT...?
I've properly configured the SPNs for the SSAS service (MSOLAPSvc.3) and the SQL Browser (MSOLAPDisco.3), with the former mapped to the SSAS service account and the latter to the cluster "alias" (since it runs as "NT AUTHORITY\LOCALSERVICE"
as is customary) and have permitted delegation on the service and machine accounts as required. So, I'm not getting any kerberos issues with the service...any more, that is... ;) I'm not sure that's important, but I wanted to be forthcoming with details to
help solve the issue.

When connecting to SSAS in a cluster, you do not specify an instance name. In your case, you would use the name of the SSAS IP address to connect.
See:
http://msdn.microsoft.com/en-us/library/dn141153.aspx
For servers deployed in a failover cluster, connect using the network name of the SSAS cluster. This name is specified during SQL Server setup, as
SQL Server Network Name. Note that if you installed SSAS as a named instance onto a Windows Server Failover Cluster (WSFC), you never add the instance name on the connection. This practice is unique to SSAS; in contrast, a named
instance of a clustered relational database engine does include the instance name. For example, if you installed both SSAS and the database engine as named instance (Contoso-Accounting) with a SQL Server Network Name of SQL-CLU, you would connect to SSAS using
"SQL-CLU" and to the database engine as "SQL-CLU\Contoso-Accounting". See
How to Cluster SQL Server Analysis Services for more information and examples.

Cannot uninstall instance of SQL Server 2014

Hello,
I have two instances of SQL Server 2014 installed and i want to uninstall them (and install SQL Server 2012 evaluation). I managed to uninstall the one instance. When i try to uninstall the second a message informs me that the operating system does not meet
the minimum requirements. I had the same proble when uninstalling SQL Server 2012 and i went to the setup file and changed the compatibility mode to Windows Vista. Is there something similar that i should do in the case of SQL Server 2014 or i should do something
totally different?
Thanks in advance,
Andreas

Hi,
Personally I have not faced this situation but this seems bug below Connect Item MS closed as not reproducable
https://connect.microsoft.com/SQLServer/feedback/details/707706/unable-to-uninstall-sql-server-2012-rc0-from-control-panel
Below connect Item deals with same issue as your
https://connect.microsoft.com/SQLServer/feedback/details/974626/cannot-uninstall-sql-express-2014-on-windows-7-sp1
Workaround should be instaed of uninstalling using GUI please use command prompt
Launch setup.exe from an elevated command shell. Change to the directory "c:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\SQLServer2014", then type:
Setup.exe /action=uninstall
Please change uninstall script as per need
Normal uninstall Script would look like
Setup.exe /Action=Uninstall /FEATURES=SQL,AS,RS,IS,Tools /INSTANCENAME=InstanceName
Please refer to
this link for uninstall parameters
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Multiple instance of Sql server running for Analyzer 7.0 install

Hi,I do have a Sql server instance where the server name is: abc\xyz. Will analyzer accetp a '\' as the server name. This instance of Sql server is not running is not running on the std port 1433. Let me know if there will be any issues whrn installing Analyzer 7.0.Thanks,

There can only be a single default instance and multiple named instances.
BOL: http://technet.microsoft.com/en-us/library/ms143547.aspx
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

RSA1 DB Connection from SAP BW to external SQL Server databas.

Hello,
I am trying to connect our SAP BW system with SQL Server Source System through DB Connect in transaction RSA1.
Our BW system is running on Windows and MaxDB platform, therefore have I already added the latest dbmssslib.dll library to the kernel for SQL Server.
But the connection does not work anyhow, I recieve the error "Database error -1 at CON > [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does > exist or access denied." and I am quite sure that my input parameters are correct.
Therefore I wonder if someone has run into a similar problem and what the problem could be?
Best Regards,
Niklas Sandstedt

Hi,
I am sorry that my case was assigned to wrong forum.
That should now have been corrected, however my problem still remains unsolved in one of our systems.
I found note 178949, which fixed the problem in one system. But even though the system setup seems to be identical, the two systems appears different.
The following has been done for both systems:
1. Upgraded kernel to 701 version 111 and added dbmssslib.dll and dbmssslib.pdb files
2. Created Logical system in BD54.
3. Tried to create DB connection in transaction DBACOCKPIT.
In the third step, the setup fails and I receive the following error message when I test the connection:
Database error -1 at CON > [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not > exist or access denied.
Database error -1
All profile parameters AL11-directories also seems to be correct in both systems, so both should find the dbmssslib.dll file.
One issue that I see is in DBACOCKPIT, the checkbox for "SAP Systems with basis release" is unchangeble and marked. This however, I think was changed in the other system automatically when the connection was established successfully.
Has anyone run into the same problem?
Best Regards,
Niklas Sandstedt

How to connect to a specific database in SQL server

Hi,
How can I connect to a specific database in SQL server? I used the following statement. But my table is inserted to the 'master' database in the SQL server. How can I insert my tables to the specific database tahta I have created before?
Connection con;
String sURL = "jdbc:microsoft:sqlserver://SERVER_NAME:1433";
con = DriverManager.getConnection ( sURL, sUsername, sPassword);

Hi,
When I use the syntax:
String sURL = "jdbc:microsoft:sqlserver://SERVER_NAME:1433/DATABASE_NAME;selectMethod=cursor";
it gives an error as follows:
problems connecting to jdbc:microsoft:sqlserver://SERVER_NAME:1433/DATABASE_NAME;selectMethod=cursor:
[Microsoft][SQLServer 2000 Driver for JDBC]Unable to connect. Invalid URL.
What is the way to connect to a specific database?

Cannot Connect to Remote Named Instance of SQL Server

Similar Messages

Maybe you are looking for