We had a little glitch with a customer this week. They called in initially to say their voicemail wasn't working, but then decided the whole system had stopped.
After guiding the customer through some diagnostics the engineer went to site. The cpu (V9.122 CPS) was resetting and not coming back online.
Then engineer was given a backup the customer had done a few days before. He defaulted the CPU and attempted to upload the database. The upload failed. He put the database through the database test and repair tool and tried again. The database would still not upload.
Eventually he upgraded the database to put it onto a bigger CPU he had in the vehicle and got the customer going, even though the system was now unlicensed and would reset every four hours.
On return the original database was tried in a spare CPU and would not upload there either. We eventually opened the database offline. That worked fine. We saved it again under another filename and attempted to upload it to the original CPU. That worked. The CPU went back to site and was put into the customers system.
So the moral is, the database test and repair tool may not correct all errors. Opening the database offline and then using the database save option is what got it fixed.
Less of these Axxess out in the field now, but still, you may be happy to find this post one day!
John Rogers
Telecom Care Ltd
