none
Lync 2013: Internal Server Error when dialing a response group

    Question

  • Hi!

    I have created a simple response group in Lync 2013, just a round robin to agents in a group, and test it with Yealink  Phone(with an internal testing version for lync).

    When I dial this group , I get "Internal Server Error" on the device and in the event log on the Lync server the following errors are present:

    Unhandled exception occurred when the service was running on a thread pool thread used by the platform.

    Unhandled exception: System.Reflection.TargetInvocationException - Exception has been thrown by the target of an invocation.
    Inner Exception: System.FormatException - Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

    Cause: Unhandled exception.
    Resolution:
    Restart service.

    PS: I've found a similar question asked by somebody else. It seems that ms has fixed it on Lync 2010, how could it happen again on Lync 2013 ? Can someone help me ?

    https://social.technet.microsoft.com/Forums/lync/en-US/d6b06d43-2749-429f-a096-9276e6500ac3/lync-2010-internal-server-error-when-dialing-a-response-group?forum=ocsvoice

    PS: It works well when answer a call to the RG.


    • Edited by gcchen7 Monday, November 17, 2014 7:47 AM
    Monday, November 17, 2014 7:43 AM

Answers

All replies

  • Does a  normal call from the Yealink  Phone to number assigned to Lync user work fine?

    What error response do you see in the SIP logs?


    PLEASE REMEMBER, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answered"

    Monday, November 17, 2014 4:29 PM
  • Hi,

    You can troubleshoot with the following steps:

    1. Restart Lync Services on FE Server.
    2. Change to other Touting method (such as Parallel, Longest idle) to have a test.
    3. As Yealink Phone is not certified by Lync now, please try to use the Lync certified IP Phone to test the issue:

    http://technet.microsoft.com/en-us/office/dn788944.aspx

    Best Regards,

    Eason Huang


    Eason Huang
    TechNet Community Support

    Tuesday, November 18, 2014 2:10 AM
    Moderator
  • It works fine in any other scenarios. 

    here's what the Lync Server responses when calls RG from the Yealink Phone.

    SIP/2.0 500 Internal Server Error
    Authentication-Info: TLS-DSK qop="auth", opaque="FD91B562", srand="CB38310C", snum="30", rspauth="dfa0e518d72579f449b5b396106f025f03a3db90", targetname="FE.cohowinery.cohovineyard.com", realm="SIP Communications Service", version
    Via: SIP/2.0/TLS 192.168.20.54:5061;received=192.168.20.54;branch=z9hG4bK426095825;rport;ms-received-port=1290;ms-received-cid=2051D00
    CONTENT-LENGTH: 0
    From: "coho 1"<sip:coho1@cohowinery.cohovineyard.com>;tag=2149086591;epid=00156522332200
    To: "info"<sip:+14257273011@cohowinery.cohovineyard.com;user=phone>;tag=9f7e2d16a3;epid=A5F1017C79
    CSeq: 1 INVITE
    Call-ID: 166602857
    Priority: Normal
    P-Asserted-Identity: "info"<sip:info@cohowinery.cohovineyard.com>,<tel:+14257273011>
    Server: RTCC/5.0.0.0 Response_Group_Service
    MS-Conversation-ID: 3461253581
    ms-diagnostics: 1033;reason="Previous hop server component did not report diagnostic information";Domain="cohowinery.cohovineyard.com";PeerServer="fe.cohowinery.cohovineyard.com";source="FE.cohowinery.cohovineyard.com"
    ms-diagnostics-public: 1033;reason="Previous hop server component did not report diagnostic information";Domain="cohowinery.cohovineyard.com";PeerServer="fe.cohowinery.cohovineyard.com"

    Tuesday, November 18, 2014 10:35 AM
  • I've tried to restart the RG service, but the error still remains.

    It's works fine when I call RG from Lync Client.

    And it also works fine when I call RG from Yealink Phone under the other Server (Federation).

    Tuesday, November 18, 2014 10:55 AM
  • Hi,

    Please try to install the latest update and reboot the server to test the issue again:

    http://technet.microsoft.com/en-us/office/dn788954

    Best Regards,

    Eason Huang


    Eason Huang
    TechNet Community Support

    • Marked as answer by Eason HuangModerator Monday, November 24, 2014 2:24 AM
    • Unmarked as answer by gcchen7 Thursday, January 08, 2015 6:34 AM
    • Marked as answer by gcchen7 Thursday, January 08, 2015 6:34 AM
    Wednesday, November 19, 2014 1:28 AM
    Moderator
  • Hi,

    I am having similar issue with Skype for Business Server. When we dial to response groups we get on SfB Logging:

    "500 Internal Server Error"

    But event id 31149 doesn't appear on event viewer.

    Also if we assign these numbers to common user it works and we have the latest updates deployed on SfB servers.

    Thanks for any help,


    Dario


    Dario Woitasen | MCSE Lync Server 2013/Exchange Server 2013 | MCITP: Enterprise Messaging Administrator 2007/2010, Lync Server 2010 Administrator, Office 365 | MCSA Windows Server 2012


    Sunday, September 20, 2015 11:40 PM
  • Hello,

    i am getting this error as well during the migration from Lync Server 2010 to Skype For Business.

    Old RGS are working just fine but as soon as I am migrating with "move-csrgsconfiguration" i am getting this error.

    This also happens when I create a RGS which is completely new and hosted on the new Skype For Business Pool.

    SIP and PSTN Calls will immediately fail to establish with the 500 Internal Server Error.

    Thanks for any help

    Daniel

    Thursday, September 24, 2015 3:55 PM
  • Hi We see the exact same behaviour - some external calls are failing to RGS with 500 Internal Server error. Those that fail will do this everytime - and thoose that work will work everytime - no real pattern in which fails and which dont - but most fail
    Wednesday, November 04, 2015 9:02 AM
  • Hi,

    Could you try to remove one of these RGS and create it again?


    Dario Woitasen | MCSE Lync Server 2013/Exchange Server 2013 | MCITP: Enterprise Messaging Administrator 2007/2010, Lync Server 2010 Administrator, Office 365 | MCSA Windows Server 2012

    Wednesday, November 04, 2015 1:32 PM