Tuesday, May 3, 2016

"Report processing stopped" on Lync Monitoring Dashboard

LYNC monitoring dashboard error:
When monitoring dashboard is opened, if you usually gets following error intermitently even after running stored procedure manually (you can refer this link to manually run stored procedure) and checking if SQL agent service is running.
Report processing stopped because too many rows in summary tables are missing in the Quality of Experience (QoE) database. To resolve this issue, run dbo.RtcGenerateSummaryTables on the QoEMetrics database.
Screenshot of error:
There is one thing about Monitoring SQL database in Lync that needs to be checked:
Owner login on SQL server agent jobs
This error also can be arised due to permission issue to run scheduled job.
You can find relative warning (event id- 208) in event viewer as below:

Solution: -
Change the owner for SQL server scheduled job that has given in event viewer warning to “sa”
Follow below steps to change owner of job:
  1. In Object Explorer, connect to an instance of the SQL Server Database Engine(Monitoring in our case), and then expand that instance.
  2. Expand SQL Server Agent, expand Jobs, right-click the job, and then click Properties.

  1. In the Owner list, select a login. Click on browse and select user “SA”.
2.    Note: You must be a system administrator to change the owner of a job.Assigning a job to another login does not guarantee that the new owner has sufficient permission to run the job successfully.


After changing the permissions, follow below steps one time and issue will be permanently resolved.

Make sure SQL server agent is running on Monitoring servers.

Open SQL Server Management Studio --> Go to QOEMetrics --> Programmability --> Stored Procedure --> go to  dbo.RtcGenerateSummaryTables --> Right click --> Execute stored procedure.

1 comment:

  1. Repetitive errors in Lync monitoring can be indicative of underlying issues affecting communication reliability. Does Gaming Improve Addressing and resolving these errors promptly is essential to maintain a seamless and error-free Lync.

    ReplyDelete