I am having trouble when publishing my topology after creating an enterprise pool. I get the below error.
Anyone know what to check to prevent this?
SqlConnectionFailure: Failed to connect to SQL Server | 7/8/2015 3:09:35 PM | Error |
|
Technology Tips and News
I am having trouble when publishing my topology after creating an enterprise pool. I get the below error.
Anyone know what to check to prevent this?
SqlConnectionFailure: Failed to connect to SQL Server | 7/8/2015 3:09:35 PM | Error |
|
It would appear the topology builder is attempting to deploy its databases in an instance named LyncEnterprise, to start can you confirm that you have manually deployed a SQL named instance called LyncEnterprise on your SQL server. If you have done that correctly, then you should see a SQL service running on that SQL server with the instance name in brackets next to it. Can you confirm that service exists and is in a running state on the SQL server?
Kind regards
Hi _Broseph,
If you have a named SQL instance, please check the services status on SQL Server and make sure these services are in running status.
For example, you should be able to see the following services.
SQL Server (LyncEnterprise)
SQL Server Analysis Services (LyncEnterprise)
SQL Server Reporting Services (LyncEnterprise)
SQL Server Agent (LyncEnterprise)
Best regards,
Eric
I only see (MSSQLSERVER) for all of those services.
I just want to add the Lync DB to our existing SQL server. I dont want any new services.
Hi _Broseph,
It's recommend to use a separate SQL instance for Lync Server.
If you did not create a separate SQL ubstance for Lync Server, please check the topology configurations and make sure that you selected the "Default instance".
Best regards,
Eric
Hi _Broseph,
If you decide to use "Defalut Instance" , Lync will automaticly create a named instance "RTC" on your SQL Server.
RTC is the default name of the Lync instance.
Best regards,
Eric