Versions Compared

Old Version 6

changes.mady.by.user Paul Berkowitz

Saved on

compared with

New Version 7

changes.mady.by.user Paul Berkowitz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The JavaScript code is added to all SharePoint pages in one of the following ways:

  • Deployed through a SharePoint solution.
  • Automatically added to init.js in SharePoint 2010 and SharePoint 2013, or core.js in SharePoint 2007 or ows.js in SharePoint 2003.
  • Manually added to a common Java Script file on your SharePoint WFEs.

Anchor
removing sharepoint
removing sharepoint
Removing the CardioLog Analytics SharePoint Solution

For SharePoint on-premise, the CardioLog Analytics Feature deployment process installs the following components: 

 

Removing the "CardioLog Analytics" Feature using SharePoint Central Administration

 

  1. Deactivate the CardioLog Analytics feature to stop data collection.

To deactivate the CardioLog Analytics feature in SharePoint 2013, go to Central Administration > System Settings > Manage farm features


SharePoint 2013 - Manage farm features

To deactivate the CardioLog Analytics feature in SharePoint 2010, go to Central Administration > System Settings > Manage farm features


SharePoint 2010 - Manage farm features


To deactivate the CardioLog Analytics feature in MOSS 2007, go to Central Administration > Operations > Manage farm features


MOSS 2007 - Manage farm features

 

2. Retract the solution and remove it. 

 

For SharePoint 2013 only - Go to Central Administration > System Settings > Manage farm solutions > Click cardiologtrackingagentfeature.wsp > Click Retract Solution.


For SharePoint 2010 only - Go to Central Administration > System Settings > Manage farm solutions > Click cardiologtrackingagentfeature.wsp > Click Retract Solution.


For MOSS 2007 only - Go to Central Administration > Operations > Solution Management > Click cardiologtrackingagentfeature.wsp > Click Retract Solution.


Once the solution status shows "Not Deployed", click Remove Solution in order to completely remove the solution.

Note: The "CardioLog Analytics" Feature can also be removed by using Command Line

Execute the following commands from command prompt in order to deactivate the feature, retract and remove the solution from your SharePoint farm (edit the directory path: 1X - 12 for MOSS 2007, 14 for SharePoint 2010, 15 for SharePoint 2013):

cd C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\1X\BIN

stsadm -o deactivatefeature -force -name "CardioLogAnalytics"

stsadm -o uninstallfeature -force -name "CardioLogAnalytics"
stsadm -o retractsolution -immediate -name "CardioLogTrackingAgentFeature.wsp"
stsadm -o execadmsvcjobs
stsadm -o deletesolution -override -name "CardioLogTrackingAgentFeature.wsp"
stsadm -o execadmsvcjobs

For SharePoint Online, you can choose between pausing and un-installing the tracking code from your SharePoint online site collection/s:

 

Anchor
removing javascript
removing javascript
Removing the JavaScript Tracking Code 

 

The code is located at the end of the file, between the comments: "//Intlock tracking code start" and "//Intlock tracking code end". In order to stop data collection remove or null the tracking code

Delete your browser cache and verify that when you browse through your SharePoint website that you can no longer request the CardioLog tracking agent popup by clicking Ctrl+F12 on the keyboard or by clicking the Agent Console link.

 

Anchor
removing http
removing http
Removing the CardioLog Analytics HTTPModule for SharePoint

  1. In your SharePoint server, remove the CardioLogHttpModule.dll from the GAC (See the Microsoft help documentation for more information). 
  2. In your SharePoint server, modify the SharePoint Web.config file and remove the module registration for each web site:

    For IIS 6.0 and IIS 7.0 running in Classic Mode:

 

<configuration>
  <system.web>
    <httpModules>
      <add name="CardioLogHttpModule" type="CardioLog.HttpModules.EventsModule,CardioLogHttpModule, Version=1.19.154.6, Culture=neutral, PublicKeyToken=56b51e29d93ab3fb" />
To register the module for IIS 7.0 running in Integrated Mode:
<configuration>
  <system.webServer>
    <modules>
      <add name="CardioLogHttpModule" type="CardioLog.HttpModules.EventsModule,CardioLogHttpModule, Version=1.19.154.6, Culture=neutral, PublicKeyToken=56b51e29d93ab3fb" />
Remove the following keys:
<configuration>
  <appSettings>
<add key="CardioLog.Events.DocExtensions" value=".doc*.docx*.ppt*.pptx*.pps*.ppsx*.txt*.pdf*.xlr*.xls*.xlsx*.log*.msg*.odt*.rtf*.csv*"/>
<add key="CardioLog.Events.ExcludeUserAgents" value="Microsoft Office Existence Discovery*"/>
<add key="CardioLog.API.EventsServiceUrl" value="http://<CardioLog server>:<port>/CardioLogAPI/Events.asmx"/>
<add key="CardioLog.Events.LogFile" value="C:\CardioLogHttpModule.log"/>
<add key="CardioLog.Events.LogLevel" value="None"/><!--None,Error,Message-->
<add key="CardioLog.Events.SharePointVersion" value="2013"/>
<add key="CardioLog.Events.SupportClaimsAuth" value="true"/><!--  Support claims based authentication  -->
<add key="CardioLog.Events.ClaimsAuthRegex" value=""/>
<add key="CardioLog.Events.ClaimsAuthRegexGroupMatch" value=""/>
<add key="CardioLog.Events.CacheExpirationTimeoutInMs" value="1000"/>
  • Open the following file for editing: [Installation directory]\CardioLogAgent\js\AgentEmbed.js
    In AgentEmbed.js, set element.HandleFileExtension to true:

    element.HandleFileExtension = true;

    In versions lower than 2.0.8.0, this file is located in [Installation directory]\CardioLogAgent\AgentEmbed.aspx
  • Restart the SharePoint IIS server (iisreset).

[Installation directory] - By default, the CardioLogAgent folder is located in the CardioLog Installation folder. If the CardioLog Analytics SharePoint feature is installed, the CardioLogAgent folder is located on all SharePoint WFEs under the SharePoint website "_layouts" folder.