Mitel MiVoice Business Troubleshooting Manual page 178

Troubleshooting Guide
SYMPTOM
Errors show that data has been
distributed to a network element
in a way that is not consistent with
the data in the Remote Directory
Number form.
Errors show that login status for a
hot desk user has been
improperly shared between the
user's primary and secondary
ICP.
There are many SDS Data
distribution errors occurring on
the department/location forms.
Performing a Form Comparison
results in conflicts for
department/location.
A change to the department field
is not distribute throughout the
network or cluster.
When adding a new element to a
migrated network, you receive
either of the following error
messages after you initiate the
Start Sharing operation:
"Synchronization failed. You must
migrate this node to the new data
model before attempting to join
the SDS network"
"Synchronization failed. The
target for this operation must
migrate to the new model first".
Start Sharing operation fails in a
mixed release network and the
node initiating the sync is an older
release than the slave node.
Distribution error caused by
associating two users to the same
phone service (which is not
allowed) from MiCollab persists
after problem corrected.
170
Table 55: Troubleshooting Sharing Operations
POSSIBLE CAUSE
An administrator made an
incorrect entry to the Remote
Directory Number form at an
element somewhere in the
network and the change has
been propagated by SDS.
A failover occurred between the
time the user logged in from one
device and then another. For
example, an external hot desk
user logs in from their cell phone,
there's a failover, and before a
failback can occur, they log into
from their office desk phone.
In a heavily congested clustered
hospitality deployment, if there
are a many hospitality
operations being performed at
the same time (either via PMS or
GSA or a combination of both),
then there is the possibility that
department/location operations
may result in distribution errors.
You attempted to add a
non-migrated element to the
GDM network.
Releases may have database
schema differences that result in
some data not being accepted
on some nodes.
Failed to perform Sync operation
after problem corrected.
CORRECTIVE ACTION
Delete the inconsistent record from the
Remote Directory Number form, and
reprogram it appropriately.
Perform a sync operation from the local
element to the remote peer.
Perform an SDS synchronization of the
department/location forms. This will
update all users that reference the
department/location fields with the new
department/location strings.
Follow the procedure described in
"Adding an Element to the Migrated
Network" in the System Administration
Tool online help.
Retry operation by initiate Start Sharing
from node running newer release.
Perform an SDS synchronization of the
User and Services Configuration form to
MiCollab.
Page 5 of 5