Page 6-39
Programming
INTER-TEL
®
AXXESS
®
MANUAL VERSION 11.0 – May 2008
Common Errors
PROGRAMMING
6
D. COMMON ERRORS
6.32 The following table lists common error messages.
Table 6-5: Common Errors
Test Error
Hardware Address Hardware Address Ext _____ refers to an unrecognized board [0.0.0
Type 262]
A device has a hardware address of 0.0.0. DB Test will remove the
device and cleanup references to it.
Referential Integrity [Applications] / [transfer_recall_destination_device_id] contains a ref-
erence to a device of the wrong type [DevID
:1, Type 0]
[Stations] / [transfer_recall_destination_device_id] contains a refer-
ence to a device of the wrong type [DevID
:1, Type 0]
The Transfer Recall Destination field is not pointing to a valid device.
DB Test changes this field to point to the current device. This corrup-
tion is a known problem and is fixed in 5.2.
Boards The board in slot ____ has an incorrect number of records in [DSPs].
DB Test creates the necessary records.
Static Records [BoardsInformation] contains an invalid number of records [0 instead
of 16]
DB Test creates the necessary records. This corruption occurred in
early versions of 5.1.
Referential Integrity [Report...] / [report_id] contains an invalid reference to [Reports] /
[report_id][0]
DB Test removes these unneeded records. This was a corruption in
the default 5.1 database.
Referential Integrity [PrimaryRateBoards] / [board_id] contains a reference to a board of
the wrong type [BoardID
:___, Type:253]
DB Test removes this unnecessary record.
Static Records [MessagePrintFreezeOnStrings] contains an invalid number of
records [0 instead of 6]
DB Test creates the necessary records. This corruption occurred in
early versions of 5.2.
Devices Ext ____ has no records in [CallRoutingAnnouncements]
DB Test creates the necessary records.
Boards The board in slot ____ has no records in T1CallType
DB Test creates the necessary records. This corruption occurred in
early versions of 5.2.
Dynamic Enumera-
tions
[Keysets] / [attached_device_baud_rate_id] contains an invalid enu-
meration value [4]
This corruption will be fixed starting in production versions of 5.2.