Iniciar sesión
 
InicioBibliotecaAprendizajeDescargaSoporteComunidadForos
Recursos para Profesionales de TI >
> 
> 
Random failure while sending plain IM message...

Pregunta Random failure while sending plain IM message...

  • jueves, 26 de enero de 2012 19:12
     
     
    Inicie sesión para votar
    0
    Occasionally, we are seeing a failure while sending messages to other Lync users. We are still in pilot, so we only have 110+ active users right now. Usually there will be a failed message, then all messages will send with no error after the one failure. Monitoring server is in place and we find the following diag: 4154; reason="Endpoint is not currently registered and a re-registration required for this operation."; HRESULT="0xC3EE79F9(ES_E_CLIENT_REGISTRATION_REQUIRED)"; source="one_of_the_servers_in_my_pool.com" Any assistance is greatly appreciated. We are replacing an OCS2007R2 installation with Lync and never saw anything like this in OCS. OCS Environment had the same approx. number of end-users and was poorly engineered by an outside vendor. Lync BPA shows no errors. Thank you, Fred
     

Todas las respuestas

  • lunes, 30 de enero de 2012 9:18
    Moderador
     
     
    Inicie sesión para votar
    0

    The pool hardware for the Lync FE server can cause this issue.

    Do you deploy Lync server in the same domain with ocs2007r2 without merger?

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • lunes, 30 de enero de 2012 16:34
     
     
    Inicie sesión para votar
    0

    We do have OCS2007R2 in place still and the topologies are merged.

    I actually plan to be able to decom OCS this week leaving only the CWA server that is already pointing toward our Lync pool.

     
  • miércoles, 01 de febrero de 2012 5:45
    Moderador
     
     
    Inicie sesión para votar
    0

    Do you decommission the ocs servers successfuly?

    Please have a try to edit the internal SRV record point to Lync FE server to check if the issue occurs again.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • miércoles, 01 de febrero de 2012 18:11
     
     
    Inicie sesión para votar
    0

    Will do - decom is sceduled for tomorrow AM. Last user (I literally have 1 left), is getting migrated to Lync today.

     

    Fred

     
  • jueves, 02 de febrero de 2012 19:35
     
     
    Inicie sesión para votar
    0

    OCS fully decommisioned and OCSPool removed. Topology re-merged. OCS Servers no longer showing any connections at all to the lync environment via NETSTAT.

    Still getting intermittnet failures:

           

    Request:

     

    BYE

    Response:

     

    200

    Diagnostic ID:

     

    52093

    Category:

     

    Expected

    Component:

     

    Client: Error Messages

    Reason:

    		  

    Conversation suspended due to a loss of network

     

    The interesting thing here is that Netoworking shows no failure at this user's endpoint. They are actually conencted via a VPN appliance. No failures were reported on either end. No other services were affected. No other on-site hardware reported any COMM loss. This would include VOIP and an Local AP that all continued to maintain a solid connection to our central office.

     

     
  • lunes, 27 de febrero de 2012 16:19
     
     
    Inicie sesión para votar
    0

    Any update on this?

    I'm having a similar error, only appears to impact users outside of the corporate firewall.

    When in Web conference, they sporadically get kicked out and then rejoin automatically.

    I don't see anyting in event logs on the Lync edge or on the Frontend servers. 

    The only error I do find is on the monitoring server like yours.

    No OCS co-existence.

    HW Resource usage looks ok

    I did try changing the binding order on the edge so the inside NIC is at the Top, waiting to see if this improves things. 

     
  • martes, 28 de febrero de 2012 19:39
     
     
    Inicie sesión para votar
    0

    Nothing new... I did see a post on one of the blogs that points to Mobility for this type of issue. We have Mobility installed, but no active end-points. Not sure if it ties in or not yet...

    JMJJ - are you running Mobility?

    -Fred

     
  • jueves, 08 de marzo de 2012 16:04
     
     
    Inicie sesión para votar
    0

    Nope, no mobility on ours. 

    I did see in the edge server logging tool that network connectivity was lost.  Still trying to determine if Lync dropped it or if it was as a result of something else.

     
  • jueves, 08 de marzo de 2012 19:40
     
     
    Inicie sesión para votar
    0

    I am prepping to roll out CU5 and will review my mobility install as well. I am wondering if Lync is just sensitive enough to detect a break in service that may not be enough of a break to cause an VPN tunnel to drop...

    -Fred

     
  • jueves, 22 de marzo de 2012 17:59
     
     
    Inicie sesión para votar
    0

    I deployed CU5 and also steped through the Mobility deploy again as well as setting up the edge for Push notifications.

    I have not seen the error since.

    -Fred