NEWS!!! -- BlackBerry Enterprise Server v5.0 Service Pack 3 for Microsoft Exchange

 BlackBerry Enterprise Server v5.0 Service Pack 3 for Microsoft Exchange
Please click on the links below to learn more about and download this software.
https://www.blackberryuniverse.com/site/view.aspx?filter=//ContentAlerts&filterID=&type=individual&contentid=f140bc3a-238a-42ac-b294-6fc4a95ed425&date=

See the release notes

Take a look before you install this upgrade

In certain circumstances, you cannot upgrade the BlackBerry® Configuration Database from 4.1 SP7 to 5.0 SP3.

The following errors appear in the database installer log file:

Release Notes SNMP known issues

63

[CBESDBInstaller::executeRetryDDL] SQL Error COM Error 0x80040E2F - IDispatch error #3119 - Source: "Microsoft

OLE DB Provider for SQL Server" - Description "Cannot insert the value NULL into column 'ServiceId', table

'DaveTest.dbo.BASServiceInstances'; column does not allow nulls. UPDATE fails." Native error = 515

[CBESDBInstaller::executeRetryDDL] SQL Error COM Error 0x80040E2F - IDispatch error #3119 - Source: "Microsoft

OLE DB Provider for SQL Server" - Description "The statement has been terminated." Native error = 3621 (DT

1113715)

During the upgrade process, if the MSI fails you might see the following error message when you try to run the

setup application again: "SQL query failed, see logs for more information". (DT 1094204)

Workaround:

1. In the registry, set the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Research In Motion\BlackBerry

Enterprise Server\Setup\Previous Version key to 5.0.0011.

2. Delete the ConfigAfterReboot and ConfigFirstRun keys from the registry.

3. Restart the setup application. At the Components Selection screen, uncheck MDS-IS.

If you upgrade from 5.0 SP1, software configurations that were set to Editable and Visible or Hidden are changed

to Read-only and Visible. (DT 1073979)

Workaround:

If you are upgrading an environment that includes many users who can log in to the BlackBerry Administration

Service using BlackBerry® Enterprise Server authentication, the setup application might appear to have stopped

responding in the

box. The setup application is applying additional migration steps to these user accounts which can take some time.

(DT 1045857)

If you are upgrading from BlackBerry Enterprise Server 5.0 SP1 or 5.0 SP2 using a different account than the account

you installed with, the upgrade process might not be able to complete. The setup application writes the following

message to the log file: "[CBESDBInstaller::executeRetryDDL] COM Error 0x80040E37 - IDispatch error #3127 -

Source: "Microsoft OLE DB Provider for SQL Server" - Description "Cannot drop the table 'ServerConnectionVTemp',

because it does not exist in the system catalog." Native error = 3701". (DT 1036048)

The upgrade process does not preserve the logging level that you set for the BlackBerry Attachment Service. (DT

1028329)

Reconfigure the software configurations after you complete the upgrade process.Installing the BlackBerry Enterprise Server files and required third-party applications dialog

Workaround:

When performing an in-place upgrade from BlackBerry Enterprise Server 4.0 SP7 to BlackBerry Enterprise Server

5.0 SP3, the installation process fails and displays the “%s installation has failed” error message when you click on

"Start services". (DT 1018750)

In the BlackBerry Administration Service, reset the logging level after the upgrade process completes.

Release Notes Upgrade process known issues

64

Workaround:

5.0 SP3. If you already upgraded BlackBerry Enterprise Server 4.0 SP7 to version 5.0 SP3, you must uninstall the

BlackBerry Enterprise Server software and reinstall BlackBerry Enterprise Server 5.0 SP3. After reinstalling, you

must reconfigure any custom settings that you created in BlackBerry Enterprise Server 4.0 SP7 for the BlackBerry

Attachment Service.

If you installed the BlackBerry Collaboration Service with BlackBerry Enterprise Server 5.0 SP2, when you upgrade

