locked
Event ID 25020 in the Lync Server Log RRS feed

  • Question

  • I am running an enterprise front end pool for Lync 2010 fully patched with the latest cumlitive updates installed. I am experiencing random drop calls from our Snom 821 IP phones. There is an error on the phone "internal server error" when the call drops.

    In trying to troubleshoot this I found this error in the Lync Server log:

    The Quality-Metric server returned invalid response. The Quality metric reports are not sent to the server.
    Response Code: 500
    Response Text: The server encountered an unexpected internal error
    QoE Agent:
    QoE GRUU: sip:lyncpool.mydomain.lcl@mydomain.com;gruu;opaque=srvr:HomeServer:MZ7UNp_cMV2q-G3pRjPYNAAA
    Diagnostics Code: 4078
    Diagnostics Source: lyncsrv1.mydomain.lcl
    Diagnostics Reason: Internal Error: Failed to get the sender info
    Cause: Either the Quality-Metric server is not running or unreachable.
    Resolution:
    Verify that Quality-Metric server is reachable from the computer running Lync Server. The response text may also indicate a configuration issue. 

    I tried researching this error and I am finding nothing. Anyone encounter anything similar?

    thank you


    Steve

    Monday, April 2, 2012 7:07 PM

Answers

  • Hi,Steve,

    Please check there is no service failure or performance issue on your Lync server(FE,Mediation Server) in event log.

    Would you please turn on Lync server logging tool,select S4,SIPStack and Mediation Server with all tags,reproduce the issue and analyze the log with snooper tool,also you can use Netmon to caputure the network traffic to see if the  trace log.Details you can check http://blogs.technet.com/b/daveh/archive/2009/01/25/how-to-troubleshoot-ocs-mediation-server-quality-of-service-event-id-25022.aspx (Although it's for OCS,it's also available for Lync)

    B/R

    Sharon


    Sharon Shen

    TechNet Community Support

    ************************************************************************************************************************

    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.

    • Proposed as answer by Sharon.Shen Thursday, April 19, 2012 11:09 AM
    • Marked as answer by Sharon.Shen Wednesday, April 25, 2012 10:21 AM
    Thursday, April 5, 2012 2:18 AM
  • The error was not tied to the Snom drops or vice versa.

    I did review all the services and found that the I was missing a web service in IIS. Once I added the additional web service for the error went away. I am sorry I forget exactly which web service other than when I went into the IIS setup it was easy to figure out. Sorry I can't be of more help. I should of documented the fix better.


    Steve

    • Marked as answer by SteveHDI Monday, May 7, 2012 1:21 PM
    Monday, May 7, 2012 1:21 PM
  • I wish I could be of more help.

    If I remember correctly, I really think it had to do with "message queing "

    Also check this list

    Sorry I am not of more help.


    Steve

    • Marked as answer by SteveHDI Friday, May 18, 2012 4:09 PM
    Friday, May 18, 2012 4:09 PM

All replies

  • It Looks like the Report data for QoE could not be send to the Monitoring server.

    To troubleshoot the Snom calls use the ocslogger tool on the Lync Server with S4,Sipstack and use the snooper tool from the Lync ressourcekit to find the Problem of the Snom phone.


    regards Holger Technical Specialist UC

    Monday, April 2, 2012 7:28 PM
  • Thanks I am looking at both. Any clues on how to check the Report data for QoE?

    Is that something I may have missed in the control panel. Like I said, i researched that error and didnt get much info on where to look to solve it

    Steve


    Steve

    Monday, April 2, 2012 8:12 PM
  • Do you have Report data. Is message queing installed on all server?

    regards Holger Technical Specialist UC

    Monday, April 2, 2012 9:00 PM
  • Yes from the control panel I have report data. Message queing is installed on the servers generating the errors.

    Steve

    Monday, April 2, 2012 9:04 PM
  • Hi,Steve,

    Please check there is no service failure or performance issue on your Lync server(FE,Mediation Server) in event log.

    Would you please turn on Lync server logging tool,select S4,SIPStack and Mediation Server with all tags,reproduce the issue and analyze the log with snooper tool,also you can use Netmon to caputure the network traffic to see if the  trace log.Details you can check http://blogs.technet.com/b/daveh/archive/2009/01/25/how-to-troubleshoot-ocs-mediation-server-quality-of-service-event-id-25022.aspx (Although it's for OCS,it's also available for Lync)

    B/R

    Sharon


    Sharon Shen

    TechNet Community Support

    ************************************************************************************************************************

    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.

    • Proposed as answer by Sharon.Shen Thursday, April 19, 2012 11:09 AM
    • Marked as answer by Sharon.Shen Wednesday, April 25, 2012 10:21 AM
    Thursday, April 5, 2012 2:18 AM
  • Hey Steve,

    Did you find a resolution to this issue?

    Interested cause I am experiencing the same thing at the moment.

    Cheers

    Arun

    Wednesday, May 2, 2012 12:07 AM
  • The error was not tied to the Snom drops or vice versa.

    I did review all the services and found that the I was missing a web service in IIS. Once I added the additional web service for the error went away. I am sorry I forget exactly which web service other than when I went into the IIS setup it was easy to figure out. Sorry I can't be of more help. I should of documented the fix better.


    Steve

    • Marked as answer by SteveHDI Monday, May 7, 2012 1:21 PM
    Monday, May 7, 2012 1:21 PM
  • Hey Steve,

    If its not too much to ask if you could send a list of installed services, that would be great because no matter what I try I am still getting this error. 

    a r u n ( d o t ) o a k l e y ( a t ) h o t m a i l ( d o t ) c o m

    This is currently happening on my Branch Appliance but my main FE server isn't showing these errors. all IIS services are the same on both and i am loosing my mind =)

    Friday, May 18, 2012 3:42 AM
  • I wish I could be of more help.

    If I remember correctly, I really think it had to do with "message queing "

    Also check this list

    Sorry I am not of more help.


    Steve

    • Marked as answer by SteveHDI Friday, May 18, 2012 4:09 PM
    Friday, May 18, 2012 4:09 PM
  • Hey Steve, Bummer already have message queing. It doesn't happen for every call just some.

    I appreciate the time to respond! Thanks

    Arun

    Monday, May 21, 2012 12:05 AM