Solved Things going downhill since 16.0.6.641 Update

[myrich22]

Hello,
I have a separate thread regarding just recordings ( Recording Issue ). However, I now realize that since the recent updates ( version 16.0.6.641 on/around 8/25) , much more has gone haywire than I realized:
1) recordings (as previously mentioned)
2) scheduled backups not running (Yikes!) (manual backup can be done thankfully)
3) reports (from reports menu) not running, gets "initialized" but never runs.
4) Call Log doesn't have anything since update
I've rebooted several times.
Has anyone had anything remotely similar since the update?
Note - I'm running a stand alone 3cx server, windows 10, running in azure. Has been working great for months until now.
Ideas?
Rich

 

[AWS2P]

all my pbxs are updated .641 but none have one of the symptoms you listed.
Have seen posts with windows pbxs hosted in Azure having problems , so may be, common part is Azure .

 

[JohnS_3CX]

Hi Rich,

The specific machine is facing possible permissions issues and we will have to learn why.

This can be enough to bring down a whole system. I replied to your PM earlier, please take a look.

 

[myrich22]

Believe it or not, we had some bad/old records that were gumming up the works. I'm back in action now.
Thanks,
Rich

 

[NZTGInfrastructure]

Hi myrich22, any chance you could share what the bad/old records you cleaned out were?
I am experiencing what I suspect is the same issue as you did.

 

[myrich22]

Hi NZTGInfrastructure,
Incredibly, they were bad/old scheduled webmeetings from several months ago. Unclear where they came from. The error turned out to be the result of a few duplicate records in the 3cx database itself. It took support to fix it. I don't think I would attempt it myself (well maybe I might with backup in hand)...
Rich

 

[JohnS_3CX]

@NZTGInfrastructure

Set your logs to verbose and restart the system service.

Search the 3CXSystemService.log for any exception

If you find anything like this from the timestamp of the service restart onwards, you will need to contact support. If it is an older error and no longer appears it might not apply.

|Excpt|System.ArgumentException: An item with the same key has already been added.