Hi,

Have you come across any issues in Lync 2010 where the front end server shows event log 5719. The effect is that the server “drops” of the domain. All services carry running. This basically means that all IM and all telephony stops working.  I have had this on 2 pool front end servers and also a SBS. A reboot fixes the issue but as we use lync companywide for telephony a reboot isn’t particularly great! The issue seems to appear again after a period of time e.g it maybe 4 weeks before it happens again.

Thanks
Matt

Log Name:      System
Source:        NETLOGON
Date:          21/04/2011 13:52:57
Event ID:      5719
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      LYCSBS01PR.Gazpromuk.intra
Description:
This computer was not able to set up a secure session with a domain controller in domain GAZPROMUK due to the following:
The RPC server is unavailable.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. 

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NETLOGON" />
    <EventID Qualifiers="0">5719</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-04-21T12:52:57.000000000Z" />
    <EventRecordID>7620</EventRecordID>
    <Channel>System</Channel>
    <Computer>LYCSBS01PR.Gazpromuk.intra</Computer>
    <Security />
  </System>
  <EventData>
    <Data>GAZPROMUK</Data>
    <Data>%%1722</Data>
    <Binary>170002C0</Binary>
  </EventData>
</Event>

DigbyBlack,

I am guessing you are running RTM code, I can't find any documentation on it but this was a known bug (I believe).  Please install CU1 (or 2), if this is the same issue it should correct it for you.

Hope this helps!

-kp

Hi Kevin,

thanks for your reply. i also cannot find anything on this but interesting to hear you think its a known bug!

so which patch in particular may fix it? the core components or the web components or the standard/enetrprise edition? http://support.microsoft.com/kb/2493736. although obviously i should probably apply all patches!

thanks

matt

Hi,

Are there event ID 29 and 14 accompanied ID 5719? Here is an artical posted by Terence refer to this event ID 5719.

 http://terenceluk.blogspot.com/2010/08/event-id-5719-29-error-and-event-id-14.html

Also,I suggest you update your drivers to the latest version,sometimes the old driver may also cause this problem.

Another more information:

http://support.microsoft.com/kb/938449

http://support.microsoft.com/kb/974909

Regards,

Hi sharon

no i dont see ids 29 or 14. i am running lync on Hyper-V 2008 R2 and the nic drivers are the latest (i.e the R2 integration components). I will update to CU2 and see if that helps. I dont suppose any further info is known on the possible bug? (im just curious as CU2 doesnt mention it!)

thanks

matt

Hi,

Any updates on your issue?

Regards,

Sharon

Hi,

I have had the exact same issue to days ago at a customer site. Is there any news on this issue?

Ive been through this with microsoft support. i was asked to apply the following patch:

http://support.microsoft.com/kb/2028827

so far ive not had any issues for approx 1 month now since the patch went on.

the symptons i had were that i could still RDP to the lync front end. however when on that box i couldnt get outbound connections i.e via a unc fileshare / telnet etc.... only a reboot helped.

hope the patch works for you!!

matt

In our case , we worked with MS support & below is the detail what we have done.

In our case issue was dynamic port exhaustion.

http://msexchange.me/2015/02/08/lync-2010-msmq-error-19-a-connection-with-active-directory-domain-services-cannot-be-established/