Known issues

This section lists known issues for the BlackBerry® Administration API 5.0 SP3 release with the BlackBerry® Enterprise Server 5.0 SP3 release.

Your application might not be able to establish a connection to the BlackBerry Administration API. Your application might receive the following error message: "Could not create SSL/TLS secure channel". (DT187943)

Workaround: Your application should retry the API request.

If your application does not specify a WLAN configuration ID or a VPN configuration ID when using the assignWlanConfigurationToUser() or assignVPNConfigurationToUser() methods, your application might receive the following error message: "Runtime exception". (DT281006)

Workaround: None

If an application uses an unauthorized administrator account to invoke the addUser() method with an existing group, your application might receive the following error message: "GROUP_NOT_FOUND". (DT281103)

Workaround: None

If your application uses the setActivationPassword() or findResolvedUserCapabilities() methods with a user ID equal to 0, your application might receive the following error message: "Runtime exception". (DT281373)

Workaround: None

If your application uses the findITPoliciesForUser(), findSoftwareConfigurationsForUser(), disableBlackBerryServiceForUser(), or clearEmailUserStats() methods with a user ID equal to -1, your application might receive the following error message: "Runtime exception". (DT281435)

Workaround: Use a valid user ID

If you use the BlackBerry Administration Service to add a prefix to the file names of the log files for BlackBerry Enterprise Server components, the BlackBerry Administration API log file might not have the specified prefix. (DT357380)

Workaround: None

If your application uses the moveUser() method with the failOutstandingJobs property set to false, your application might receive the following error message: "Runtime exception". (DT440427)

Workaround: None

If your application sends a request that contains an embedded control character (for example, 0x7 (BEL)), your application might receive the following error message: "Invalid Character Exception". (DT492472)

Workaround: Remove the embedded control characters from the argument.

Next topic: Related resources
Previous topic: New in this release

Was this information helpful? Send us your comments.