Chat now with support
Chat with Support

Unified Communications Analytics 8.6 - Release Notes

Resolved issues

Currently, when a customer upgrades or uninstalls, UC Analytics has a backup process for the configuration files for the Data Engine, Query Engine and Storage Engine. Now UC Analytics also creates a backup for the Configuration folder, which contains the DeploymentConfiguration.txt and ProductAdministrators.txt files.


Previously, UC Analytics did not verify the storage path during initial installation. When a path was entered with two or more consecutive back slashes, and the customer later tried to upgrade, the installer logged an error. Now the initial storage path is verified during installation, and the installer will tolerate extra slashes during an upgrade.


The Bulk Data Exporter would fail with the error "Operation not supported: Unsupported query property" if a user tried to export LinkPair fields. The /ShowDataModel output incorrectly included the non-exportable LinkPair fields which are used in filters only. LinkPair fields are no longer included in the /ShowDataModel output. Error reporting has been improved. Key fields are now included in the /ShowDataModel output.


During upgrade, an error occurred if the original service account that was used to install UC Analytics had been removed from the local Admins group. The error occurred even if the service account for the UC Analytics services has been changed in Windows. Now, during upgrade, if a mismatch is detected between the Data Engine service account and the service account in the UC Analytics configuration file, you are prompted to update the service account.

A new button is also added to the Deployment Manager (Manage Deployment | Change Service Account) that lets you update the service account in Windows for UC Analytics services and in the UC Analytics configuration database when necessary.


The Data Engine service would stop automatically after starting when an upgrade was completed. In some data sources, the fieldSets property did not exist or was null which resulted in an exception occurring in the Data Engine service and the service being stopped.


Instrumentation was added to the Data Engine query management component to collect performance statistics for insights, exports, subscriptions, and for fine-tuning and troubleshooting long query times in Microsoft Power BI OData endpoint queries.


When you generated a .csv file using the Bulk Data Exporter, the .csv file used incorrect escape characters for data that contained double quotation marks or commas, which meant the .csv file could not be used with Microsoft Excel or Microsoft PowerBI Desktop.


Previously, if the database backup script failed or was interrupted, it would leave behind the temporary Cassandra snapshot and the partial backup. The backup script now keeps track of the temporary Cassandra snapshots and the backups being created. The information is stored in a State.CSV file in the same folder as the backup script.

If the script fails or is interrupted (for example, computer reboot by Windows Update), during the next run, the backup script will clean up temporary Cassandra snapshots and any partial backups from the previous run. To indicate that a backup is a partial backup, a marker file ►Partial Backup◄.TXT is created in the backup while the backup is being created. When the backup is complete, the marker file is deleted.


A warning message that referred to a "Runtime Error" would occur in the Exchange Public Folders collection job if a public folder identity contained a specific type of double quotation marks, specifically the double low-9 quotation marks '„' (U+201E).


When a parent folder and its subfolders were hard deleted in a mailbox, the checkpoints of the subfolders were not removed from the UC Analytics database This caused detailed log warnings ("ServiceResponseException: The folder to be synchronized could not be found.") each time UC Analytics attempted to gather data since the last run. Now the checkpoints of the removed subfolders are also removed from the database when the sync folder is not found, and UC Analytics will not log warnings.


A lot of ports were used when UC Analytics was collecting Exchange Mailbox Contents Summary and Exchange Mailbox Contents data. UC Analytics creates many connections when collecting target mailboxes and the Exchange Web Services (EWS) KeepAlive property default value was true, which resulted in many sockets being left in the Time Wait state. Now the default setting for on-premises data collection is set to false but the default value for online data collection is true.


When running the Exchange Configuration data collection using an account that had the required permissions, the customer received an error:

Now, when collecting mobile device statistics for mailboxes that have an invalid subfolder name, the data source collection skips these mailboxes and logs a warning message instead of an error


When the Exchange (Online) Mailbox Contents data collection job was run, and items were removed or items were added to a mailbox since the previous job run, the following error could be logged in the Data Engine service logs: "Failed to sync item in folder....NullReferenceException: Object reference not set to an instance of an object." This occurred if the property ItemChange.Item was null because the mail item was deleted or the IsRead property was changed.


