Hello!

I am working in a lab and trying to get 2 Lync FE servers installed.  Lync 2013.  After going through all the installation steps one FE server starts fine and clients can log in.  But, the 2nd server FE service just hangs at "starting".  Then, if I stop the service on the FE that works and try on the other FE, it will start.  So, I can start the service on either FE server but only one at a time.

I think something is wrong with the Windows Fabric.  I get a lot of 2560 and 25600 events in the Event log.  Basically just saying there is a time out in the Windows Fabric communication.  I've tried countless powershell commands like Reset-CsPoolRegistrarState but the result is always the same...only one FE server can have the service running at a time.

Any help is greatly appreciated...and I mean greatly!!  Thanks!

Hi smuponies,

You can use the Get-CsPoolFabricState cmdlet with the -PoolFqdn parameter to determine the current state of your Lync 2013 pool.

In addition, did you try rebooting both Front End servers at the same time? (Its not recommend deploying a Front End pool that contains only two Front End Servers, in your case the practice is to restart both Front End Servers at the same time.)

Best regards,

Eric

• Edited by Eric_YangKMicrosoft contingent staff, Moderator Wednesday, January 28, 2015 2:26 AM

Hi smuponies,

You can use the Get-CsPoolFabricState cmdlet with the -PoolFqdn parameter to determine the current state of your Lync 2013 pool.

In addition, did you try rebooting both Front End servers at the same time? (Its not recommend deploying a Front End pool that contains only two Front End Servers, in your case the practice is to restart both Front End Servers at the same time.)

Best regards,

Eric

• Edited by Eric_YangKMicrosoft contingent staff, Moderator Wednesday, January 28, 2015 2:26 AM

Hi smuponies,

You can use the Get-CsPoolFabricState cmdlet with the -PoolFqdn parameter to determine the current state of your Lync 2013 pool.

In addition, did you try rebooting both Front End servers at the same time? (Its not recommend deploying a Front End pool that contains only two Front End Servers, in your case the practice is to restart both Front End Servers at the same time.)

Best regards,

Eric

• Edited by Eric_YangKMicrosoft contingent staff, Moderator Wednesday, January 28, 2015 2:26 AM

Hi smuponies,

You can use the Get-CsPoolFabricState cmdlet with the -PoolFqdn parameter to determine the current state of your Lync 2013 pool.

In addition, did you try rebooting both Front End servers at the same time? (Its not recommend deploying a Front End pool that contains only two Front End Servers, in your case the practice is to restart both Front End Servers at the same time.)

Best regards,

Eric

• Edited by Eric_YangKModerator Wednesday, January 28, 2015 2:26 AM

Hi smuponies,

You can use the Get-CsPoolFabricState cmdlet with the -PoolFqdn parameter to determine the current state of your Lync 2013 pool.

In addition, did you try rebooting both Front End servers at the same time? (Its not recommend deploying a Front End pool that contains only two Front End Servers, in your case the practice is to restart both Front End Servers at the same time.)

Best regards,

Eric

• Edited by Eric_YangKModerator Wednesday, January 28, 2015 2:26 AM

Have you tried both below commands with Reset-CsPoolRegistrarState?. Do not try to restart manually by your self. Let the command to do it for you and start the services back.

Reset-CsPoolRegistrarState -PoolFqdn "atl-cs-001.litwareinc.com" -ResetType QuorumLossRecovery

Reset-CsPoolRegistrarState -PoolFqdn "atl-cs-001.litwareinc.com" -ResetType ServiceReset

Hey,Have you ran the latest CU installer on the servers and ensured that fabric is patched to the same version on both servers ? I have seen version mistakes cause issues before.

Also i assume you have seen the guideline for a two node FE pool with 2013.

https://technet.microsoft.com/en-us/library/gg412996%28v=ocs.15%29.aspx?f=255&MSPPError=-2147217396

You could also look to remove fabric on the troubled server from programs and features, rerun Lync 2013 deployment wizard to reinstall and then run the CU installer to patch it. Please make sure both servers have the same CU version. You may need to run the Reset-CsPoolRegistrarState again.