Connecting to SQLServer 2k named Instance

Hey guys, this time i need some URGENT help, i swapped from windows to linux platform and using CF9, when i create a DSN in windows using SERVER_NAME\INSTANCE_NAME for the Server field, filling user name and password with a Microsoft SQL Server native DSN works perfectly, but when i do this same thing on Linux i get this nasty error:
java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]The requested instance is either invalid or not running.
The root cause was that: java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]The requested instance is either invalid or not running.
So i tryed to create a connection using the "Other" as DSN type and filled out this info:
CF Data Source Name: Test
JDBC URL: jdbc:sqlserver://SERVER_NAME\INSTANCE_NAME:1433;DatabaseName=MyDatabase
Driver Class: com.microsoft.sqlserver.jdbc.SQLServerDriver
Driver Name: SQL Server JDBC
User name: myuser
Password: mypass
i get this error:
Connection verification failed for data source: test
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host FULLSQL, port 1433 has failed. Error: "Connection refused. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.".
This was done after downloading sqljdbc_3.0.1301.101_enu.tar.gz from microsoft's web site and placing the sqljdbc4.jar file inside the /opt/coldfusion9/runtime/lib directory.
So basically the first way to create the connection works on windows but not on linux, and the second way does not work in any place even tho it's supposed to be working...
Please send me some help ASAP, need this thing working BADLY!

Okay, just solved the mistery... i will NEVER connect since every time you install a new SQL Server instance THAT new instance will listen to a different port, in this case the default 1433 was working but for the first instance and i was trying to connect to a second one listening in some other port i can't remember ATM.
Thanx for that help ne way Adam....!

Similar Messages

SQLDeveloper cannot connect to SQL Server named instances

I'm trying to connect to a SQL Server 2005 named instance on my local PC but SQLDeveloper is failing to connect as there is no way to specify the named instance on the connection screen.
For comparison I set up a jdbc connection in JDeveloper and
the connection URL which works in JDeveloper is jdbc:jtds:sqlserver://127.0.0.1:8020;instance=WESTERNEUROPE
Without the instance property JDeveloper gets a connection refused

Set up the connection through SQL developer, then exit the software.
For a sqlserver database like GABRIEL\angel
Modify the URL property in the IDEConnections.xml file
<URL>jdbc:jtds:sqlserver://GABRIEL:1433;instance=angel</URL>
You cannot use Windoze authenrication, and will need a SQL Server named user to connect.

Connecting to sqlserver using named pipe

I would like to connect to mssql (running on same PC as SQL Developer) using named pipes.
The host is listed in the Windows Service Manager as \\SX3102971\SIMSLOCAL
I have gone to the 'Oracle' tab, selected 'Advanced' and in the 'Custom JDBC URL'
entered
jdbc:jtds:sqlserver:\\SX3102971\SIMSLOCAL;namedPipe=true;user=<username>;password=<password>
where <username> and <password> are the true values.
I receive a message
Staus : Failure -Invalid connection information specified. Verify the URL format for the specified driver.
Can anyone advise on what may be wrong?
Also, can SQLDeveloper handle blank passwords?
The database is installed as part of a third party application, which sets the default dba logon with no password. SQL Developer states that a password is required. For the example above I have created my own log on.

Hi,
I managed to solve the problem. So don't worry about it.
For others who are looking for the solution...
- I have referred to the http://www.qint.de/joria/doc/jdbc/jtds.html.
- I have changed the URL element in IDEConnections.xml file located under where SQLDEVELOPER software is installed.
- The URL must look like the following ...
<URL>jdbc:jtds:sqlserver://\\.\;namedPipe=true;instance=<name of the database - without the server name>;</URL>
Hope this helps.
Regards
Raja
Message was edited by:
rajaram_r

Required Ports to connect remote SQL named Instance for SCCM 2012 R2

Hi,
I have allowed the TCP 1433,1434,135 and 80 but still unable to connect the remote SQL named instance DB for the SCCM 2012 R2... and getting below error..can you please suggest if any other port required for the same, i have turned off the windows
firewall and RPC service is running ob Remote SQL and SCCM 2012 R2 server..
CCMsetuplog
Shailendra Dev

During the installation you need more ports. You would also need the (dynamic) RPC ports. See for a complete list (section Site Server --> SQL Server):
https://technet.microsoft.com/en-us/library/hh427328.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

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.

