06-23-2011 06:16 AM
Description:error=0x0 error_address=0x2f300001 /error=0x0 error_address=0x2f300000
after rebooting the system ,the error disappear,bu for several days,the error shows again.
can you give some advices to solve this problem?
06-23-2011 06:58 AM
Thanks for the post !
May I ask what software version you are running....these types of messages were seen in v7 - a lot of corrections / enhancements were made in v8.0.2.
Note: Before upgrading ANY core infrastructure please read the Release Notes to ensure you are aware of the procedure, required keys and interopability with other devices.
06-24-2011 10:24 AM - edited 06-24-2011 10:26 AM
Exception Handler messages are caused by the software failing to perform a function when called upon. Almost anything can cause an Exception Handler message, because it is a catch-all for any software issue that is uncommon enough that it does not warrant it's own error message.
If there is some specific action or circumstances that trigger the messages, it can sometimes be possible to identify a particular build that might aleviate the issue. But even if it is not clear that a more recent release will address that issue, the first step should always be to upgrade to the most stable available build.
9.0.4 is the most current MGC release. And in the release notes of the 9.0.4 software, there is a resolved issue (VNGM-2270) with a problem description of:
MCU displays frequently the Exception Handler Message error, whether or not there is a running conference.
Every release of MGC software will include fixes for exception handler messages, whether or not they are documented, because it is such a generic message. But the first step for resolving those issues is always going to be to bring the bridge up to the latest stable build.
Of course, as Andrew pointed out, you always want to review the release notes ahead of time and ensure that you are aware of the changes implemented in that build.
Hope this helps.