Blackberry PROFESSIONAL SOFTWARE FOR MICROSOFT EXCHANGE Manual - Page 9
Browse online or download pdf Manual for Software Blackberry PROFESSIONAL SOFTWARE FOR MICROSOFT EXCHANGE. Blackberry PROFESSIONAL SOFTWARE FOR MICROSOFT EXCHANGE 23 pages. Version 4.1 sp4b
Also for Blackberry PROFESSIONAL SOFTWARE FOR MICROSOFT EXCHANGE: Getting Started Manual (49 pages), Release Note (11 pages)
Migration Guide
Troubleshooting the installation process
A third-party tool did not install successfully and the BlackBerry
Professional Software setup application closed
Possible solution
1.
In the BlackBerry® Professional Software installation media, double-click the Tools folder.
2.
Double-click the setup application file for the tool.
3.
Complete the instructions on the screen.
4.
Restart the BlackBerry Professional Software setup application.
Failed to write License key to the Database. Refer to the installation log
file for more information.
This message appears if you change the client access license (CAL) key for the BlackBerry® Enterprise Server - Small Business
Edition to the CAL key for the BlackBerry® Professional Software during the migration process. In addition, the BlackBerry
Professional Software does not install successfully.
Possible cause
By default, the setup application for the BlackBerry® Professional Software does not overwrite an existing CAL key during
the installation, migration, or upgrade process.
Possible solution
You must complete the installation using the existing CAL key for the BlackBerry® Enterprise Server - Small Business Edition.
After you complete the installation, you must change to the CAL key for the BlackBerry® Professional Software.
1.
On the server that hosts the BlackBerry Professional Software, on the taskbar, click Start > BlackBerry Manager.
2.
Click the Home tab.
3.
In the Account section, click License Management.
4.
Click Add License .
Previous version detected but no database available
This message might appear when you start the setup application. The setup application then closes.
Possible solution
Troubleshooting the installation process
3
7