Always on listener on named instance. Do I have to specify the port while connecting a listener created on a named instance?

Hi all. Here again.
Scenario: I have to consolidate several physical servers with one SQL server instance install on each one. I decided to consolidate all in one server installing different named instances. In order to avoid application connection string change I had the idea
of configuring different listener pointing to different alwayson group.
To meet this requests, I configured the cluster, I installed a principal SQLServer Instance and configured the alwayson groups with the required listeners.
All ok so far, alwayson is great.
So, I installed a named instance, I configured the necessary alwayson groups and the related listener but...
NOTE: The db in the principal and in the named instance have the same name.
If I connect the listener pointing the ag belonging the named instance I connect to the principal instance!
the only way I have to connect to the named instance is to specify the port that must be different from the 1433 as usual.
Anyway, why I cannot use the 1433 port if dealing with a different ip?
Listener are the following:
Named instance
10.100.21.100 : 1455
Principal instance
10.100.21.50 :
1433
Thankyou

Hi all.
I reviewed the architecture installing only named instances and I solved.
Anyway, i'm going to explain better my configuration in order to understand where I went wrong.
I have two servers, SQLCLU01 and SQLCLU02 partecipating to AVSQLCLU cluster
Each server has two SQL instances, the principal SQLPROD and the named instance SQLTEST
Each instance contain the OneToOne database.
I created an AG named AgOneToOneProd laying on the SQLPROD instance with its
OneToOne listener described here down (sys.dm_tcp_listener_states;)
7 10.100.21.50
1 1433
0 TSQL
0 ONLINE
2014-05-07 10:23:04.113
DnsName:OneToOne
Port:1433
IpconfigurationFromCluster:('IP Address: 10.100.21.50')
So I tried to create an AG named AgOneToOneTest laying on the SQLTEST named instance with its
OneToOneTest listener but the port 1433 is unavailable even if the listener IP is different. I managed in creating the listener changing the port like this
7 10.100.21.100
1 1455
0 TSQL
0 ONLINE
2014-05-07 10:36:05.347
DnsName:OneToOneTest
Port:1455
IpconfigurationFromCluster:('IP Address: 10.100.21.100')
So, the issue is:
Connecting to OneToOne.mydomain.local i can see the OneToOne database and crud operation are performed against the SQLPROD instance.
But connecting to OneToOneTest.mydomain.local the OneToOne database I'm connected to is still the one belonging to the
SQLPROD instance.
The only way to let my application connected to the SQLTEST instance is to specify the port in the DSN.
Anyway, summary here, issues are bolded
OneToOne.mydomain.local -------> SQLPROD
OneToOneTest.mydomain.local -------> SQLPROD
OneToOneTest.mydomain.local,1455 -------> SQLTEST
The same by IP
10.100.21.100,1455 --------> SQLTEST
10.100.21.100 --------> SQLPROD
and.....
10.100.21.100,1433 --------> SQLPROD
May be... Do I missed some best practices in creating listeners against a principal + named instances?
Thankyou
Stefano
Ste'

SQL2012 SSMS fail to connect named instance

Hi, Currently we would like to setup replication between 2 sql instances (binded to corresponding IP, listening on port 1433) on different servers (DUAT01, DUAT101). However, we found the SSMS cannot connect remote server A from server B using
named instance.
The sql instances can be connected by using either IP or FQDN, however, that cannot fulfill the requirement on setting up replication as it require the instance to connect as "DUAT101\SQL2K8R2" instead of "x.x.x.x" or "SQLUATCSS2K8R2.domain.com".
We tried to change "Protocol"->"Listen All" from "No" to "Yes", then SSMS can connect the named instance successful in this format "DUAT101\SQL2K8R2", but the application using "SQLUATCSS2K8R2.domain.com"
to connect sql instance was fail.
Pls advise how to make it possible to connect sql instance successful in both way. thanks.

can connect the named instance successful in this format "DUAT101\SQL2K8R2", but the application using "SQLUATCSS2K8R2.domain.com" to connect sql instance was fail.
Hello,
To connect to a named instance you have to use either the instance name or the instance IP port, like
DUAT101, 1433
The only other Option is to create a SQL Server alias using CliConfg.exe (Client configuration) tool.
Olaf Helper
[ Blog] [ Xing] [ MVP]
Hi Olaf, our server (DUAT101) have 5 sql instances. It always return the default instance with "DUAT101, 1433". When I connect using instance name, it prompt me below error that we need to solve.
===================================
Cannot connect to duat101\sql2k8r2.
===================================
Instance failure. (System.Data)
Program Location:
   at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer
