| Never Connected |
The
user�s handheld has not initialized its connection with the Good Messaging Server
since being added to the Good Management Console. Please ensure the user has initialized
the OTA setup per their "Welcome to Good" email and that it is proceeding
without error. |
|
Disabled |
The
user has been disabled for this Service Type. Please check that the user is enabled
correctly at the Good Management Console. To do this launch the Good Management
Console and verfiy the user�s name appears in the Users list view. Please re-provision
the handheld in order to recover by adding the user to the Good Management Console
and running through the OTA setup again. |
|
Failed
| The
connection between handheld and the Good Messaging Server has failed due to an
error. Please re-provision the handheld in order to recover by either running
through the OTA setup again or Good debugger > reprov. Re-adding the user to
the Good Management Console may be necessary. |
| Client
Disconnected |
The
handheld has sent a disconnect message to the Good Messaging Server. If this handheld
has received a remote Erase Data command, it will disconnect itself from the Good
Messaging Server. Please re-provision the handheld in order to recover by re-adding
the user to the Good Management Console and running through the OTA setup again. |
| Admin
Disconnected | Under
rare circumstances, the Good Messaging Server user cache can get out of sync with
the user�s enabled state. This can happen when the IT Administrator has disabled
and re-enabled the user in the Good Management Console while the Good Messaging
Server is down (due to Services stopped, machine rebooting, network unavailability,
etc.). Please re-provision the handheld in order to recover by either running
through the OTA setup again or Good debugger > reprov. Re-adding the user to
the Good Management Console may be necessary. |
|
User
Not Enabled | The
Good Messaging Server is reporting a connection problem with Exchange for this
user�s profile. Please ensure the user�s mailbox is enabled and functioning
properly. Also verify that the user has been properly added to the Good Management
Console. |
|
Failed
to Recover | The
connection between handheld and the Good Messaging Server has failed to recover.
Please re-provision the handheld in order to recover by either running through
the OTA setup again or Good debugger > reprov. Re-adding the user to the Good
Management Console may be necessary. |
|
Not All Session
Connected | The Good Messaging Server failed to
start one or more of the service types for the user during startup. Please re-provision
the handheld in order to recover by either running through the OTA setup again
or Good debugger > reprov. Re-adding the user to the Good Management Console
may be necessary. |
|
Incorrect
Server | This is a rare case where the Good Messaging
Server has found an inconsistency in your Good Messaging Server name. Please re-provision
the handheld in order to recover by re-adding the user to the Good Management
Console and running through the OTA setup again. |
|
Service Not Enabled |
This
is a rare case where the particular service is not Good-enabled even though the
user is still Good-enabled. Please re-provision the handheld in order to
recover by either running through the OTA setup again or Good debugger > reprov.
Re-adding the user to the Good Management Console may be necessary. |
| Database
Corrupted | An
internal database is corrupted. When the user's handheld is set up again, Good
will re-initialize the database and correct the problem. |
