Troubleshoot Zimbra Mobile Connector for BlackBerry Installation Failures: Difference between revisions
No edit summary |
mNo edit summary |
||
Line 42: | Line 42: | ||
{{Article Footer|n/a|03/10/2010}} | {{Article Footer|n/a|03/10/2010}} | ||
Latest revision as of 02:38, 4 February 2022
- This is archive documentation, which means it is not supported or valid for recent versions of Zimbra Collaboration.
Troubleshoot Zimbra Mobile Connector for BlackBerry Installation Failures
Troubleshoot Zimbra Mobile Connector for BlackBerry Installation Failures Homepage
Please See Troubleshoot_Zimbra_Mobile_Connector_for_BlackBerry_Installation_Failures
Introduction
The most common installation problems are due to the deviation from the step by step installation instructions outlined by the ZimbraBESConnector PDF Guide or from deviation from the installation prerequisites.
References:
- Has our official documentation on Zimbra Connector for BlackBerry Enterprise Server
- For the older ZCS Connector for BlackBerry Guide
Resolution Steps
- First, please verify that the installation process is started with none of the prerequisite software installed and that all user applications are closed before starting the installation process for ZCB. Then verify that the steps are followed in the order they are given.
- If there are still problems with the installation, the installer can be run in verbose mode to generate debug logs. These logs can be sent to Zimbra support for analysis. To run the installer in verbose mode, run the following command in the folder where the installer file (this has an .msi extension) is located.
- To run the installer in verbose mode, run the following command in the folder where the installer file (this has an .msi extension) is located.
msiexec /i [msi-filename] /lv''' [output log file path name]
- For example, the following command will launch the zcb_beta3.msi installer in verbose mode, and will output the verbose logs to out.txt in the current directory.
msiexec /i zcb_beta3.msi /lv out.txt
- To run the installer in verbose mode, run the following command in the folder where the installer file (this has an .msi extension) is located.