to BlackBerry Enterprise Server 5.0 SP3 and select Microsoft® Office Communications Server 2007 R2 or Microsoft®

Lync™ Server as the instant messaging server, the port numbers do not display the default values (5061 for TLS or

5060 for TCP, and 65061 for the listening port). (DT 1000050)

Upgrade BlackBerry Enterprise Server 4.0 SP7 in stages, first to version 5.0 SP1 and then to version

Workaround:

If you run a “Set no count on” SQL statement before you upgrade the BlackBerry Enterprise Server to 5.0 SP3, the

upgrade fails when the installation is finalizing and an “Error writing to Database” message is displayed. (DT 992357)

If you attempt to upgrade the BlackBerry Enterprise Server from 4.1.x and the default size of the BlackBerry

Monitoring Service database (BMSStore) is set to a value larger than 100 MB, the setup application cannot create

the BlackBerry Monitoring Service database and the upgrade process fails. (DT 990052)

You must type the port numbers to specify the instant messaging settings.

Workaround:

than 100 MB or you can manually create the BlackBerry Monitoring Service database.

In some circumstances, the IBM® Lotus® Sametime® server name is not automatically prepopulated when

upgrading to BlackBerry Enterprise Server 5.0 SP3. (DT 984685)

You can change the default size of the BlackBerry Monitoring Service database to a value smaller

Workaround:

When upgrading from BlackBerry Enterprise Server 4.1 SP7 to 5.0 SP3, if you switch the authentication type from

SQL to Windows® authentication, the following error message is incorrectly displayed: "The Database

<database_name> does not currently exist. Would you like to create it?" (DT 978308)

Manually enter the Lotus Sametime server name.

Workaround:

the installation process.

The BlackBerry Enterprise Server now stores passwords that the BlackBerry MDS Connection Service uses to

connect to external servers in protected format in the BlackBerry Configuration Database. This change means that

when you upgrade to BlackBerry Enterprise Server 5.0 SP3, the proxy credentials for the BlackBerry MDS

Connection Service and BlackBerry Collaboration Service are lost. (DT 890282)

The setup application is confirming that you want to upgrade the database. Click Next to continue

Workaround:

upgrade process completes, restore the proxy settings.

Write down the proxy settings before you upgrade the BlackBerry Enterprise Server. After the

Release Notes Upgrade process known issues

65

When you upgrade the BlackBerry Enterprise Server, if you change the pool name for the BlackBerry Administration

Service, the setup application should prompt you to log in to the computers in the BlackBerry Domain that host

the BlackBerry Administration Service and synchronize the local property files and registry entries with the

BlackBerry Configuration Database. (DT 853637)

Workaround:

1. On each computer in the BlackBerry Domain that hosts the BlackBerry Administration Service or BlackBerry

Monitoring Service, open the BlackBerry Configuration Panel.

2. Click the

3. Click

In some circumstances, if you upgrade to the latest JRE™, and then upgrade to the BlackBerry Enterprise Server

5.0 SP2, an earlier version of JRE is installed with the BlackBerry Enterprise Server software. (DT 769397)

If the BlackBerry Enterprise Server includes evaluation license keys and enterprise license keys, and you upgrade

to version 5.0 SP2 or SP3, the setup application does not prompt you to fix this issue before starting the upgrade

process. (DT 743460)

When you upgrade the BlackBerry Enterprise Server, the setup application does not upgrade the Microsoft® SQL

Server® Native Client. (DT 732061)

Administration Service - High Availability tab.Synchronize.

Workaround:

BlackBerry Enterprise Server 5.0.

If you upgrade from BlackBerry Enterprise Server 5.0 SP1, and you are upgrading the only BlackBerry Administration

Service instance in the BlackBerry Domain, the setup application permits you to remove the BlackBerry

Administration Service. This can leave your organization without a running BlackBerry Administration Service. (DT

637461)

If a BlackBerry Administration Service upgrade failed because of insufficient disk space and you reinstall it, the

setup application completes successfully, but the value of the "JVM® Option Number 8" registry key is blank. (DT

622976)

