Call report never finishes

[AlexanderReichert]

I have a call report that apparently is stuck in status running. How do I solve that?

 

[YiannisH_3CX]

Hello @AlexanderReichert

If the report has been stuck at running, try restarting the PBX system service and let us know if that resolves your issue.

 

[AlexanderReichert]

Hello @YiannisH_3CX
I restarted the PBX system - but the report is still stuck in running.

 

[YiannisH_3CX]

What PBX version are you running? You can see the exact build number on the Dashboard, under the Information column next to the licence version. For example 16.0.1581
Also can you delete the running report or not?
The best way to troubleshoot this is to look into the system service report and see if the report is still running or if you get an error.

 

[AlexanderReichert]

Version: 15.5.15502.6
No I cannot delete the report. that option is greyed out.
Where do I find the system service report?

 

[YiannisH_3CX]

You can navigate to Dashboard / Activity log / Logs and select instance. You should be able to see the log there.

 

[AlexanderReichert]

the only remotely close to reporting in the log is this.
I don't think that the report is still running. I think the report just reflects the wrong status.

2019/04/10 17:48:17.282|630|0021|Excpt|System.ArgumentException: The supplied DateTime represents an invalid time. For example, when the clock is adjusted forward, any time in the period that is skipped is invalid.
Parameter name: dateTime
at System.TimeZoneInfo.ConvertTime(DateTime dateTime, TimeZoneInfo sourceTimeZone, TimeZoneInfo destinationTimeZone, TimeZoneInfoOptions flags, CachedData cachedData)
at ReportSchedule.FireTimeScheduler.GetNewLocalNextFireTime(DateTime nextFireTime)
at ReportSchedule.FireTimeScheduler.Next()
at ReportSchedule.Service.ReportExecutionContext.ScheduleNextExecution()
at ReportSchedule.Service.ReportExecutionContext.Execute()

Anyway how to fix this?

 

[AlexanderReichert]

@YiannisH_3CX
I am still have this issue - any way to fix this - I am fine if there is a way to fix it directly on the server and delete this report at least