When trying to open the whiteboard, the following errors were logged on the front end server:
Event ID 51021 , Source LS MCU Factory
The MCUFactory failed to find an Web Conferencing Server to service an web conferencing modality request.
Cause: All Web Conferencing Servers are unavailable or overloaded.
Resolution:
Verify that all Web Conferencing Servers are available and not overloaded. If overloaded deploy and extra server to distribute load.
Event ID 32069 , Source LS User Services
The Mcu Factory returned failure for a request sent to it. Conferencing requests for this Mcu type will be retried but if this error continues to occur conferencing functionality will be affected.
Mcu Type: data-conf
Cause:Mcu factory not being provisioned or functioning incorrectly.
Resolution:
Ensure that the Mcu Factory is provisioned and functioning correctly. If any network related errors are reported by the Mcu Factory ensure that they are resolved.
Now these errors weren't exactly helpful, as this was a new install of Lync 2013 so we had a 10 pilot users on there. So there is no way it could be an overloaded conferencing server.
I started looking at Lync 2013 with 2012 R2 issues and came across
this Microsoft KB article: http://support.microsoft.com/kb/2901554/en-us
This doesn't mention the errors I was getting above, but I thought I'd give it a go anyway.
Resolution:
- Click Start, type regedit in the Start search box, and then click regedit.exe in the results list.
- Locate the following registry subkey: HKLM\System\CurrentControlSet\Control\SecurityProviders\Schannel
- Right-click Schannel, and then click New DWORD (32-bit) value.
- Type EnableSessionTicket, then press Enter.
- Right-click EnableSessionTicket, and then click Modify.
- Change the existing value to 2, and then press Enter.
- Exit Registry editor.
- Open the Lync Server Management Shell.
- Run the following Lync Server PowerShell commands in the given order: Stop-CsWindowService
Start-CsWindowsService
After doing these steps, whiteboards started working immediately! As stated in the KB article, it's a fully supported workaround for Lync 2013. So I'll be doing this on all deployments going forward on Server 2012 R2 until Microsoft fixes it.
This fixed solved my issue, Feb 2020 on 6 year old Lync 2013/Server 2012 R2 installation.
ReplyDeleteAttempting to get into conferences, after entering ID and being accepted as leader, got the message "Sorry cant connect". After removing all the conferencing setup and replacing I got the error in this post with voice message "having trouble accessing the system". The registry fix cured it.
Thanks