HotFix v2.0.8.4 for CardioLog Analytics and SharePoint Marketing Suite Released!

HotFix for CardioLog Analytics and SharePoint Marketing Suite [v2.0.8.4]

We have released a HotFix for CardioLog Analytics and SharePoint Marketing Suite [v2.0.8.3], which includes the following fixes.

If you have customized the Tracking Agent code in your environment (i.e. customized search) or the SharePoint Tree Adaptor (i.e professional services), please contact us before applying this HotFix. 

BUG: "Exception of type 'System.OutOfMemoryException' was thrown” error in the Portal Tree Updates job.
BUG: “Input string was not in a correct format” error in the Portal Tree Updates job.
BUG: The Portal Tree Updates job fails to refresh the tree structure when using the Website Tree adaptor, when the Page URLs crawled by the adaptor do not match the existing page URLs in the tree structure (it is case sensitive).
BUG:  "Exception: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding" error in the Portal Tree Updates job.
BUG: “Arithmetic overflow error converting expression to data type int.” error in the Portal Tree Updates job.
BUG: “Exception: The given value of type String from the data source cannot be converted to type nvarchar of the specified target column“ error in Active Directory Updates job when the user display name is longer than 200 characters.
BUG: “Failed to get yammer access token” error in the Yammer adaptor, when trying to connect to Yammer.
BUG: “The INSERT statement conflicted with the FOREIGN KEY SAME TABLE constraint "FK_tab_yammer_item_tab_yammer_item". The conflict occurred in database "CardioLog", table "dbo.tab_yammer_item", column 'UID'.” error in the Yammer adaptor, when retrieving Yammer groups.
BUG: “Invalid length for a Base-64 char array or string." error in the Yammer adaptor settings page
BUG: “You do not have permissions to view this report" error when using the Site Statistics feature in site lists and libraries, with SharePoint based report permissions enabled.
BUG: User categories columns added to the Unique Users table report occasionally disappear 
BUG: Incorrect navigation reports when clicking on multiple documents on the same page.
BUG: The “Page Views” report returns results for SharePoint deleted items 
BUG: "Error converting varchar to bigint" error in the Search Destination Pages report
BUG: Server error 500 in EventCollector/monitor.asmx 
BUG: Page URLs for sub-domains are not included in the tree structure when using the Website Tree adaptor
CHG: Improved performance for the Portal Tree Updates job when importing documents and list items versioning information for SharePoint lists and libraries
CHG: Improved error handling in the tracking agent, when the SharePoint 2013 search pages are customized
CHG: Exclude custom events sent by the CardioLog API from navigation reports
CHG: The response timeout for pages crawled by the Website Tree adaptor and the SEO Reports module is configurable
CHG: Improved performance for the “Page Views” table report with the “Show first level child items only” option enabled  

Note – If you have not upgraded your product to the latest release yet (v2.0.8.3), it is highly recommended to do so (as detailed here), and prior to applying this HotFix. Find out what's new by viewing our Release Notes.

The updated and improved version includes many new features such as:


Editions and versions

This HotFix is compliant with CardioLog Analytics Standard, Professional and Enterprise editions and SharePoint Marketing Suite Professional and Enterprise editions, version only.

To find out what is your product version, go to Administration > Product License.

Installation Instructions

Download the HotFix package from here.

Note: This HotFix includes modified SQL stored procedures and updated application files. It does not require any downtime of SharePoint.

Right click on the downloaded package zip file, select Properties > General and click on "Unblock" before unzipping it.

See installation instructions in the embedded README file.

Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk