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

Similar Messages

Database instance for SCCM 2012 and WSUS on a single primary site server

I am going to install SCCM 2012 and its SQL database on a single physical server. This is going to be a single primary site server. The default SQL instance will be dedicated to SCCM 2012 with no other named instances to be added on the SQL server down
the road.
During the WSUS server role installation, there is the Database Options page asking for using (1) Windows Internal Database, (2) existing db server on this computer, or (3) an external db server.
Since SCCM 2012 doesn't share db instance with others, how should I handle the WSUS db that's going to be hosted on the same SCCM/SQL physical server? Do I really need to create a separate SQL instance just for the WSUS db?
Thanks and regards.

Even though you can do it, it is the best practice to have SCCM 2012 and WSUS installed on separate instances.
http://technet.microsoft.com/en-us/library/hh692394
When the Configuration Manager and WSUS databases use the same SQL Server and share the same instance of SQL Server, you cannot easily determine the resource usage between the two applications. When you use a different SQL Server instance
for Configuration Manager and WSUS, it is easier to troubleshoot and diagnose resource usage issues that might occur for each application.

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

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 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

Required access for SCCM 2012 R2 Client End

Hi all,
What is minimum level of access required for SCCM 2012 client machines management ( Deploy , Discovery , agent install …etc) , we have an account called clientdeploy , is that account is mandatory
to have local administrators privilege on all client machine to manage everything , is that Microsoft recommended one ?
Sengo

No, Not required this account to be local admin in all client.
If you want access required for sccm 2012, for deploying app., O.s and managing client, this account must be member of sms group such as configmgr remote control users for remote tool
For more details, you can refer below link
http://technet.microsoft.com/en-us/library/hh427337.aspx
Also I recommended to ask your question in
SCCM Forum
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

SQL 2012 Enterprise SP1 installation for SCCM 2012 R2

I am just starting to install SQL 2012 with SP1 Enterprise for SCCM 2012 R2.
Does anyone have a step by step guide for this install please
I am planning to install SQL 2012 with SP1 Enterprise as a physical install which I intend to geo cluster later on
Also I am thinking of installing WSUS on a separate server and get my SCCM 2012 servers (1 primary and 3 secondary) to use this server - would appreciate some help on how this can be setup as well

That doesn't make sense to me. Both versions are fully supported on virtual and physical platforms.
Also, I'm with Garth - local SQL all the way.
Here are my thoughts on the subject
http://www.gerryhampsoncm.blogspot.ie/2013/10/configmgr-sql-some-tips.html
ConfigMgr is not a real-time product like Exchange, for example. A certain amount of downtime can be tolerated. I would spend more time implementing a robust backup solution, rather than trying to implement high availability.
You should be able to recover a ConfigMgr site from SQL backup in a couple of hours.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

How to Custom Report using sql server report builder for SCCM 2012 SP1

Hi ,
I am new to database, if i want to create a manual report using sql server report builder for SCCM 2012 SP1, what step should i take.
i want to create a report in which computer name, total disk space, physical disk serial no come together. i already added class (physical disk serial no.) in hardware inventory classes. refer snapshot

Hi,
Here is a guide on how to create custom reports in Configuration Manager 2012, it is a great place to start, change to the data you want to display instead.
http://sccmgeekdiary.wordpress.com/2012/10/29/sccm-2012-reporting-for-dummies-creating-your-own-ssrs-reports/
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Remote SQL DB Instance Connection error while deplyting the Standalone Primary Site

Hi
I am getting error as The RPC server is unavailable .(Exception from HRESULT:0x8000706BA)
while adding the Remote SQL DB named instance. I am also attaching ConfigMgr Setup log can you please advice..
Windows Firewall is turned off on SCCM Primary Site server and SQL DB server.
I am able to telnet over port 1433 of SQL DB server, Dynamic Port is not Configured for SQL DB Named Instance its only on TCP 1433.
Shailendra Dev

Hi,
Please confirm the ports below are allowed.
Site Server --> SQL Server
During the installation of a site that will use a remote SQL Server to host the site database, you must open the following ports between the site server and the SQL Server:
Server Message Block (SMB) TCP 445
RPC Endpoint Mapper UDP TCP 135
RPC TCP DYNAMIC (See note 6, Dynamic ports)
Reference:https://technet.microsoft.com/en-us/library/hh427328.aspx#BKMK_CommunicationPorts
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Dupremove.ncf unable to connect to SQL DB instance

