Under The Hood: Exchange ActiveSync Mailbox Log Analysis – Part 2 – Exchange Team Blog – Site Home – TechNet Blogs
Under The Hood: Exchange ActiveSync Mailbox Log Analysis – Part 2 – Exchange Team Blog – Site Home – TechNet Blogs The official Microsoft Exchange blog
Exchange 2013 Server Role Requirements Calculator Release Notes – Exchange Team Blog – Site Home – TechNet Blogs
Ok, first real post….
And yes this probably has a been covered by someone smarter and sexier than I but you have to start somewhere…..
Installed a Lync 2013 Standard Edition server on a Windows Server 2012 R2 server (my first, in the hope chest you go :)) and though I had a couple of odd issues while bootstrapping (SQL Express), it generally went well. Until-I-Started-The-Services. Everything started ok but I noticed a couple of odd event log messages:
LS MCU Infrastructure 61029
The process RtcHost(7612) received an invalid client certificate.
Certificate SN: CN=LYNC2013-STD02.fu.mydomainissecret.com, OU=IT, O=bla, L=town, S=IL, C=US
Certificate issuer name: CN=BLA, DC=BLA, DC=BLA, DC=BLA, DC=BLA.
Certificate error: 2148204816.
Followed by Incessant LS MCU Infrastructure 61035 errors
Log Name: Lync Server Source: LS MCU Infrastructure Date: 12/3/2013 2:59:21 AM Event ID: 61035 Task Category: (1022) Level: Error Keywords: Classic User: N/A Computer: LYNC2013-STD02.fu.mydomainissecret.com Description: This process was not able to update its health status The Web Conferencing Server failed to send health notifications to the MCU factory at https://LYNC2013-STD02.fu.mydomainissecret.com:444/liveserver/mcufactory/. Failure occurrences: 2044, since 12/2/2013 6:28:17 PM. Cause: Either the Front End service is not running, or poor network connectivity. Resolution: Verify that the Front End Service is available, and its machine is visible over the network. Event Xml: <Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”> <System> <Provider Name=”LS MCU Infrastructure” /> <EventID Qualifiers=”50174″>61035</EventID> <Level>2</Level> <Task>1022</Task> <Keywords>0×80000000000000</Keywords> <TimeCreated SystemTime=”2013-12-03T08:59:21.000000000Z” /> <EventRecordID>828</EventRecordID> <Channel>Lync Server</Channel> <Computer>LYNC2013-STD02.fu.mydomainissecret.com</Computer> <Security /> </System> <EventData> <Data>https://lync2013-std02.ciep.dis.anl.gov:444/liveserver/mcufactory/</Data> <Data>2044</Data> <Data>12/2/2013 6:28:17 PM</Data> </EventData> </Event>
Flabbergasted and out of ideas I turned to BING, yes thats right, BING. Google is the devil. Anyways I came across a couple posts but ultimately this resolved my issue…
- 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:
Poof, BOOM! On the arm, the error went away and all is well. Hope this is useful in some way. If it is, send a SASE with 1 billion dollars to:
I kid, I kid.