The Data Query Availability job would run for more than two days for large deployments. This issue was mainly caused by the Exchange Mailbox Contents and the Exchange Online Mailbox Contents collection jobs having too small a data insertion value which resulted in a very high number of small segments to be written to shards in the Storage Engine (Cassandra database). The data sources’ EWS batch size is now configurable (checkpointInsertionSize) to allow for larger data insertion values to support large data collections.


In the Exchange (and Exchange Online) Mailbox Contents data collection, when the job processed a mailbox that had a folder name which contained characters that are invalid in XML, the following exception was logged in the Data Engine service logs:

The collection job would fail to save or update the checkpoint for the specified mailbox. In this case, the mailbox was gathered as an initial collection each time the job ran.


When the Exchange Configuration data source job was run, the job status messages reported both skipped mailboxes and skipped users that were not mail-enabled as being skipped mailboxes. Now the status messages clearly distinguish between skipped mailboxes and skipped users (not mail-enabled).


The Exchange IIS Logs data collection would log an error, "StartIndex cannot be less than zero", on IIS logs that had activity for users with a UPN (user principal name) in Active Directory that did not contain an '@' symbol.


When a mailbox was being moved from one server to another due to server maintenance, the Exchange (Online) Mailbox Contents collection would log an error, “The mailbox database is temporarily unavailable”. However, the process would continue to try to collect folders or messages from the problematic mailbox. Now the collection skips the “missing” mailbox, shows warnings in the data source logs, and continues to the next mailbox.


Data Query Availability job tried to merge a corrupted shard repeatedly for one day. The Data Query Availability job got stuck when it tried to merge a data shard and the shard contained a corrupted segment. As a result, the remaining shards were never merged and data from those shards never appeared in the insights. The job now merges data shards in rounds. A single merge attempt on each shard is made (no retries) in each round. This way, all shards receive a merge attempt in a round. Shards that fail to merge for some reason are retried in next round. Up to four rounds are performed per run of the Data Query Availability job.


A customer had one daily subscription that would run twice, 30 minutes apart, in one day. UC Analytics uses a checkpoint to determine whether a subscription has run. Subscriptions are scheduled to run on the hour or half hour. However, the checkpoint was slightly ahead of the hour or half hour, causing the subscription to run twice. Now the checkpoint is stored exactly on the hour or half hour.


The Mailboxes - Activity Summary insight had poor performance when exporting or sending a subscription for the insight. Significant performance improvements have been made for the following insights: Mailboxes - Activity Summary, Mailboxes / Mailbox Activity / Summary, Mail Activity / Internal vs. External, and Mailboxes / Sizes and Quotas / Mailbox Quotas.


Domains that were classified as internal in the Domain Classifications configuration page were incorrectly displayed in the Internet / Top Internet Domains insight in the Outbound Domains by Message and the Outbound Domains by Volume views. The internal domains were also incorrectly shown in the Internet / Top Internet Domains Users insight in the Sent Messages Details view. The issue could occur when an outbound message was sent to both internal recipients and external recipients.


In your User Profile, in the Date, Time, and Numbers settings, if you removed the . (period) specified as the Decimal Separator and saved the change to your profile, all your exports and subscriptions would be broken. The message "Error: An error occurred while executing the request" would be displayed and the subscription or export would fail.


Certain insights, such as Email - Details, contained the default field Recipients which caused performance issues when the insight was displayed. Recipients includes direct recipients and, if a group is a direct recipient, expands the group to include all the indirect recipients. To improve the time that it takes for the insight to display, the following insights now show Direct Recipients by default:

If you want to modify an insight to see all recipients, you can customize the insight and add the Recipients field (Recipients | Email Address | Display Name) to the insight.


In Skype for Business / Lync insights, some users were incorrectly shown as Enabled for Federation even when they were not enabled. UC Analytics determined the EnabledForFederation attribute value using the Get-CsUser cmdlet, but the value from Get-CsUser was sometimes incorrect. Now UC Analytics determines if a user is Enabled for Federation using both the Get-CsUser and Get-CsExternalAccessPolicy cmdlets to provide the correct information.


