I figured it out. I had not downloaded the new element manager. I was using an old version of element manager and it was not working correctly with new OS version. Thanks again for all of the help.
I may have mistated the revision issue. The info below is from the parc.txt file which I extracted from the system before it crashed. So the load build number and the bios version are different. Not sure which is relevant to me (if either).
Load Build Number: 40B201
MSC Card FW...
I have a follow up question if you guys would be so gracious as to indulge me again. I have received and installed my replacement drive and the system is up and running. I installed my keycodes and telephony is still working. However I am having trouble restoring my backups. When I browse to...
Thanks so much for all of the response. I have ordered a hard drive and it will be here tomorrow morning. I would still be open to a source for downloading an image though as I could fix tonight instead of tomorrow night.
I wanted to ask if I should be able to log in to the system from the...
We are in the US. We have a fast connection so we could potentially download. We should probably discuss outside of forum (not sure about rules for stuff like this). Is there a way I can contact you (should I used linkedin)?
Firebirdscrambler
Thanks much for the response. I had already looked at a couple of articles you referenced these had been very helpful. I was very pleased to see your article about recovering the license file from the logs. I had copied the logs down to my machine a few hours before the...
Hello - I am hoping to get some advice. I have a BCM 400 4.x and the hard drive has crashed. Phones still work but no VM or auto attendant. I cannot connect with Element manager or BCM monitor. I can get to the console (serial) but I get a "failed to authenticate" error when I try to login...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.