After apply KB 4470124 - front end did not start
Question
-
Hi everyone
I deployed Skype for business server 2019 standard a few weeks ago. It was operating quite well with 10 users.
On windows maintenance I performed the following administrative tasks:- Applied windows updates and sql 2016 updates till build number version 13.2.5102.14
- Apply the March 2020 update to skype, Updates for Skype for Business Server 2019
https://support.microsoft.com/en-us/help/4470124/updates-for-skype-for-business-server-2019- Restarted the Skype server and noticed that Sql automatic services tookt start automatically
After waiting for several minutes, all Skype services except the front end service startedIn this scenario, I applied this url:https://social.technet.microsoft.com/Forums/lync/en-US/d1df7ea9-56d4-496b-a35f-75d0e2096d31/troubleshooting-skype-for-business-server-frontend-service-cannot-start
and found this error:
Error: An error occurred: "Microsoft.Rtc.Common.Data.SqlConnectionException" "Could not connect to SQL server after 3 retries. Reason: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The remote computer refused the network connection.)
Connection String: Data Source=(local)\rtclocal;Initial Catalog=xds;Integrated Security=True;Application Name=Microsoft.Rtc.Management;Connection Timeout=60
I could get all group in the login
Could anyone give any additional advice to fix this issue?
Warm regards MeVs
- Edited by MeVs Thursday, April 2, 2020 7:06 AM
Answers
-
Hi MeVs!
In order to fix this issue, we recommend you try to follow these steps to see if it works.
*Go to Sql Server Configuration Manager> SQL Server Network configuration, make sure you have enabled “TCP/IP”. Then you can restart these SQL Server in SQL Server Services by right-click SQL Server <instance name> in the right pane, and select Restart.
*Make sure if you open the port in the firewall. The default instance is listening on TCP port 1433. If you are connecting to a named instance or a port other than TCP port 1433, you must also open 1434 for the SQL Server Browser service. For more details about SQL browser port requirements, you can refer to:
For more details about troubleshooting connecting to the SQL Server Database Engine, you can refer to the following link:
Best Regards,
Jimmy Yang
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.- Marked as answer by MeVs Friday, April 3, 2020 5:49 AM
All replies
-
Hi MeVs!
In order to fix this issue, we recommend you try to follow these steps to see if it works.
*Go to Sql Server Configuration Manager> SQL Server Network configuration, make sure you have enabled “TCP/IP”. Then you can restart these SQL Server in SQL Server Services by right-click SQL Server <instance name> in the right pane, and select Restart.
*Make sure if you open the port in the firewall. The default instance is listening on TCP port 1433. If you are connecting to a named instance or a port other than TCP port 1433, you must also open 1434 for the SQL Server Browser service. For more details about SQL browser port requirements, you can refer to:
For more details about troubleshooting connecting to the SQL Server Database Engine, you can refer to the following link:
Best Regards,
Jimmy Yang
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.- Marked as answer by MeVs Friday, April 3, 2020 5:49 AM
