MENTUM PLANET 5.7.

0 PATCH 10 - RELEASE NOTICE

Release Date:
June 20, 2014

Release Type:
Patch (General Distribution)

Description:
This patch fixes several important issues that were reported against Mentum Planet 5.7.0 and
introduces Automatic Cell Planning (ACP) tool performance improvements.

Software:
This patch consists of 2 executable files:
o Mentum Planet 5.7.0 Patch.exe
o Data Manager Server 5.7 Patch.exe
The patch files can be downloaded from the web download pages in the Customer Support
section of the InfoVista website (http://support-
mentum.infovista.com/index.php?page=customer-care&hl=en_US). Please contact InfoVista
Customer Support to obtain an access password, if required.

Enhancements/changes:
Automatic Cell Planning (ACP) tool performance improvements.
Case 41812 The software has been modified so that there is no longer a requirement for an
inbound communication port to be open on the client side when running Data Manager
Console. [Included in Patch 8]
When viewing the prediction for a given sector you can now view the PDSCH signal. If the sector
uses beamforming then you may select the antenna pattern to be used. In doing so, you may
specify a particular azimuth, select a point on the map or use the interference pattern created
through Monte Carlo simulations. [Included in Patch 1]

Issue Resolutions:
Case 57761 Issue whereby an error message displayed when attempting to apply optimization
changes for antenna azimuth.
Case 40692 Issue whereby Automatic Cell Planning (ACP) results were expectantly different
when run based on the same settings.
Case 40984 Issue whereby the Data Manager Administration Console incorrectly showed
clients being logged in multiple times.
Case 56853 Issue whereby the message Violation of PRIMARY KEY constraint <KeyID>. Cannot
insert duplicate key in object <ObjectID. Displayed when attempting to change project
permissions in the Data Manager Administration Console.
Case 58424 Issue whereby the defined default color profile was not applied to the PDSCH
C/(N+I) network analysis layer. [Included in Patch 9]


Case 56852 Issue whereby the action of emptying a project from the Data Manager
Administration Console failed with an error message. The problem occurred in cases where a
project was being checked in at the same time a project folder was being emptied. [Included in
Patch 8]
Case 57546 Issue whereby the message The following error has occurred while checking in
the data: Cannot find DataManager Project with given Uid displayed when attempting to
submit a project to Data Manager. [Included in Patch 8]
Case 58397 Issue whereby the message Cannot get EV file for antenna file
<AntennaFileName>. Import failed displayed when attempting to import data with IECON.
[Included in Patch 8]
Case 41827 Issue whereby users that were not part of the root domain did not appear in the
Data Manager Console. To work around this limitation, set the "UseAlternateGetUsersMethod"
parameter in datamanagerconsole.exe.config to "True". [Included in Patch 8]
Case 56851 Issue whereby the Data Manager Console was slow to connect. [Included in Patch
8]
Case 56499 Issue whereby the message Error: An exception occurred during the ACP engine
optimization: Internal error (exception) displayed during an ACP run. [Included in Patch 8]
Case 56812 Issue whereby the message Index was outside the bounds of the array displayed
when attempting to perform model tuning. The issue only affected the P3M propagation model.
[Included in Patch 8]
Cases 56060 and 57301 Issue whereby EV-DO layers were not included in the default network
analysis layer list. [Included in Patch 8]
Case 57547 Issue whereby the message MapInfo Professional application file has stopped
working displayed when attempting to use the Compare to Modeled Prediction function in
Survey Manager. [Included in Patch 8]
Case 42286 Issue whereby results produced by the PN Offset Planning Tool were incorrect in
some cases. [Included in Patch 8]
Cases 55949, 43409, 57363, 55617, 56679 Issue whereby the action of connecting to a Data
Manager Server project was very slow. This patch introduces changes aimed at reducing the
time it takes to connect however, in some cases, it still may take several minutes before the
process completes. The amount of time required to connect depends, in part, on the size of the
project and whether it already exists in memory. By default, projects are held in memory for 2
hours after a project is accessed. This duration can be increased by adjusting the Close Project
After Inactive value in the Data Manager Server Console Options dialog (Tools>Options).
[Included in Patch 7]
Case 55761 Issue whereby the message The following error has occurred while submitting
data: Object reference not set to an instance of an object displayed when attempting to submit
data to Data Manager. [Included in Patch 6]
Case 56465 Issue whereby the message Check in files to server failed. Access to the path
<PathName> is denied displayed when attempting to submit data to Data Manager. The
problem occurred randomly in cases where the number of files being checked in was large.
[Included in Patch 6]
Case 56850 Issue whereby the Data Manager Server could not be started. The problem
occurred as a result of database constraints not being properly enabled following database
migration. [Included in Patch 6]