timeout)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
   at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

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

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

Sql server 2012 express - tcp/ip connection to named instance using dynamic port not working

I have a named instance on a SQL 2012 Express server that won't connect via TCP/IP when wanting to connect off of the dynamic port. I can connect via shared memory locally on the server.   I can connect to the namespace when specifying the
dynamic port listed in the configuration manager.
This is the only named instance on the server and it is not the default.
TCP/IP is enabled
Allow Remote connections is enabled
the server browser service is running
I can connect via the dynamic port number
I am testing the connection locally on the server, so I don't believe a firewall is the issue. I get the same results if I test it from a remote computer.
When using the sqlcmd (sqlcmd -S tcp:SQLSRVR\NAMEINST -E) I get the message that "the requested protocol isn't supported [xfffffffff]".   The command (sqlcmd -S tcp:SQLSRVR\NAMEINST,59992 -E) works.
Through SSMS, I get the message "the connection was actively refused".
On other boxes, I can connect with the named instance without having to specify the port.
I have looked through the sql logs and nothing much shows up. The log does show that is listening on the port # for ipv4 and ipv6.   There is also a line in there talking about the SPN not being registered and not to worry about it if
you are not using Kerberos. I logged in through shared memory and it said I was using NTLM.
Any help would be appreciated.
thanks.

Hi clw,
I’m writing to follow up with you on this post. According to your description, I do a test, if you configure the database engine to listen on a specific TCP port (59992), and
the port is opened in the firewall. If you want to connect to the SQL Server instance, you 'd better to
use the port number.
In my opinion, by default, the default instance of the Database Engine uses port 1433, usually, if you have configured the server to listen on a non-default port number, when an instance of SQL Server uses dynamic port allocation, the connection string that
is built at the SQL Server client does not specify the destination TCP/IP port unless the user or the programmer explicitly specifies the port. Therefore, the SQL Server client library queries the server on UDP port 1434 to collect the information about the
destination instance of SQL Server.
If UDP port 1434 is disabled, the SQL Server client cannot dynamically determine the port of the named instance of SQL Server. Therefore, the SQL Server client may be unable to connect to the named instance of SQL Server. In this situation, the SQL Server
client must specify the dynamically allocated port where the named instance of SQL Server is listening.
For more information about configuring an instance of SQL Server to listen on a specific TCP port or dynamic port, you can review the following article.
https://support.transfrm.com/entries/503111-How-to-configure-an-instance-of-SQL-Server-to-listen-on-a-specific-TCP-port-or-dynamic-port
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

DI Server - Cannot connect to named instance SQL server database

Hi,
I have developed a small DI server application and want to migrate it to a production server. I keep on getting the Cannot connect to SBOCommon error on login though. I have verified all user names and passwords and the only real difference is that the production environment uses a named instance SQL server eg server\instance setup.
The production DI server will however connect perfectly to the test database (which is NOT a named instance) .
Anyone using DI server against a named instance SQL server or have some other ideas what might cause this?
I use B1WS 1.0 and the version of SBO is 8.00.181..
Jaco

I may have solved the problem, at least partially.
I created a test user with full rights on my test database server and it would also not connect, even though my test database is not a an instance setup.
Then I found this thread [Re: DI Server Always Uses SA to log into MS SQL database even if SOAP packet]
It seems that at my current patch level the user 'sa' is hard coded into the DI server as sql username! I don't have the production server's 'sa' user credentials at present but will test it on Monday. Will also test against 8.8 soon ..

While connecting to the default instance from out side of the server it's reaches to Named instance ?i

Hi All,
We have two named instance in "test" server. the names like test\a & test\b... The tcp\ip for test\a is dynamic and for test\b is default port 1433... Now customer requested to install the default instance...we had an issue with installation
that is the default port number is in use so, the default installation failed and then i changed the settings in registry to use the dynamic port for default instance and then i manually start the sql servers...seems all are good...but when i connecting this
default instance from out side of the box through SSMS it's pointing to the named instance which one having the default port number(test\b).
We can change the port number for test\b and assign that port to default instance...but the applications which are connecting to the test\b those are using the default port number...so, we don't want to disturb the connectivity...
is there any way to fix this issue with out changing the port number for test\b ?
it is urgent...we have to fix this issue ASAP..
Thanks in Advance,
rup