Manually install the latest version of the Microsoft SQL Server Native Client when upgrading from

Workaround:

1. Click

2. Type

3. Navigate to \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BAS-AS\Parameters.

4. Change the value of

Djboss.partition.name=RIM_BES_BAS_HA_########_BLACKBERRYNEW

5. Restart the BlackBerry Administration Service.

Add the registry key manually.Start > Run.regedit.JVM Option Number 8 to -.

Release Notes Upgrade process known issues

66

After you upgrade remote components from version 5.0 SP1, the BlackBerry Administration Service displays

incorrect version information for BlackBerry Controller instances installed with remote components. (DT 617030)

When you upgrade the BlackBerry Enterprise Server from 4.1 SP7, the setup application prompts you for the SRP

ID and SRP authentication key. (DT 614767)

Workaround:

the log file.

When you upgrade to BlackBerry Enterprise Server 5.0 SP3, the setup application does not preserve the logging

level that you configure for the ASRV and ACNV log files in the BlackBerry Configuration Panel. (DT 600379)

Type the SRP information and continue with the upgrade process. Duplicate errors might appear in

Workaround:

If during an upgrade process from BlackBerry Enterprise Server 5.0 SP1 you remove the local BlackBerry Attachment

Service, and later reinstall the local BlackBerry Attachment Service but configure the BlackBerry Enterprise Server

to use a remote BlackBerry Attachment Service, users cannot view attachments on devices. (DT 578530)

Use the BlackBerry Administration Service to configure the logging levels.

Workaround:

When you upgrade the BlackBerry Enterprise Server without installing the BlackBerry database notification system,

the dbo.GetHostName stored procedure is also installed in the BlackBerry Configuration Database, though it is not

required. (DT 560408)

If you upgrade the BlackBerry Enterprise Server from version 5.0 and you give the account full permissions on the

BlackBerry Configuration Database and only denydatawriter permissions on the BlackBerry Monitoring Service

database, the setup application does not respond. (DT 506639)

Start the local BlackBerry Attachment Service.

Workaround:

again.

After you upgrade the BlackBerry Enterprise Server, the version numbers of the BlackBerry Enterprise Server

components are not updated in the BlackBerry Administration Service until you start the BlackBerry Enterprise

Server components. (DT 491613)

Close the setup application, correct the permissions on the account, and run the setup application

Workaround:

After you upgrade a BlackBerry Domain from version 4.1, the BlackBerry Administration Service may display one

or more BlackBerry MDS Connection Service instances that do not exist. (DT 490746)

Start all of the BlackBerry Enterprise Server components.

Workaround:

instances that do not exist, if possible. Removing them by using the BlackBerry Administration Service is not always

possible because the BlackBerry Administration Service may request that the software be removed first and this

is not possible since the software does not exist.

Use the BlackBerry Administration Service to remove the BlackBerry MDS Connection Service

Release Notes Upgrade process known issues

67

During an upgrade, if you configure the BlackBerry Enterprise Server to use Microsoft® Office Communicator 2007

in the

Communications Server 2005 (Office Communicator) in the

If you uninstall BlackBerry Enterprise Server 4.1 or later and install BlackBerry Enterprise Server 5.0 or later on the

same computer, the setup application finds software and registry keys for BlackBerry Enterprise Server 4.1 when

it performs the BlackBerry Policy Service configuration validations and does not allow the upgrade process to

proceed. (DT 427051)

Instant messaging settings dialog box, the setup application displays the incorrect Microsoft® Office LiveSummary dialog box. (DT 427065)

Workaround:

If you upgrade a remote BlackBerry Monitoring Service from version 5.0, the URL of the BlackBerry® Web Desktop

Manager in the last dialog box of the setup application contains the NetBIOS name instead of the FQDN. (DT

296369)
Reinstall BlackBerry Enterprise Server 4.1 SP6 and then upgrade to BlackBerry Enterprise Server 5.0.

-Dario

Upgrade process known issues