3CX PhoneSystem 01 Management Console not starting

leejor

Customer
Joined
Jan 22, 2008
Messages
16,665
Reaction score
1,656
I'm posting this in the event someone else happens runs into the same issue. I had not seen anything recently on the forum about this topic, but it can obviously still happen.

I updated my version of Windows 10 that 3CX is currently using to the Windows 10 IoT Enterprise LTSC 2021, as it is supported until 2032. The computer I'm using for 3CX does not support Windows 11, and no, it's not moving to anther machine, at least not for the time being

A clone of the hard-drive was made just in case, and, the upgrade to LTSC went fine, 3CX worked OK, no apparent issues at the time. This was a little over a month ago.

When I attempted to log into the management Console through the browser on the machine today, it timed out and said it could not connect. Multiple attempts on different browsers were made, with the same result. After checking the running services, It seemed the Management Console was not running.

I attempted to start the Management Console manually, and it was timing out each time.

3CX was running just fine in the background, calls worked. In Windows, the Management Console error said that the service did not respond in a timely manner. After doing some searches, I came across this post to the forum, from a few years ago...

See correct thread below.

I made the changes as suggested, in the Microsoft site, to the Windows Registry, to extend the wait time, for the service to start, and it now works.

It could be a combination of things like the operating system and recent 3CX updates, but in any event, it caused an issue on the machine i happened to be using.
 
Last edited:
Which changes?

im not sure you posted the correct thread, theres no mention of registry in this one
 
Silly me, that's what happens when you don't double check things. Must have had multiple tabs open and pasted the wrong one.

This is the link I meant to post..

 
Why don't you switch to a Debian install for the PBX?
 
  • Like
Reactions: bitn2
While I've "dabbled" with Linux on a few machines, from time to time, I'm more comfortable with Windows, which is the reason I originally gravitated to 3CX about 17 years ago.
 
  • Like
Reactions: Chris-MBN
3CX on Debian with the provided install ISO becomes mostly an "appliance", especially with auto-update enabled.
 
I find that if something goes wrong (isn't working quite the way it should), I'm much more comfortable taking the hood off A windows system, and getting my hands dirty, than I would be with a system running Linux. I do use it, but, for the most part on Raspberry Pi's, running "utilities", in the background. If something fails, I don't troubleshoot It, I simply do a restore from a backup I've made of the SD card.
 
  • Like
Reactions: Chris-MBN
I might be a bit biased as I'm now a long time linux administrator :), I used to be an Windows administrator several (10+) years ago. But since then, for me a server should only have a GUI if used as terminal server.

This said I would think as 3CX is now primarily developed targetting Debian, and Windows is only an second choice, getting updates later as testing is more complex.... Going with Debian is the more stable approach.

And as 3CX is also managing the OS updates for you you don't have to dig into the system.
To be honest non advanced users should not and don't need to change anything inside the Debian at all.

But in the end the OS choice depends on personal preferences. And as you are able to solve your problem. It shows you know your windows so it might the right decision for you. In the end if you feel more secure with windows it is the reasonable decision.

Even if I always prefer the debian system. Easy Updates, and 3CX development tested against it.
 

Latest Posts

Forum statistics

Threads
111,952
Messages
589,894
Members
164,844
Latest member
abctel2