Mar 31 2020 01:08 AM
Mar 31 2020 01:08 AM
In a Skype for Business Server 2019 environment, I see this error on the Front-End servers
Log Name: Lync Server
Source: LS Conferencing Announcement Service
Date: 31-03-2020 14:07:43
Event ID: 33126
Task Category: LS Conferencing Announcement Service
An unhandled exception was encountered in Conferencing Announcement Service.
Exception: System.ArgumentOutOfRangeException: Time-out interval must be less than 2^32-2.
Parameter name: dueTm
at System.Threading.Timer..ctor(TimerCallback callback, Object state, TimeSpan dueTime, TimeSpan period)
at Microsoft.LiveServer.Cas.CasService.OnTerminationCountdownStatusChangedQueued(Object sender, TerminationCountdownStatusChangedEventArgs eventArgs)
at Microsoft.Ucas.App.Common.EngineThread.Execute(WorkItem work)
Cause: Internal error in Conferencing Announcement Service.
Restart the service. If the problem persists contact product support.
Users don't report any issues, but has anyone seen this error and know what it means?
Apr 24 2020 08:47 AM
May 11 2020 08:32 AM
May 11 2020 08:46 AM
No but we are using Anywhere365. I guess that it has to do with the way those products work. They setup a conference for joining agent and caller. In this process they do a certain action which triggers the event. The issue only happens on a Skype for Business 2019 environment and not on 2015.
We have a confirmation of Anywhere365 that there is no user impact but nevertheless this makes a lot of clutter in the event log.
So seems to be a specific "bug" on SfB2019 ?!
May 11 2020 09:25 AM
Competella do the same, setup a conference for queue handling
But your are right, this is only a problem in SfB 2019...
May 15 2020 08:31 PM
Same issue here.
Just applied March 2020 CU.
Using Enghouse Interactive. It uses conferences for call control. Alot of these alerts.
Dec 04 2020 05:31 AM
Same Issue on our environment. We have implemented Luware Callcenter.
Jan 25 2021 07:11 AM
We also use Anywhere 365 in combination with Skype for Business in our company.
After updating to Skype 2019, we also notice this error in the log.
Is there already a solution for the unsightly behavior?
Jan 25 2021 08:05 AM
@Marco1187 the issue is still there. I think we have customers on the last SfB CU with A365 but still experience the explosion in events. We currently filter out the eventid in question.
Jan 25 2021 10:57 PM - edited Jan 25 2021 11:50 PM
Thanks for your answer.
I have already worked on this issue a year ago with Microsoft premier support.
According to microsoft support the fix should be available in CU 4. Unfortunately this does not seem to be the case. I will contact Microsoft again. Maybe now we have a little more attention, because some others have the same problem.
Jan 25 2021 11:49 PM - edited Jan 25 2021 11:52 PM
Hi, i received the following answer from microsoft support:
"Hello, Good morning! At the moment we receive feedback from many users with this problem. At the moment there is an IcM opened and the production group is aware of this issue. At the moment there is an IcM opened and the production group is aware of this issue"
Let's wait and see when they bring out a hotfix.