- 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.
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...
For reasons to long to list here I restored my Windows 10 Pro 64 Bit system to a previous version dated 12/3/18 using Acronis True Image Premium 2018. I use No-IP service for a fixed IP address and it's up and running smoothly with the correct IP address. The restore process seemed to go fine with the following exceptions:
1) I could not access any of my profiles because none of the passwords seemed to work. This was a relatively easy fix using Lazesoft Recovery Software.
2) I did have to rejoin the domain with a new profile as the terminal reported that my security credentials...
- Titleguru
- Replies: 6
- Forum: Phone System / PBX
See correct thread below.For reasons to long to list here I restored my Windows 10 Pro 64 Bit system to a previous version dated 12/3/18 using Acronis True Image Premium 2018. I use No-IP service for a fixed IP address and it's up and running smoothly with the correct IP address. The restore process seemed to go fine with the following exceptions:
1) I could not access any of my profiles because none of the passwords seemed to work. This was a relatively easy fix using Lazesoft Recovery Software.
2) I did have to rejoin the domain with a new profile as the terminal reported that my security credentials...
1) I could not access any of my profiles because none of the passwords seemed to work. This was a relatively easy fix using Lazesoft Recovery Software.
2) I did have to rejoin the domain with a new profile as the terminal reported that my security credentials...
- Titleguru
- Replies: 6
- Forum: Phone System / PBX
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: