Blackberry VERSION: 10.1.2 manual Fixed issues, Installation fixed issues

Release Notes Fixed issues

Fixed issues 2

Installation fixed issues

The setup application stopped responding when it mishandled a failed SQL call. (DT 7531615)

If you attempted to install the BlackBerry Enterprise Service 10 software on a computer that had previously had the software installed on it, the install might have failed. (DT 7531574)

If you installed BlackBerry Enterprise Service 10 on a computer and stopped the Core components, then started to install a secondary instance on another computer and restarted the core components on the primary instance after the "The setup application could not connect..." message appeared, the setup application would not complete on the secondary instance. (DT 7439711)

If the domain name that you specified for the BlackBerry Administration Service pool name began with a number, the installation process continued but might not complete. (DT 7284702)

When you ran the setup application, you could not specify an IP address for the BlackBerry Administration Service pool name. (DT 7199525)

If you re-ran the setup application on a computer, the Communication component certificate was deleted. (DT 7199217)

If you changed the core password using the BES10 Configuration Tool, when you uninstalled the BlackBerry Enterprise Service 10 and then reinstalled it and used the new core password, the installation would not complete. (DT 7177306)

When you installed the BlackBerry Enterprise Service 10 core components on a computer that hosted the BlackBerry Enterprise Service 10 administration consoles, the installation process might not have completed. (DT 7170786)

When you installed a secondary Core Module, the password fields in the Core Module information dialog were enabled, even though you should not create a different password for a secondary Core Module. (DT 7111259)

In some circumstances, if you configured additional port bindings in Microsoft IIS, the BlackBerry Enterprise Service 10 setup application would incorrectly populate the port fields in the Core Module information dialog box. (DT 7092542)

The setup application stopped responding if the Organization name contained special characters such as a plus sign (+), equals sign (=), hash (#), backslash (\) and semi-colon (;). (DT 6839542)

5