Cases 57271, 57229, 57226, 57284 Issue whereby the message The following error has
occurred while checking in data: Check in files to server failed. Error saving local file
<FilePathName> to server location <ServerFilePathName>.[Included in Patch 6]
Case 55611 Issue whereby the messages "Error: Equipment type: "LTE FDD-UE_1" of
subscriber type "Subscriber LTE-FDD" does not support the mobile speed associated with usage
"Data" and/or Object reference not set to an instance of an object displayed while attempting
to run Monte Carlo analysis. [Included in Patch 6]
Case 43021, 41862 Issue whereby the message The following error has occurred while
retrieving project item statuses: Object reference not set to an instance of an object displayed
while attempting to connect to Data Manager. [Included in Patch 6]
Case 42094 Issue whereby the 32-bit version of the Radio Propagation Engine (RPE) Server and
Agent did not correctly determine the number of available CPU processors. [Included in Patch 6]
Case 42281 Issue whereby some color profile files were not correctly migrated. [Included in
Patch 6]
Case 40868 Issue whereby the message Object reference not set to an instance of an object
displayed when attempting to view the configuration changes associated with an optimization
scenario. [Included in Patch 6]
Case 42223 Issue whereby the message Object reference not set to an instance of an object
displays when attempting Monte Carlo simulation. The problem occurs in the calculation of the
maximum HSUPA data rate, in cases where there is only 1 serving sector for a given subscriber.
[Included in Patch 5]
Case 41838, 42324 Issue whereby Monte Carlo simulation failed with one or all of the
messages Disk cache error, Error: Unable to read beyond the end of the stream or Error:
Object not set to an instance of an object. The problem occurred under various scheduler
options when the size of the simulation was very large. [Included in Patch 5]
Case 42107 Issue whereby the message Index was outside the bounds of the array displayed
when attempting to generate GSM network analysis layers. The issue occurred in cases where
more than 32,767 sectors were included in the network analysis. [Included in Patch 5]
Case 42016 Issue whereby the message ExecuteScalar requires an open and available
connection. The connections current state is closed displayed when attempting Data Manager
migration. [Included in Patch 4]
Case 41642 Issue whereby Automatic Cell Planning (ACP) fails with the message The number
of WaitHandles must be less than or equal to 64. [Included in Patch 2]
Case 41153 Issue whereby the message Project \ OptimizationContraintsManager could not
be locked: Locked by <UserName> displayed when attempting to lock a site in Data Manager.
[Included in Patch 2]
Case 41633 Issue whereby ASPT discarded the configuration of the selected Candidates Sites
and applied the same Site Template as the one defined for placing new Sites. The issue occurred
when ASPT was used in Expansion Mode (ASPT Advanced) with some Candidates Sites.
[Included in Patch 2]
Case 41793 Issue whereby the Radio Propagation Engine (RPE) failed to use all available
processor threads and eventually caused the application to lock up. [Included in Patch 2]
Case 39457 Issue whereby random artifacts were observed under certain conditions when
predictions were generated based on the Predict 4 propagation model. [Included in Patch 1]
Case 40690 Issue whereby an antenna with multiple electrical patterns displayed only one
electrical pattern after being saved. [Included in Patch 1]


Case 41108 Issue whereby the message "Unable to cast object of type 'VirtualBandData' to
type 'PhysicalBandData' displayed when attempting to run an antenna query. [Included in
Patch 1]
Case 41116 Issue whereby Sectors column data was missing on the Antennas tab in a project
data export spreadsheet (and in Tabular Editor). [Included in Patch 1]
Case 39946 Issue whereby the message Spectrum Range <ID> has non-sequential carriers
displayed when attempting to migrate a project. [Included in Patch 1]
Case 41014 Issue whereby the message Invalid view layer displayed when a project was
being opened. The problem occurred in cases where one or more grid file names were very long
and the translucency setting in User Preferences was enabled. [Included in Patch 1]
Case 41027 Issue whereby Fraction of incident power scattering values entered in the
propagation model editor were not retained (e.g. they reverted to the original value). This issue
impacted the Predict 4 and Air Predict propagation models only. [Included in Patch 1]
Case 40919 Issue whereby Monte Carlo simulation erroneously showed some subscribers as
being not served for reason downlink resources. [Included in Patch 1]
Case 39398 Issue whereby signal strength values shown in a table produced through Fixed
Subscribers Analysis were incorrect. The problem occurred when using the Planet 3D (P3M)
propagation model. [Included in Patch 1]
Case 53534 Issue whereby the message Object reference not set to an instance of an object
displayed when attempting to connect to Data Manager. [Included in Patch 1]
Case 53119 Issue whereby prediction results were inaccurate when generated based on the
Berg antenna algorithm. The problem occurred in cases where the boresight direction was
anything other than True north. [Included in Patch 1]
Cases 41209, 41482, 41210 Issue whereby Areas created based on complex polygons (e.g.
polygons containing holes, polygons consisting of multiple objects etc) were not created
properly. [Included in Patch 1]
Issue whereby mean error values shown in the model tuning report always displayed as positive
values. [Included in Patch 1]

Installation:
Important: Install the Data Manager patch prior to installing the Mentum Planet client patch.
Stop Data Manager Service (for Data Manager patch only).
Double-click on the installation files and follow the steps in the installation Wizard.
Re-boot your computer after installation.

Compatibility:
This patch was built specifically for Mentum Planet 5.7.0. The patch was not tested on any other
versions. Customers using previous versions of Mentum Planet must upgrade to Mentum Planet
5.7.0 prior to applying this patch.

Notes:
n/a