Should the Lync Server Front End (RtcSrv) service fail to start or is stuck at “Start Pending”, you may encounter the following error message when attempting to execute any Lync PowerShell cmdlet:
Get-CsPool : The target principal name is incorrect. Cannot generate SSPI context.
At line:1 char:1
+ CategoryInfo: NotSpecified: (:) [Get-CsPool], SqlConnectionException + FullyQualifiedErrorId : Microsoft.Rtc.Common.Data.SqlConnectionException, Microsoft.Rtc.Management.Xds.GetPoolCmdlet
Launching Lync Management Control Panel could also fail with the message:
Cannot find appropriate URL, please input a URL to connect Lync Server Control Panel
[ OK ] [ Cancel ]
To resolve this issue, check that network connectivity to SQL Server database instances for Lync are intact, in particular reachability by way of accessible Windows Firewall ports. A restart of SQL Server and dependent Lync services may also help.
If you run Lync Server in a Hyper-V virtualized environment and have enabled dynamic memory, ensure that sufficient startup RAM memory and memory buffer is allocated to the Front-End server pool to avoid constant disk trashing and Lync service startup failures.
Technorati tags: PowerShell, Microsoft Lync Server/Client /Lync Phone Edition / Lync Mobile
1 Comment »
One Response to “Lync Server 2013/2010: Cannot generate SSPI context”
Leave a Reply
You must be logged in to post a comment.