I have ZDM7SP1_IR3a, my inventory database is running as a named instance on SQL2005. I am unable to get the dupremove module to connect to the data base. I keep getting a message:
Trying to (re)connect to the database -> mw_dba
Jdbc:sqlserver://10.10.11.55:1433;selectMethod=cursor
Com.microsoft.sqlserver.jdbc.SQLServerException: The TCP?IP connection to the host
Has failed. Java.net.ConnectException: Connection refused
at com.microsoft.sqlserver.jdbc.SQLServer Connection.connect(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServer Connection.connect(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.conne ct(Unknown Source)
at java.sql.DrierManager.getConnection(DriverManager. java:512)
at java.sql.DrierManager.getConnection(DriverManager. java:140)
at com.novell.zenworks.desktop.inventory.storer.Datab aseOperator.create(DatabaseOperator.jav:830)
at com.novell.zenworks.desktop.inventory.storer.Datab aseOperator<init>(DatabaseOperator.jav:589)
at com.novell.zenworks.desktop.inventory.storer.Datab aseOperator.main(DatabaseOperator.jav:7162)
Could not connect to database.
My dupremove.ncp is as follows:
java -ns -sn"ZENworks Inventory Dupremove utility" -neh -mx128m -classpath $tmppath;"$classpath" -Djava.compiler= com.novell.zenworks.desktop.inventory.storer.Datab aseOperator -host=10.10.11.55 -listwsdup -dbtype=2 -sid=mgmtdb -port=3855
It appears that this module is ignoring the port number provided. Is there a way to get it to accept the port given so that the connection to the database can be made?
I appreciate any and all suggestions.

DMPotter,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

MAP v 9.1 Issue detecting SQL Named Instances

I have an issue where the Map toolkit is connecting to only the 1st Named instance on a multi-instance SQL Server so I am unable to perform a full database inventory yet alone performance analysis.
My 1st thought was around port blocking etc. However we do not have any port blocking configured "within" the domain and I have carried out port connectivity tests from the dedicated server where MAP is installed to several ports on different SQL
servers and can confirm that the ports under which each instance is talking are open.
Configuration
Scenario - SQL Server with Databases database details
WMI - Domain Account with local Server admin rights
SQL - SQL Native account with SQL Server SA rights.
I have tested the native SQL account on those failed instances to confirm that all is in order
I have tested that the Dynamic ports under which SQL is running are open and accessible from the MAP Server
Please can anyone point me in the right direction. What am I missing ?

I'm not an expert with WMI but to my knowledge MAP WMI pulls from ServerNetworkProtocolProperty and SqlServiceAdvancedProperty classes, which may not have any information for those instances. If you run WBEMTEST.exe and connect to \\ServerName\root\Microsoft\SqlServer\ComputerManagement11
(for SQL 2012, Management10 for SQL 2008 and Management12 for SQL 2014), you can click "Query" and try "Select * from ServerNetworkProtocolProperty". In the case of my environment it only returns information for the instance that MAP picked
up, and misses the other instance that failed. As to why the failed instance doesn't have that WMI information is beyond me, but hopefully that can give you a starting point.
Regards,
Nick

VMM (2012 R2) PRO/Operations Manager Integration Requires Named Instance for SSAS -- Which is Great in a NOT Clustered Environment

This is my third or maybe 4th time posting this question... surely I can't be the only person that has run into this issue...
Subject more or less captures the essence of my question... I have a clustered SQL 2012 (SP2) environment that runs on 3 nodes (active-passive-passive), one of which runs Analysis Services. As I've come to learn (and likely everyone already knows) SSAS in a
clustered configuration is _ONLY_ accessible using the hostname, FQDN, or VIP. Addressing the named instance results in a failure (I think this is partially a SQL browser bug as looking closely at the requests to SSAS using a named instance results in the
browser issuing a bogus TCP port where no service is actually running). Additionally, not providing a named instance in the VMM console UI results in an error message:
Please enter SSAS instance name
Would greatly appreciate any guidance on this issue. Thank you.

Since you're on your 4th time of asking, let me at least say I'll try to make this your last.
While I haven't got an answer this exact minute, I'll look into it tomorrow as I have access to a clustered SSAS that I can play with.
Probably the reason no-ones answered so far is that for VMM the SSAS instance must be on the same instance as the SCOM Reporting Services and since that can't be clustered most will install standalone.
Regards,
Steve
<a href="http://systemcenter.ninja/">My System Center Blog</a>

Unable to Connect to SQL 2000 Instance from Windows Server 2012 environment

We have a windows server (TEST) 2012 environment , where our test SQL Server 2012 instance is hosted.
We have a different (DEV) Server (windows 2000) where a SQL Server 2000 instance is present.
When I RDP to our Windows Server 2012 box, I cannot connect to the SQL 2000 server instance from SQL Management Studio. (whereas I can connect to
the same server from my local machine which has windows 7 and SQL 2012 installed).
This is the error i see -
"A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name
is no longer available.) (.Net SqlClient Data Provider)"
When run from SQL Agent Service from TEST (A Job which tries to connect to that SQL 2000 instance to read some data using SSIS) , we get the following
error -
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "[DBNETLIB][ConnectionRead
(recv()).]General network error. Check your network documentation.".
The same SSIS package runs successfully from my local machine.
Please, could someone advice how to resolve this situation?

Thanks Olaf.
Its just that we have legacy systems here in our company, who, for some reason haven't upgraded their older infrastructure, whereas they have set up new Windows 2012/SQL 2012 environments for the newer sql instances where they want to transition to !
Not sure what the solution is honestly. It is affecting our timelines now. The infrastructure team needs to take a decision now, as to what to do.
I do have to add, we were able to connect to these "older" servers from our Windows 7 client machines which have SQL 2012 - both from SQL management studio & SSIS (using OLE-DB Provider for SQL Server).

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

ODBC--connection to 'SQL Serverservername' failed for one user but not another

In Win7, we're linking tables in an MS Access 2010 db to tables in a SQL Server 2008 R2 db. The driver user by the File dsn is SQL Server version 6.01.7601.17514 & we're using SQL Server Authentication.
For some reason, one user gets the msg "ODBC--connection to 'SQL Serverservername' failed" before they're even asked for a password, but for other users, the prompt comes up and when they uncheck the Windows Auth box, they enter their password
and connect successfully to the SQL Server db. Both users have db_datareader access to the SQL Server db.
I had the user that gets the error msg log onto my PC and they get the same error (yet it works for me.)
This user was, however, able to successfully relink the tables, but then when we closed the access db and opened it again, the user got the "ODBC--connection..." error agin.
I'm stumped as to why this is happening for one user.

Hello Knellen,
Please help to collect more log information regarding this issue, such as windows event log, SQL Sever log information. They are helpful for us to troubleshoot it.
Regards,
Elvis Long
TechNet Community Support

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

Similar Messages

Maybe you are looking for