Hi rup,
Glad to hear the issue is resolved.
As your post, if SQL Server is configured to use dynamic port,
it is difficult for application connectivity because the port number selected changes every time that the Database Engine is started.
From your description, you have changed the dynamic port number to static port number. To avoid a common pitfall, please also ensure that
you have deleted the entry (0 or some random port) for dynamic port in SQL Server Configuration Manager. For more details, please review this
blog.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

DBACOCKPIT - MSSQL Named Instance, RFC and DB Connection different systems

Hello All,
SAP is installed as a Central Server. Database and Central instance on a single host with the database on a Named Instance.
I have configured the dbacockpit as per SAP Note 1388700 - SQL Server Remote Database Monitor in Solution Manager 400 for my Named Instances. I have a working database connection %_<SID>_<HOSTNAME> with the DBCO Connection Info referencing the MSSQL_SERVER as <HOSTNAME>\<SID>. Full line:
MSSQL_DBNAME=<SID> MSSQL_SERVER=<HOSTNAME>\<SID> OBJECT_SOURCE=SAPSolMan710
In dbacockpit now as an additional action I try to edit the connection. I select the checkbox by RFC destination, first message with a Red LED is 'This is not the local system, please specify a RFC destination. I select any RFC destination referencing the host, even custom made ones. The response after logging in to the target (when not using Trusted RFC) is always the same.
'Red LED', SMP, RFC destination and database connection describe different systems.
In the home screen of dbacockpit if you now select 'SLD System Import' the systems with a Named Instance are still available under 'New Database Systems in the SLD'.
Now edit the system again, remove the RFC destination and Save. This will write to the SLD.
If you now log in to the SLD, Administration, Content Maintenance, 'Class' Database Systems you will now have a new System with 0(zero) associations. This system has SystemHome = <HOSTNAME>\<SID> as such it will not match to the SAP System. I have edited the Database in SMSY to directly reference the Database connection but even this does not help
Has anyone come accross this? What is the resolution?

Hi,
Could you please post the errors that appears while configuring in the DBACOCKPIT t code at the bottom of the screen?
According to that we can determine, whether it is able connect the database correctly or not.
Cheers

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

SQL Server 2000 and Named Instances

Heya,
I'm having trouble creating a JDBC Connection Pool against our SQL Server box through the Admin Console. There are firewalls between the Weblogic box and the SQL Box, and they have traffic blocked on port 1434. I am specifying port 1433 in the URL, but it seems that it's still trying to do the dynamic port determination through UDP on 1434. My URL is along the lines of:
jdbc:bea:sqlserver://99.99.99.99\\MYINSTANCE:1433
Is there a way with named instances to force the driver to use the indicated port? I'm going to see if they'll open up port 1434 for a test, but I wanted to know if there are other options.
Thanks,
Anna

Anna Veirauchs wrote:
Heya,
I gave it a try and it threw a socket error: Unknown host 99.99.99.99/myinstance
I've been researching the issue on my end and I think I might be able to treat it like a non-named instance. This was sort-of hinted at in some Microsoft documentation for their JDBC driver. On Weblogic I put it in as 99.99.99.99 instead of 99.99.99.99\\myinstance and I got a connection. I'm confirming with my DBA that it somehow connected to the right database. It could be that since they've set up SQL Server with static ports it doesn't need the instance name. In SQL Server, you can't use dynamic p
ort discovery if your database is not a member of a named instance, so the JDBC is forced to use the port you specify. Most people use dynamic discovery with named instances, but probably for security reasons our DBA does not want to use it.
I really appreciate you taking time to look into this for me!
Thanks,
Anna
P.S. That Admin Console does have another problem when setting up pools with named instances.
You put it in as 99.99.99.99\\myinstance, the test will connect correctly, but when you try
to create and deploy to a server you get an error because it appears to write 99.99.99.99myinstance somewhere.
You usually have to go back to the Properties attribute and reinsert the "\\" for it to work right.you're very welcome. I will file a change request about the double back-slash...
Joe

Connecting to SQLServer 2k named Instance

Similar Messages

Maybe you are looking for