If you have a backup card, or if it's an R7, back it up, default it, set the time and date, and restore it. See if it works properly after that.
If it doesn't, default it, (you've already backed it up, but the back up is corrupted), set the time and date, and some minimal programming, see if it works properly. If ir does, resore it again, so that you can document the programming. Then default it and program from scratch.
the problem was not found reset the system for the third time and it cleard i was able to set the date and time It was odd the first two atempts to reset didn't work think you all for your input
With multiple manufacturers over the years I have found that sometimes resets, or defaulting the system features do not always clear everything from memory every time. I discovered this in Toshiba, ESI, Multitech, Avaya, Tadiran, and a few others in both system, and VM default procedures. About ten years ago I began doing all default procedures 4 to 6 times, and you know what, in some of the tier 2, or higher support guys I know they have confirmed that sometimes doing a default multiple times will clear data that doing it just once sometimes does not do.
It does not take that much time to do it a few times, and it seems to help, especially when having issues of an unexplained nature, default, default, default, default, default, default, reprogram. I have bought a number of "so called" bad systems and revived them in this fashion.
In case you do not know this every newly, refurbishedly, usedly installed system should be defaulted prior to programming including VM systems if you do not want issues down the road. It is possible your system was not ever defaulted prior to you doing it.
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.