Local Windows Server Shutting Down

[RichardJF7]

We are running 3cx 16 0 1078 on a local Windows Dell server with 2016 Standard installed.

On Monday the server has started shutting down every 2 hours, below is the last windows log entry the last time it fell over.
Ive been working on it since yesterday trying to understand what is going on.

What do you think this is? if I reinstall 3cx from a backup, will I just reinstall the problem?
Can I stop the server from shutting down on this error?

Any help would really be appreciated.

Thanks
Richard


The description for Event ID 0 from source PostgreSQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

FATAL: terminating connection due to administrator command

 

[NickD_3CX]

Hi!

I'm not sure I've seen a 3CX software causing a Windows Server to reboot, but judging from the error, something does seem to be wrong with the Windows installation if I had to guess.

From your description, I understand the although every 2 hours the server restarts, in between those 2 hours, the PBX works.
If this is the case, clearly Postgres is installed, otherwise it wouldn't work at all.

What I would suggest? Taking a backup, downloading it off that server, format everything and re-deploy again.

Note that if for some reason the Postgres Database is indeed corrupted, it may be a good idea to used a backup from before this problem started, because any corruptions in the DB most likely will pass onto any new backup made, which in turn will go onto the new 3CX installation you restore it on.

 

[Alphabetic]

You need to go through the system and application logs in more depth and take another look instead of filtering by critical or error. Windows shutdown/reboot events will occur as information. You will find the cause of the shutdown/reboot logged in there somewhere. Even if the server is BSOD, this will be logged in the system logs.

Have you checked scheduled tasks too?

Are you running any RMM software? is this the cause?