How and where have you changed that port for SQL Server?
Did you restart that SQL Server after those changes?
Is there a configuration in your SCCM server where a port was defined previously?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
We have already SCCM server installed, with SQL Server on a separate server. Initially whole setup was configured with SQL server dynamic port. I have now changed SQL port from dynamic to static 1433 from SQL Server Configuration Manager.
Now SCCM Console won't connect. What else i need to change?
hman.log below:
[HYT00][0][Microsoft][SQL Server Native Client 11.0]Login timeout expired SMS_HIERARCHY_MANAGER 8/26/2022 5:34:20 AM 8952 (0x22F8)
[08001][10061][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. SMS_HIERARCHY_MANAGER 8/26/2022 5:34:20 AM 8952 (0x22F8)
Failed to connect to the SQL Server, connection type: SMS ACCESS. SMS_HIERARCHY_MANAGER 8/26/2022 5:34:20 AM 8952 (0x22F8)
STATMSG: ID=3303 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=SCCMServer.domain.com SITE=A01 PID=2384 TID=8952 GMTDATE=Fri Aug 26 01:34:20.517 2022 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 LE=0X0 SMS_HIERARCHY_MANAGER 8/26/2022 5:37:47 AM 8952 (0x22F8)
Cannot connect to the site source on the database, sleep 5 minutes... SMS_HIERARCHY_MANAGER 8/26/2022 5:37:47 AM 8952 (0x22F8)
[08001][-2146893055][Microsoft][SQL Server Native Client 11.0]SSL Provider: The handle specified is invalid SMS_HIERARCHY_MANAGER 8/26/2022 5:37:56 AM 4800 (0x12C0)
[08001][-2146893055][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection SMS_HIERARCHY_MANAGER 8/26/2022 5:37:56 AM 4800 (0x12C0)
Failed to connect to the SQL Server, connection type: SMS ACCESS. SMS_HIERARCHY_MANAGER 8/26/2022 5:37:56 AM 4800 (0x12C0)
[08001][-2146893055][Microsoft][SQL Server Native Client 11.0]SSL Provider: The handle specified is invalid SMS_HIERARCHY_MANAGER 8/26/2022 5:37:56 AM 4800 (0x12C0)
[08001][-2146893055][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection SMS_HIERARCHY_MANAGER 8/26/2022 5:37:56 AM 4800 (0x12C0)
Failed to connect to the SQL Server, connection type: SMS ACCESS. SMS_HIERARCHY_MANAGER 8/26/2022 5:37:56 AM 4800 (0x12C0)
IsSafeToGetSCF: Failed to get SQL connection SMS_HIERARCHY_MANAGER 8/26/2022 5:37:56 AM 4800 (0x12C0)
Site is in maintenance mode, sleep 10 minutes SMS_HIERARCHY_MANAGER 8/26/2022 5:37:56 AM 4800 (0x12C0)
[08001][10061][Microsoft][SQL Server Native Client 11.0]TCP Provider: No connection could be made because the target machine actively refused it. SMS_HIERARCHY_MANAGER 8/26/2022 5:37:57 AM 2072 (0x0818)
[HYT00][0][Microsoft][SQL Server Native Client 11.0]Login timeout expired SMS_HIERARCHY_MANAGER 8/26/2022 5:37:57 AM 2072 (0x0818)
[08001][10061][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. SMS_HIERARCHY_MANAGER 8/26/2022 5:37:57 AM 2072 (0x0818)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS. SMS_HIERARCHY_MANAGER 8/26/2022 5:37:57 AM 2072 (0x0818)
CHierarchyManager::CaptureRunningQueries: Failed to get SQL connection SMS_HIERARCHY_MANAGER 8/26/2022 5:37:57 AM 2072 (0x0818)
running queries will be polled in 600 seconds... SMS_HIERARCHY_MANAGER 8/26/2022 5:37:57 AM 2072 (0x0818)
How and where have you changed that port for SQL Server?
Did you restart that SQL Server after those changes?
Is there a configuration in your SCCM server where a port was defined previously?
This issue has been resolved. Thank you for your response.
Hi,
Here is the solution:
Step 1
Change SQL Ports in SQL Server configuration Manager from Dynamic to Static 1433
Step 2
Run Microsoft Configuration Manager wizard and in SQL Setup related change port with ServerFQDN,1433 whatever dynamic port there is. Click on Next and wait for the setup to finish successfully
Hi,
Thanks very much for your feedback and sharing. We're glad that it's working ok now. It's appreciated that you could click "Accept Answer" to the helpful reply, this will help other users to search for useful information more quickly. Here's a short summary for the problem.
Problem/Symptom:
Failed to connect with error after changing SQL Server port from dynamic to static 1433.
Solution/Workaround:
Step 1
Change SQL Ports in SQL Server configuration Manager from Dynamic to Static 1433
Step 2
Run Microsoft Configuration Manager wizard and in SQL Setup related change port with ServerFQDN,1433 whatever dynamic port there is. Click on Next and wait for the setup to finish successfully
Thanks again for your time! Have a nice day!
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.