Help Center

Local Navigation

Error messages: BlackBerry Load Test Configuration Tool

Calendar validation failure
This message appears when, after the BlackBerry® Load Test Configuration Tool converts the user account, the BlackBerry Configuration Database value in the Calendar enabled field is not typed correctly.
Device capabilities validation failure for PIN
This message appears when the value of the Device Capabilities field selected in the BlackBerry Load Test Configuration Tool does not match the corresponding value stored in the BlackBerry Configuration Database.
DeviceType validation failure
This message appears when the Device Type field in the BlackBerry Configuration Database is not specified correctly.
DispatcherHostInstance not found
This message appears when the BlackBerry Load Test Configuration Tool cannot find an instance of the BlackBerry Dispatcher service on the computer that the BlackBerry Load Test Configuration Tool is installed on.
Email address contains an invalid character
This message appears when an email address that is provided in the file that contains the user account list contains a character that is not valid.
Encryption key validation failure
This message appears when the encryption key that the BlackBerry Load Test Configuration Tool uses is different from the encryption key that is stored in the BlackBerry Configuration Database.
ERROR: Additional Device Capabilities field length invalid: <length>
This message appears when the length of the record field in the BlackBerry Configuration Database entry does not correspond with the length that was specified. The BlackBerry device capabilities were not specified correctly.
ERROR: Device Capabilities length invalid: <length>
This message appears when the length of the record field in the BlackBerry Load Test Configuration Tool entry does not correspond with the length that was specified, for a reason other than an incorrect definition of the capabilities that the user can specify.
ERROR: Dispatcher or ConfigServerName registry entries missing.
This message appears when the registry on the computer is missing the values that describe the BlackBerry Dispatcher and the BlackBerry® Enterprise Server.
ERROR: Failed to parse!!
This message appears when the BlackBerry Enterprise Server does not specify any capabilities for a user account.
ERROR: Not implemented
This message appears when the BlackBerry Load Test Configuration Tool tries to activate a user account, but the type of messaging server is not specified for the user account.
ERROR: PIN is not available
This message appears when the PIN that is associated with the user account that the BlackBerry Load Test Configuration Tool is trying to convert is already reserved by another user account.
ERROR: User <email_address> has pending delete status
This message appears when the user account is still pending deletion on the BlackBerry Enterprise Server when the BlackBerry Load Test Configuration Tool tries to convert or update the user account.
Error parsing <user_account_list_entry>
This message appears when the BlackBerry Load Test Configuration Tool cannot parse an entry in the user accounts list. This error message is usually preceded by a descriptive error message of the issue.
EXPECTED: email@server.com, F1xxxxxx
This message occurs when the format of the user account file is not correct. The error messages shows the correct format for entry for the user account list, and is also stored in the log.
Failed to connect to socket: <socket_name>
This message appears when the BlackBerry Load Test Configuration Tool cannot connect to a socket when the BlackBerry Load Test Configuration Tool tries to start a web service.
MailStoreName not updated <PIN>
This message appears in a test environment with BlackBerry® Enterprise Server for IBM® Lotus® Domino® when the BlackBerry Load Test Configuration Tool tries to verify user accounts, but the field MailStoreDisplayName is not current in the BlackBerry Configuration Database. The BlackBerry Load Test Configuration Tool adds user accounts to the BlackBerry Enterprise Server for IBM Lotus Domino in chunks of 200 user accounts, with a delay between each chunk. After each delay, the BlackBerry Load Test Configuration Tool updates the information in the MailStoreDisplayName field of the BlackBerry Configuration Database. If the process of adding user accounts takes longer than the delay programmed into the BlackBerry Load Test Configuration Tool, the BlackBerry Load Test Configuration Tool displays this message.
MailStoreType was not found
This message appears when the BlackBerry Configuration Database does not specify the type of messaging server.
One or more of the failed user accounts are pending for deletion or could not be reimported. Writing user accounts to email-to-pin map file
This message appears in a test environment with BlackBerry® Enterprise Server for IBM® Lotus® Domino® when you cancel the delay of the BlackBerry Load Test Configuration Tool and you are converting user accounts again. The BlackBerry Load Test Configuration Tool writes to a file a list of the user accounts that it did not convert.
OTAFM validation failure
This message appears when the OTAFM enabled field in the BlackBerry Configuration Database is not typed correctly.
Specified email address is invalid
This message appears when an email address in the file that contains the user account list has a format that is not valid.
Specified PIN is invalid
This message appears when a PIN in the user account list is not eight characters long.
The remove name could not be resolved
This message appears when the name of the BlackBerry Administration Service is different from the name that you specified.
The specified user import file not found
This message appears when the file that contains the user account list does not exist on the computer that the BlackBerry Load Test Configuration Tool is installed on.
Timeout waiting for pending user updates...
This message appears when the BlackBerry Load Test Configuration Tool waits more than 300 seconds for the BlackBerry Enterprise Server to complete pending changes.
Unable to determine BES Dispatcher instance. Try specifying -bdn <server> option from the command line
This message appears when the BlackBerry Load Test Configuration Tool is setting up a web service and cannot retrieve the name of the BlackBerry Dispatcher instance in the registry or the command line.
User <user_name> could not be deleted
This message appears when the BlackBerry Load Test Configuration Tool cannot delete a user account. When the BlackBerry Load Test Configuration Tool converts user accounts again, the user accounts are deleted from the BlackBerry Enterprise Server and then are added to the BlackBerry Enterprise Server.

User <user_name> could not be disabled
This message appears when the BlackBerry Administration Service could not deactivate a user account.
User '<user_name>' already exists. Updates are not supported in Domino. The user must be deleted in BAS/BBManager before importing...
This message appears when you left the user account named <user_name> on that particular BlackBerry Enterprise Server for IBM Lotus Domino. For this environment, you must delete the user accounts from the BlackBerry Enterprise Server before running the BlackBerry Load Test Configuration Tool.
User '<user_name>' is disabled in BAS. (BASID: <BAS_user_ID> UserConfigID: <user_config_ID>) The user must be enabled or deleted in BAS/BBManager before importing...
This message appears when a user account exists on the BlackBerry Enterprise Server for IBM Lotus Domino but is not associated with it.
User '<user_name>' was not found in BAS. (BASID: <BAS_user_ID> UserConfigID: <user_config_ID>)
This message appears when a user account does not exist in the BlackBerry Administration Service.
UserDeleteStatus validation failure
This message appears when the BlackBerry Enterprise Server for IBM Lotus Domino has scheduled a converted user account for deletion during the conversion validation process.
Validation Failed.. <user_name>, <PIN>
This message appears when the BlackBerry Load Test Configuration Tool cannot validate a user account that was just converted.

Was this information helpful? Send us your comments.