Cannot Access Management Console

[MarkCSUK]

When trying to access the management console I get as far as the login prompt and then get SERVER ERROR.
The management console service is not running and will not start.
it gives ERROR 1604.

• 3CX Version, Professional Annual 16.0.6.655
• Server OS, Windows 10 build 1903
• Is the 3CX Server Hosted and where? no
• Has the Firewall Checker passed: YES

any help with this would be much appreciated.

 

[AWS2P]

go in windows services and force console service to start.
without any link related to your problem, you could try to push windows 2004 release

 

[MarkCSUK]

as stated in my original post, the console service will not start. It gives Windows Error 1604.

thanks for your reply.

 

[AWS2P]

try if not already done a windows reboot

 

[MarkCSUK]

thanks - tried many many many reboots.

 

[AWS2P]

is it a fresh pbx install or was it running since a while ?
PC is dedicated to 3CX ?
No antivirus ?

 

[MarkCSUK]

Hi,

been running a good long while, PC dedicated to 3CX and yes No AV.

 

[AWS2P]

since when did you got that problem? after an update ?

If i was you, i will do a complete PBX backup and keep it safe out of that pc, then update my windows to latest v2004, then remove actual pbx, reboot, reinstall from scracth with restore during install.

 

[MarkCSUK]

Thanks, but as we can't get into the management console it's difficult to backup it up.

 

[AWS2P]

you don't have any recent backup ?

 

[AWS2P]

in eventviewer do you have detailled explaination on why that service is not running?

 

[MarkCSUK]

Hi,

we have been working on this with 3CX Support (Charalambos) and this is now resolved.

 

[AWS2P]

Are you okay to share what you've done to fix it ?

 

[MarkCSUK]

sure,

we used the command line to take a partial backup (no fqdn, no license), we then uninstalled 3CX and unlinked the license from the FQDN (via customer portal). renamed c:\programdata\3CX to C:\programdata\OLD-3CX and rebooted the machine.

We then reinstalled 3CX recreated the 3cx.co.uk FQDN and linked to license (part of the install) - made sure all updates were applied, once everything was latest version we restored the partial backup.

bish bash bosh - all settings & extensions restored, everything working.

 

[AWS2P]

Thanks for sharing solution