When the customer exported an insight such as Legacy Public Folders - Inventory, and the insight contained a tabular view with a metric column (such as # of Nested Subfolders) and a customized column (such as Replicas Creation Date) that included multiple DateTime objects, the export would fail with the error message “Internal error occurred during the query request execution” in the exported file.


The Company Home Page or an individual home page would hang if the page contained an insight that had been removed by one user but had been saved by another user using a different browser instance.


Several insights have a default date range of 28 days which can cause the initial display of the insight to have a long loading time. The default date range for these insights has been changed to 7 days to improve the initial insight display time. Once the insight is displayed, you can modify the date range to show whatever number of days you want.


Platforms - Activity

Platforms - Activity Chargeback

Platforms - User Adoption

Groups - Empty Mail-Enabled Groups Inventory

Groups - Inventory

Groups - Summary

Mail-Enabled Groups - Inventory

Mail-Enabled Groups - Membership

Mail-Enabled Groups - Summary

Office 365 Users - Exchange Online Inactive

Users - Recent Changes

Users - Summary

ActiveSync - Server Activity

ActiveSync - User Activity

DLP Matches - Activity

DLP Matches - Details

Email - Activity

Email - Bi-Directional Activity

Email - Chargeback

Email - External Activity

Email - File Attachment Activity

Email - Response Time

Email - Size Distribution

Email - System Activity

Exchange - Adoption

Exchange - Inactive Users

Exchange - Inventory

Exchange - Summary

Groups - Inactive

Groups - Usage

Legacy Public Folder Replicas - Trend

Legacy Public Folders - Inactive

Mail Contacts - Inactive

Mail Contacts - Usage

Mailboxes - Activity Summary

Mailboxes - Chargeback

Mailboxes - Inactive

Mailboxes - Inventory

Mailboxes - Summary

Mailboxes - Trend

Mobile Devices - Inactive

Mobile Devices - Summary

Outlook on the Web (OWA) - Activity

Outlook on the Web (OWA) vs. ActiveSync Unique Usage

Personal Archive Mailboxes - Inventory

Personal Archive Mailboxes - Summary

Public Folders - Inactive

Public Folders - Migration Trend

Public Folders - Trend

Skype for Business / Lync - Chargeback

Skype for Business / Lync - Feature Adoption

Skype for Business / Lync - Inactive Users

Skype for Business / Lync - Skype for Business Client Adoption

Skype for Business / Lync - User Adoption

Skype for Business / Lync Conferences - Activity

Skype for Business / Lync Conferences - Server Usage

Skype for Business / Lync Enterprise Voice - Activity

Skype for Business / Lync Enterprise Voice - Chargeback

Skype for Business / Lync Enterprise Voice - Server Usage

Skype for Business / Lync Peer-to-Peer Sessions - Activity

Skype for Business / Lync Peer-to-Peer Sessions - External Domain Activity

Skype for Business / Lync Peer-to-Peer Sessions - Server Usage

Skype for Business / Lync QoE - Devices

Skype for Business / Lync QoE - Location

Skype for Business / Lync QoE - Network

Skype for Business / Lync QoE - Summary

Cisco - Activity

Cisco - Chargeback

Cisco - Inactive Users

Cisco - Summary

Cisco Conferences - Activity

Cisco Conferences - Server Usage

Cisco Peer-to-Peer Sessions - Activity

Cisco Peer-to-Peer Sessions - External Activity

Cisco Peer-to-Peer Sessions - Server Usage

Cisco Top External Numbers Dialed

Distribution Groups / Group Access

Distribution Groups / Inactive Groups / By Distribution Group

Distribution Groups / Top Group Users

Exchange ActiveSync / Devices / Active Devices

Exchange ActiveSync / Devices / Inactive Devices

Exchange ActiveSync / Servers / Server Activity

Exchange ActiveSync / Servers / Server Sync Times

Exchange ActiveSync / Users / Email Activity / Attachments

Exchange ActiveSync / Users / Email Activity / Departmental Summary

Exchange ActiveSync / Users / Email Activity / Summary

Exchange ActiveSync / Users / Top Email Senders and Receivers

Inventory / Inactive Mailboxes

Mailboxes / Mailbox Activity / Daily

Skype for Business / Lync / Instant Messages / Instant Message Usage

Skype for Business / Lync / Instant Messages / Top Internal Senders And Receivers By Messages

Skype for Business / Lync / Organizational Summaries / Top Usage by User

Known issues

It is not recommended that you use the built-in domain Administrator account for installing or for accessing UC Analytics. If you have a child domain in your environment, or if you have two root level domains, you will be unable to install the product.


After installing the Storage Engine on a separate computer with multiple network cards, the customer is unable to access the web site (“Application failed to start.”) and nothing seems to work. In this case, an incorrect IP address may have been registered for the Storage Engine.

NOTE: If you are installing multiple Storage Engines on a separate computers that have multiple network cards, the installation may not complete.


On servers that have more than one IPv4 address, the UC Analytics installer selects one of the IPv4 addresses and registers that as the IP address for the UC Analytics component on that computer. The selected IP address may not be the IP address you want for the UC Analytics Storage Engine.


Disable the network cards that have undesired IP addresses, run the UC Analytics installer for the Storage Engine, and re-enable the disabled network cards. If you need to disable a network card that is used for Remote Desktop access to the server, you must install UC Analytics using the physical console instead of Remote Desktop.


Typically, when you uninstall the product, the Storage directory is removed. If the specified directory cannot be removed (for example, if the directory is on a network drive) an error message appears. You can work around the error by clicking “Ignore”. You can manually remove the directory after the uninstallation process is complete.


In the Autorun.exe, the Download buttons for the software prerequisites may appear to be not working. An error is displayed about a script error on the page.


On some computers, an iexplore.exe process lingers for about 30 seconds after Internet Explorer is closed. Until the iexplore.exe process exits, the Javascript call for the Download buttons fails to launch a new Internet Explorer window.


Launch the Task Manager and wait until the iexplore.exe process has exited. The Download buttons work correctly.


In a deployment with multiple Data Engine collector roles installed, if you modify your deployment configuration properties using the Deployment Manager, and you clear the Data Engine configuration and reset it, an issue can occur in which the Primary Data Collector cannot be identified. The following error is displayed “You must have one collector role for the Data Engine designated as the primary collector.”


In the Deployment Manager, select Manage Deployment | Modify Deployment.
Click Edit Deployment and click Data Engine Advanced.
Select the Primary Data Collector check box for the server that hosts collector that should be the primary collector.


If an Office 365 account is added as a product administrator in the Deployment Manager, the account is not granted full access to the Admin Settings.


In the UC Analytics web site, in Admin Settings | Security, add the Office 365 user account under the Access to Tenant Configuration heading to grant full access to Admin Settings. You must have already added an Office 365 target environment.


When setting security access to insight data in the Admin Settings | Security page, if you add an Active Directory (AD) user in email address format when the user does not have an associated mailbox, the security access is not set. For example, if you granted unrestricted access to that user, the user would see the error "You do not have the required access rights to view the insight” when attempting to view an insight such as the Mailboxes - Inactive insight.


You can add the user and grant data access if you enter the user SAM account name.


In the Classifications | Threshold Classification page, you can set thresholds for Skype for Business and Lync QoE quality metrics. The page has the recommended thresholds set for Skype for Business 2015 and Lync 2013 by default. Most of these thresholds also apply to Lync 2010.

However, if you add a threshold classification that is specific to Lync 2010 only, and you have a mixed environment, the threshold will also be applied to Lync 2013 and Skype for Business 2015 even though the threshold may not be applicable to those versions.


On the Admin Settings - Data Collection page, under Data Sources, you cannot remove data sources if you are viewing the page using iPad or other mobile platforms.


In the Exchange Online (hybrid and native) data source collections, if the same PowerShell credentials are used for more than one data source, there can be overlapping Azure AD plug-in credential incompatibility. You might notice authentication errors with Azure AD PowerShell cmdlets such as the following:

Though UC Analytics recovers from these errors, it is recommended that each Exchange Online data source be configured with its own set of PowerShell credentials.


Previously, UC Analytics might collect incorrect data for mobile devices if a mailbox display name contained a / (forward slash) or a \ (backslash). For example, if there were two mailboxes, /AB and AB, and if mobile device #1 connected to mailbox /AB, and mobile device #2 connected to mailbox AB, UC Analytics would incorrectly match both mobile devices #1 and #2 to mailbox AB. This issue existed only for mailboxes that were migrated from on-premise Exchange to Exchange Online. Though this issue was corrected in version 8.4.2, incorrect mobile device data that was collected previously and stored in the database is not changed. All new collected data will be correct.


UC Analytics does not distinguish between discovery mailboxes and system mailboxes. Discovery mailboxes are collected and recorded as system mailboxes. In insights, there is no indication that a mailbox is a discovery mailbox. You cannot filter on discovery mailboxes.


There can be partial ActiveSync data on the day that a user first starts using a mobile device. For example, ActiveSync activity is shown but not associated with a user in the Exchange ActiveSync / Users / Email Activity / Summary insight. This situation occurred when a user started using an ActiveSync device for the first time after the Exchange Configuration collection had successfully run for that day. ActiveSync activity for subsequent days will be correctly associated with the user.


If you have configured the Exchange Configuration data source for a resource forest implementation, if you later add an LDAP connection for more account forests, the data collection does not automatically run to update the data. You must wait until the next day’s data collection run to see the new information from the account forest.


In a hybrid environment (Exchange Online and Exchange on-premise), Azure AD Connect (formerly Azure AD Sync) synchronizes on-premises users with Office 365 cloud services for single identities. If the synchronization process is stopped, UC Analytics can double-count users. When the Azure AD Connect synchronization resumes, all new data collections will show the correct user count.


In the Exchange DLP Matches - Details insight, the text in the Justification for Override (insertable) column will appear incomplete if the justification text that was entered by the user contained a semicolon (:) or a single instance of single (‘) or double (“) quotation marks.



The Exchange IIS Logs data collection cannot associate ActiveSync events to a user for some ActiveSync clients with users that have spaces in their Windows logon name (such as MYDOMAIN\N Wong). This issue affects ActiveSync events from the ActiveSync client in Windows Mail. It does not affect the ActiveSync clients in iOS or in Android.


When collecting Exchange data from an Exchange resource forest deployment, there are certain limitations when an active (master) user account has more than one Exchange mailbox, or has more than one archive mailbox, in more than one forest.

The master account of the linked mailboxes and of the linked archive mailboxes is correctly recorded. However, only one of the mailboxes that belong to the master account will be reported as its mailbox. Similarly, only one archive mailbox that belongs to the master account will be reported as its archive mailbox.


For any back-end ActiveSync events that have an Exchange server as the authenticated user, the Exchange IIS data collector cannot associate the event to a device and user. The ActiveSync events are gathered but are shown in the insights without a device or a user.


To collect data for personal archive mailboxes (using the Exchange Configuration, Exchange Online Hybrid Mailbox Configuration, or Exchange Online Native Configuration data sources), you select the following two options:

If you do not select both options for the same data source collection, the Storage Limit Status column is not populated in the Personal Archive Mailboxes - Inventory and Personal Archive Mailboxes - Summary insights.


In the Exchange Online data sources, during target expansion, batch size configuration is implemented to improve gathering performance. To ensure that the complete membership of dynamic distribution groups is collected, the batch size values set in the Data Engine collector configuration cannot be less than 1000, and must be greater than or equal to 1000.

The batch size settings for the Exchange Online data source configuration are located in the UC.Analytics.Insights.DataEngine.DataCollector.dll.config file, on the computer that hosts the Data Engine (Collector):

Do not change these values except under guidance from Quest Support. If you reduce these values to a number less than 1000, some members of the target dynamic distribution groups will not be included in the Exchange Online data collections.


When entering an organizational unit (OU) when configuring certain data sources, if the user enters an OU in the correct format but with an invalid value, the data collection jobs do not issue a warning or error but resolve 0 targets for the invalid OU. Data will be missing from the insights. Data sources in which you can specify an OU as a target are as follows:


When you export an insight that shows a date range for the displayed data at the top of the insight, the date range time zone does not appear in the exported file.


In Exchange 2010, if the Microsoft OWA light version is used, the Outlook on the Web (OWA) insights will display the browser as "Unknown” for Internet Explorer 11, Edge, FireFox, Chrome, and Opera. The issue does not exist in other versions of Exchange or if Safari is the browser.


If the time zone offset is negative (such as -5), and you apply smoothing to a graph, and the beginning of your date range is before the date when data collection initially started, the total for the smoothed graph is less than the total for the unsmoothed graph.


Ensure that the date range does not include the days before data was collected.


In the Mobile Device insights, the Device IMEI column shows <none> for iOS devices. UC Analytics uses the cmdlet Get-MobileDeviceStatistics (for Exchange 2013/2016/2019) and Get-ActiveSyncDeviceStatistics (for Exchange 2010) to get the device IMEI. Due to how the iOS device built-in mail app works, the information is not stored in the internal mobile device logs and is not available to PowerShell, and by extension, to UC Analytics.


In the insight view, If the date range is set to a single day, any trend graph will change to a vertical bar chart but if you export the same insight, the trend graph does not display a bar chart but displays a trend line with a single point.


On the home page, you cannot enlarge or shrink the insight tiles on iPad and other mobile platforms.


After installing Quest UC Analytics and attempting to open the Analytics web site (http://<server>/Analytics), the user sees the following error: “The application failed to initialize.”

This issue may be caused by a bug in IIS 7.0 in handling extensionless URLs. See the following link for details:

Install the Microsoft patch to fix this issue.


If the Date format that is set in your UC Analytics user profile is in a different order than the Date and time format that is set in regional settings on your local computer, and you export an insight to .csv or .tsv format, when you open the exported file in Excel, Excel will incorrectly convert the date.


Set the order for day/month/year for the user profile Date format to be the same as in the local Date and time format that is set in your computer’s regional settings.

For example, if the Data and time format on your computer is set to be mm/dd/yyyy, set the Date format in the user profile to also be mm/dd/yyyy.

For more information about setting the date format in UC Analytics, see the Unified Communications Analytics User Guide.


When you export an insight to either .pdf or to Word (.docx) format, there might be discrepancies in how information is displayed:


In the details browser, the Exchange server details are not shown in the Exchange ActiveSync / Servers / Server Sync Times insight.

This scenario can occur if you collect ActiveSync data for a time period from before you installed the product. The insight is populated with the historical ActiveSync data collected from the IIS logs (Exchange IIS Logs data source). However, the server detailed data is populated from the once-a-day “snapshots” collected from Active Directory (Exchange Configuration data source).

Since you had not run the Exchange Configuration data collection during that time period, there is no Exchange server detailed information in the database. This issue decreases over time as the server data is accumulated through daily Exchange Configuration data collections.


In the Mailboxes - Folders Inventory insight, if there is a mailbox owner with many folders that span more than one displayed insight page, when you click a heading (such as Size) to sort the fields, sorting does not work.


The total number or size of messages (Unique Messages, Total Volume) will not always equal the sum of sent and received messages. The reason is that the total includes messages that were “sent on behalf of”, while the total of sent messages does not include this type of message. For example, when user A sent a message on behalf of user B, the insight would show the total number of messages of user B is 1, while the number of sent messages is 0.

The following insights are affected:


When configuring UC Analytics for subscriptions (Admin Settings | Subscriptions) you have the option to require authentication to the SMTP server that is used for email subscriptions.

UC Analytics cannot send subscription emails through Exchange receive connectors that meet all the following conditions:


Subscriptions might not send long emails, such as insights with large tables, in MHTML or HTML format. Depending on message size limit set on the specified SMTP server for email subscriptions, a subscription in MHTML or HTML format with a long body might be blocked.


If a user does not receive an email subscription in MHTML or HTML format, switch the subscription format to either .pdf or .docx format in which the size of the message is much smaller.


For Insight Visibility and Security (data access settings), UC Analytics does not support a configuration in which specified users are in a separate forest from the forest in which UC Analytics is installed. For on-premise target environments that are configured for Authentication-enabled, all users that are entered for Insight Visibility and Security must be in the same target environment as UC Analytics.


Time Zone Offsets: When you create a subscription, the current time zone offset (such as UTC -04:00) is captured and is used for the future subscription schedule. This captured time zone offset does not change with Daylight Saving Time (DST). You must manually change the existing subscription schedule when DST begins and ends.

Using a time zone offset override

Each time you log in, your user profile’s time zone offset is updated to the time zone of the client computer. The offset is used for executing queries and affects the display of data, including scheduled insights.

If you want your data queries to always run using a particular time zone offset regardless of your current location or whether DST is active, you can set an override in your user profile page. To access your user profile, click your user name in the top right corner of the Analytics web site and select Edit Profile.

If you travel to a different time zone, or when the time changes due to daylight saving, the scheduled subscription emails still use the old time settings until you log in to UC Analytics in the new time zone or after the time switch.


The UC Analytics Storage Engine service cannot start due to a failure to read a file descriptor in one of the commit logs. The Storage Engine tries to restart and fails because of a commit log replay issue, resulting in an error in the Cassandra.log file such as the following:

By default the log file is located in the following path:

C:\Program Files\Quest\UC Analytics\Storage Engine\bin\Cassandra.log


Delete the corrupted commitlog file that is specified in the error message and restart the Storage Engine service.


All the files in the Storage Engine directories must be available for reading and writing at all times. If you have any automated processes running on the Storage Engine directories that lock files, you might encounter problems. The Storage Engine, when it encounters one of its files that cannot be written to or deleted, stops running. You must restart the service to get the Storage Engine working again.


The Data Engine does not communicate with the Query Engine when a proxy is enabled on the Data Engine server.


Disable the proxy or ensure that the proxy allows direct communication to the Query Engine server (which can be the same server as the Data Engine).


System requirements

If you are installing UC Analytics, the computer must meet the following minimum requirements:


Minimum: Quad core 64-bit computer.


Minimum: 24 GB.


X GB where X is the required disk space for collected data

For estimates regarding the required disk space for the collected data for different numbers of users for all the platforms, see the UC Analytics Deployment Sizing.xlsx spreadsheet which can be found under Documentation in the autorun.exe.

Operating system

One of the following:

Any server on which a UC Analytics service or service role is installed must have a static IP address defined.

For a distributed deployment, the Remote Registry Service must be running.

Generally, using a NAS/SAN device for the Storage Engine is not supported. UC Analytics might support specific NAS/SAN devices but Quest would require full testing with the devices, or device simulators, to support them. Since each NAS/SAN device, depending on manufacturer, is unique, Quest will work with NAS/SAN vendors to certify or qualify a device but the NAS/SAN vendor must be willing to assist. To engage a NAS/SAN vendor and initiate the qualification process, you would send an email to your NAS/SAN vendor and contact Quest Support.

To install and run UC Analytics, the following software requirements must be met on the computers that host these specific UC Analytic services:

Web site

IIS (Internet Information Services) 7.0 or later

For the required configuration for IIS logging, see Appendix C in the Quest UC Analytics Deployment Guide.

Data Engine service

Also, since the Microsoft Azure AD cmdlets use the proxy settings for Internet Explorer, ensure that the Internet Explorer proxy settings for the service account are set correctly.

Query Engine service

64-bit Java Runtime Environment (JRE) 8

- OR -

Zulu OpenJDK 8

For information and downloads, see

Storage Engine service

64-bit Java Runtime Environment (JRE) 8

- OR -

Zulu OpenJDK (Java 8)

For information and downloads, see

For information about the rights and permissions needed to configure UC Analytics and by the credentials used to gather information, see the Quest UC Analytics Deployment Guide.

Gathering environment

The following is a list of the minimum environments that are supported for data collection:

Supported browsers

To access the UC Analytics web site, use one of the following browsers:

For users with large amounts of data, it is recommended that you ensure your browser is in 64-bit mode.

For more information about setting Internet Explorer to 64-bit mode, see the section titled “Using a browser in 64-bit mode” in the UC Analytics User Guide.

Product licensing

In release 8.1, UC Analytics switched to a new license type (.dlv) and emailed the new license file to existing customers.

If you are an existing customer with 8.1 or later installed, you will have a .dlv license file installed. When you upgrade, your dlv license will continue to work if it is not expired.

To install a new license, use the following procedure to activate it.

Click the Manage Licenses button.
Click Add License and browse to the location where license file (xxx-xxxx.dlv) is copied and install it.

After you download a trial version or purchase UC Analytics, you will receive a license file (.dlv) through email that is used to activate UC Analytics. After you install UC Analytics but before you can use UC Analytics, you must activate the license.

Click the Manage Licenses button.
Click Add License and browse to the location where license file (xxx-xxxx.dlv) is copied and install it.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating