An unhandled exception was encountered in Conferencing Announcement Service.

%3CLINGO-SUB%20id%3D%22lingo-sub-1267041%22%20slang%3D%22en-US%22%3EAn%20unhandled%20exception%20was%20encountered%20in%20Conferencing%20Announcement%20Service.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1267041%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20a%20Skype%20for%20Business%20Server%202019%20environment%2C%20I%20see%20this%20error%20on%20the%20Front-End%20servers%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3ELog%20Name%3A%20Lync%20Server%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ESource%3A%20LS%20Conferencing%20Announcement%20Service%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EDate%3A%2031-03-2020%2014%3A07%3A43%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EEvent%20ID%3A%2033126%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ETask%20Category%3A%20LS%20Conferencing%20Announcement%20Service%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ELevel%3A%20Error%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EKeywords%3A%20Classic%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EUser%3A%20N%2FA%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EComputer%3A%20sfb01.contoso.local%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EDescription%3A%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EAn%20unhandled%20exception%20was%20encountered%20in%20Conferencing%20Announcement%20Service.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EException%3A%20System.ArgumentOutOfRangeException%3A%20Time-out%20interval%20must%20be%20less%20than%202%5E32-2.%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EParameter%20name%3A%20dueTm%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3Eat%20System.Threading.Timer..ctor(TimerCallback%20callback%2C%20Object%20state%2C%20TimeSpan%20dueTime%2C%20TimeSpan%20period)%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3Eat%20Microsoft.LiveServer.Cas.CasService.OnTerminationCountdownStatusChangedQueued(Object%20sender%2C%20TerminationCountdownStatusChangedEventArgs%20eventArgs)%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3Eat%20Microsoft.Ucas.App.Common.QueuedEventHandler%601.Execute()%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3Eat%20Microsoft.Ucas.App.Common.EngineThread.Execute(WorkItem%20work)%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ECause%3A%20Internal%20error%20in%20Conferencing%20Announcement%20Service.%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EResolution%3A%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ERestart%20the%20service.%20If%20the%20problem%20persists%20contact%20product%20support.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsers%20don't%20report%20any%20issues%2C%20but%20has%20anyone%20seen%20this%20error%20and%20know%20what%20it%20means%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1267041%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESkype%20for%20Business%20Server%202019%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1335999%22%20slang%3D%22en-US%22%3ERe%3A%20An%20unhandled%20exception%20was%20encountered%20in%20Conferencing%20Announcement%20Service.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1335999%22%20slang%3D%22en-US%22%3Esame%20error%20here.%3CBR%20%2F%3ESFB%202019%20on%20Win2019.%3CBR%20%2F%3Epls%20post%20solution%20if%20you%20find%20it%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1359540%22%20slang%3D%22en-US%22%3ERe%3A%20An%20unhandled%20exception%20was%20encountered%20in%20Conferencing%20Announcement%20Service.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1359540%22%20slang%3D%22en-US%22%3ESame%20here%2C%20also%20no%20knowledge%20of%20user%20impact.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1380136%22%20slang%3D%22en-US%22%3ERe%3A%20An%20unhandled%20exception%20was%20encountered%20in%20Conferencing%20Announcement%20Service.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1380136%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22tlid-translation%20translation%22%3E%3CSPAN%20class%3D%22%22%3EI%20have%20found%20this%20error%20shows%20when%20you%20call%20a%20Competella%20AgentService%20queue%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F7158%22%20target%3D%22_blank%22%3E%40Mike%20Shivtorov%3C%2FA%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F326159%22%20target%3D%22_blank%22%3E%40domienxylos%3C%2FA%3E%3C%2FP%3E%3CP%3EDo%20you%20use%20Competella%20in%20your%20environment%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1380183%22%20slang%3D%22en-US%22%3ERe%3A%20An%20unhandled%20exception%20was%20encountered%20in%20Conferencing%20Announcement%20Service.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1380183%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9116%22%20target%3D%22_blank%22%3E%40Claus-Ole%20Olsen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20but%20we%20are%20using%20Anywhere365.%20I%20guess%20that%20it%20has%20to%20do%20with%20the%20way%20those%20products%20work.%20They%20setup%20a%20conference%20for%20joining%20agent%20and%20caller.%20In%20this%20process%20they%20do%20a%20certain%20action%20which%20triggers%20the%20event.%20The%20issue%20only%20happens%20on%20a%20Skype%20for%20Business%202019%20environment%20and%20not%20on%202015.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20confirmation%20of%20Anywhere365%20that%20there%20is%20no%20user%20impact%20but%20nevertheless%20this%20makes%20a%20lot%20of%20clutter%20in%20the%20event%20log.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20seems%20to%20be%20a%20specific%20%22bug%22%20on%20SfB2019%20%3F!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1380312%22%20slang%3D%22en-US%22%3ERe%3A%20An%20unhandled%20exception%20was%20encountered%20in%20Conferencing%20Announcement%20Service.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1380312%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F326159%22%20target%3D%22_blank%22%3E%40domienxylos%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECompetella%20do%20the%20same%2C%20setup%20a%20conference%20for%20queue%20handling%3C%2FP%3E%3CP%3EBut%20your%20are%20right%2C%20this%20is%20only%20a%20problem%20in%20SfB%202019...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1394647%22%20slang%3D%22en-US%22%3ERe%3A%20An%20unhandled%20exception%20was%20encountered%20in%20Conferencing%20Announcement%20Service.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1394647%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20issue%20here.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20applied%20March%202020%20CU.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsing%20Enghouse%20Interactive.%20It%20uses%20conferences%20for%20call%20control.%20Alot%20of%20these%20alerts.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1956081%22%20slang%3D%22en-US%22%3ERe%3A%20An%20unhandled%20exception%20was%20encountered%20in%20Conferencing%20Announcement%20Service.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1956081%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20Issue%20on%20our%20environment.%20We%20have%20implemented%20Luware%20Callcenter.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

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
Level: Error
Keywords: Classic
User: N/A
Computer: sfb01.contoso.local
Description:
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.QueuedEventHandler`1.Execute()
at Microsoft.Ucas.App.Common.EngineThread.Execute(WorkItem work)
Cause: Internal error in Conferencing Announcement Service.
Resolution:
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?

 

7 Replies
same error here.
SFB 2019 on Win2019.
pls post solution if you find it
Same here, also no knowledge of user impact.

I have found this error shows when you call a Competella AgentService queue

@Mike Shivtorov
@domienxylos

Do you use Competella in your environment?

@Claus-Ole Olsen 

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 ?!

 

@domienxylos 

 

Competella do the same, setup a conference for queue handling

But your are right, this is only a problem in SfB 2019...

 

Same issue here. 

 

Just applied March 2020 CU. 

 

Using Enghouse Interactive. It uses conferences for call control. Alot of these alerts. 

Same Issue on our environment. We have implemented Luware Callcenter.