Below are common questions and concerns with their solutions relating to configuring and troubleshooting CardioLog Analytics. This guide is recommended for Administrators and technical support individuals.
Questions or Concerns | Solutions |
---|---|
How can I monitor an additional web application in my SharePoint farm? | To monitor an additional web application in your existing farm please follow the instructions in SharePoint Tree Adaptor |
When I run the IIS Logs Import, I get the following error, "Cannot run process cmd.exe: Cannot open : Error opening files: Error opening file 'C:\inetpub\logs\LogFiles\W3SVC1\ex110101.log': The system cannot find the file specified. " | This issue occurs when running a 32-bit version in 64-bit systems. Ideally, upgrade to the latest 64-bit release version. In order to workaround this issue, edit the CardioLog machine registry (and the CardioLog Installation key): |
Why do I get "Missing or invalid product license" error, even though my license is valid? | If your version is lower than 2.0.7.0, browse to CardioLog > Administration > CardioLog Scheduling Service, Click on each one of the service components and verify that none of the services schedule type is set to "Once". Restart the CardioLog Scheduling Service. |
The CardioLog Scheduling Service is started but all the jobs fail. Why do I see the "Exception has been thrown by the target of an invocation" error in my log file. | This error usually occurs when:
sc config "CardioLog Scheduling Service" depend= MSSQLSERVER |
Why are my SharePoint Publishing Sites not being tracked when using the "CardioLog Analytics SharePoint Feature" | The CardioLog Analytics SharePoint Feature will work only for master pages which contain the following control in the head section: This control is included in the master pages for all SharePoint templates, except for the MOSS Publishing Site master page. Add this control to each of your master pages, right before the closing </HEAD> tag. Alternatively, you can perform a single update, by using a top master file which is included in all of the Publishing Sites master pages. |
Why do I get the error "Error: trying to remove main branch, persist stopped" when running Portal Tree Updates? | This is a safety mechanism which is triggered in order to prevent the removal of a monitored environment from CardioLog (eg. a SharePoint farm, a custom website). It is raised when removing a tree adaptor web service URL from the web services list in Portal Tree Updates service configuration. If you wish to bypass the safety mechanism and remove a monitored environment (eg. a main tree branch in the CardioLog tree structure), follow these steps:
Note: The monitored environment you have removed will be marked as deleted in the CardioLog tree structure. In order to view history usage data in reports for it, go to the Analysis Center and click Show Deleted Items.The removed monitored environment tree branch will appear in red in the tree structure and will be available for reporting. |
Why do I get the error "Navigation to the webpage was canceled" when exporting a report to PDF? | When exporting a report to PDF and opening the PDF file, you may encounter the "Navigation to the webpage was cancelled" error. The export operation is executed on the CardioLog server. It opens a web browser object with the report, takes a screenshot of it and saves it as a PDF file. This process can fail if the report URL is inaccessible locally on the CardioLog server, due to insufficient permissions or security restrictions. In order to resolve the issue, open [CardioLog Installation Folder]\CardioLog\web.config and edit the following key value: <add key="CardioLogPDFRoot" value="http://[CardioLog Host Name]:[CardioLog Port Number]/" /> If this did not resolve the error, try the following steps:
Please contact Intlock Support if you need any further assistance. |
Why do I get the error "Server Error in '/CardioLog' Application - Access is denied." when I open Administration > System Diagnostics? | First, verify that the CardioLog application user account has local administrator permissions on the CardioLog application server and has permissions for starting and stopping the CardioLog services. Secondly, open IIS Manager and navigate to IIS > Connections > Application Pools > Actions > Stop, and restart the CardioLogApplicationPool. |
What is my product version number? | To determine your product version, in the navigation pane, open Administration, and click Product License. This page also displays all features available to you. |
Why does the 'Last Event #' in the tracking agent display as 'None' or 'N/A'? | In order to more easily manage data collection issues, please see Troubleshooting Usage Data Collection Issues in Troubleshooting The Tracking Agents. |
Why do I get the error "A configuration error has occurred." on my SharePoint WFEs? | The following error may occur on the SharePoint WFEs Event Log when installing the CardioLog Analytics Tracking Agent Feature: 3008
These errors may appear when the CardioLogAgent web application under the SharePoint website /_layouts folder in IIS is not configured as a web application. In order to resolve it, open IIS Manager > Right click the CardioLogAgent directory located under the SharePoint website (http://sharepoint in this example) /_layouts folder and select "Convert to Application" |
Why do I get the error "Invalid object name 'tab_iis_log_import_temp'" when I run the IIS Logs Import? | CardioLog Analytics uses the Log Parser tool in order to parse the IIS log files. Verify that the following key in the [CardioLog Installation Folder]\CardioLog\web.config file contains the correct path to the Log Parser tool installation folder, which should be: <add key="IISLogParserPath" value="C:\Program Files (x86)\Log Parser 2.2\LogParser.dll" /> You can download the latest version of Log Parser from Microsoft. |
How do I change my user interface's language and date format? | In order to change your user interface language and date format, perform the following steps:
Available languages:
|
Why do I get the warning "Failed to collect SQL statistics" when I run the Usage Data processing job? | When running the Usage data Processing job, CardioLog Analytics collects internal SQL statistics on database performance, including the current database size, the index fragmentation rates and I/O rates for future use. In order to collect these statistics the CardioLog service account should have the "view server state" permission on the CardioLog database. If you encounter the warning below, please allow "view server state" permission for the CardioLog service account on the CardioLog database. "Message : Failed to collect SQL statistics. (Exception: The user does not have permission to perform this action. The user does not have permission to perform this action.)" |
How do I create the CSV of my Site Collection for the SharePoint Online Adaptor? | To import your SharePoint Online Site Collection using CSV that will then be applied via the SharePoint Online Tree Adaptor, follow these steps: 1) Create a folder on the root drive (If not C:/ just change location in script) called Scripts. Please run this script on a regular basis either manually or using automation to update the CSV frequently. We recommend keeping this updated daily in order to keep all changes made in your Online environment in sync with your Portal Tree and your reports. |
How do I configure the CardioLog Agent to collect users' real IP addresses when they go through a Proxy? | If your users access your site through a proxy, then the CardioLog Agent will collect the proxy IP address instead of the users real IP address. By default, CardioLog Agent looks at the "REMOTE_ADDR" HTTP request server variable. When using a proxy, this variable will only contain the IP of the proxy server. Alternatively you can set the CardioLog Agent to look at the "HTTP_X_FORWARDED_FOR" HTTP server variable, which will in most cases contains the end user real IP address behind the proxy. <add key="UserIpBehindProxy" value="true" /> If the "CardioLog Analytics" SharePoint feature is installed on your SharePoint on-premise farm, the CardioLogAgent folder should be located on all SharePoint WFEs within the SharePoint website "_layouts" folder: SharePoint 2007 - "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\CardioLogAgent\". Otherwise, the CardioLogAgent folder should be located in the CardioLog Installation folder, which is located by default in C:\Program Files\Intlock\CardioLog\CardioLogAgent. |
How do I configure email in CardioLog? | You can automate different actions by configuring email contacts using the CardioLog Scheduling Service. This will allow you to:
|
Why do I get an authentication login box when I try to access the CardioLog web site locally on the server, even after submitting correct network credentials? | This issue may occur when the server tries to browse to itself recursively. Try to browse to the CardioLog web site from your workstation or from a different server to confirm that this is the issue. To resolve this issue on the server, you will have to disable the Loop Back Check in the registry.
|
Why do I receive the error "Access to the path 'C:\Program Files\Intlock\CardioLog\CardioLogAgent\CardioLogAgent.js' is denied" in the Configuration Wizard? | When selecting "Yes, install and activate the 'CardioLog Analytics' SharePoint Feature" in Step 2 of the Configuration Wizard, the following error may appear at the top of the window: Access to the path 'C:\Program Files\Intlock\CardioLog\CardioLogAgent\CardioLogAgent.js' is denied This error is raised when the CardioLog service account has insufficient permissions. Please confirm that the CardioLog service account is a local administrator on the CardioLog server and that it has all required permissions, then run the the Configuration Wizard when you are logged on to the server with the CardioLog service account. If you would like to try a different user, change the account in IIS (the identity of the CardioLogApplicationPool) and for both CardioLog Windows services (the log on account for CardioLog Scheduling Service, CardioLog Diagnostics Service). Confirm the new account is a db_owner of the CardioLog database. |
Why do I get the error "Error installing the 'CardioLog Analytics' Feature: Failed to restart service. Server Response: Service SPAdminV4 was not found on computer'" in the Configuration Wizard? | When selecting "Yes, install and activate the 'CardioLog Analytics' SharePoint Feature" in Step 2 of the Configuration Wizard, the following error may appear at the top of the window: Error installing the 'CardioLog Analytics' Feature: Failed to restart service. Server Response: Service SPAdminV4 was not found on computer '.' This error is raised when the CardioLog service account has insufficient permissions. Please confirm that the CardioLog service account is a SharePoint farm administrator and a local administrator on all SharePoint servers and that it has all required permissions, then run the the Configuration Wizard when you are logged on to the server with the CardioLog service account. You can also choose to install the feature manually and skip Step 2 of the Configuration Wizard. If you would like to try a different user, change the account in IIS (the identity of the CardioLogApplicationPool) and for both CardioLog Windows services (the log on account for CardioLog Scheduling Service, CardioLog Diagnostics Service). Confirm the new account is a db_owner of the CardioLog database. |
Why do I get the error "stsadm addsolution error: Object reference not set to an instance of an object." in the Configuration Wizard? | When selecting "Yes, install and activate the 'CardioLog Analytics' SharePoint Feature" in Step 2 of the Configuration Wizard, the following error may appear at the top of the window: There was some problem with the installation or activation of the 'CardioLog Analytics' SharePoint Feature: This error is raised when the CardioLog service account has insufficient permissions. Please confirm that the CardioLog service account is a SharePoint farm administrator, a local administrator on all SharePoint servers, a "db_owner" on the SharePoint config database, and it has all required permissions, then run the the Configuration Wizard when you are logged on to the server with the CardioLog service account. If you would like to try a different user, change the account in IIS (the identity of the CardioLogApplicationPool) and for both CardioLog Windows services (the log on account for CardioLog Scheduling Service, CardioLog Diagnostics Service). Confirm the new account is a db_owner of the CardioLog database. |
Why do I get the error "HTTP Error 407 - Proxy Authentication Required" in the CardioLog UI main window? | When a proxy is configured in your network you may encounter the following error in the CardioLog UI: HTTP Error 407 - Proxy Authentication Required To resolve this issue, insert the following code into the [CardioLog Installation Folder]\CardioLog\web.config file: <system.net> |
Why do I get the error "'Error in '_layouts/CardioLogAgent' Application: That assembly does not allow partially trusted callers" when troubleshooting malfunctioning tracking? | You may notice that once you have completed the installation of CardioLog and/or updated to the latest minor version, that tracking has stopped functioning correctly and you may have received the error while using Browser Dev Tools. When downloading any minor updates, make sure to right click on the .zip file and select Properties > Click Unblock. In some environments with strict security settings, any compressed files that contain .dll files will be blocked automatically. The two methods to resolve this are:
Clear your Browser Cookies and Cache and test to see if tracking is now functional. Sometimes an IIS Reset is also required on the WFE and CardioLog Application Server to restart the tracking action. |
Why do I receive error 401.1 when I browse to a web site that uses Integrated Authentication? | The source of this error is usually LoopBack, a JavaScript framework, which typically uses the address 127.0.0.1 for tests. LoopBack can keep transferred information internal and block some communication between networks, which causes the 401.1 Error to appear. There are two methods to resolve this issue. Either specify a host name, which is preferred if NTLM Authentication is required, or simply disable LoopBack Check, which we don't recommend unless completely necessary. Method 1: Specify host names (This is the preferred method if you would like to use NTLM authentication) To specify host names that are mapped to the LoopBack address and can connect to Web sites on your computer, follow these steps:
Method 2: Disable the LoopBack check The second method is to disable the LoopB ack check by setting the DisableLoopbackCheck registry key. To set the DisableLoopbackCheck registry key, follow these steps:
|
My SharePoint portal runs on SSL. Why do I get an authentication login box for the CardioLog server after installing the CardioLog tracking agent? | In order to avoid authentication prompts or browser security messages while working with SSL, do one of the following:
|
How can I import user data from Extradium into CardioLog Analytics? | Riolinx provides an API that allows you to export Extradium user database to other systems. A CSV export tool provided along with the source code is available from Riolinx. You will be prompted to sign in in order to access the download. In order to import Extradium users into CardioLog Analytics, and filter reports by specific users or by specific profile properties, you can develop a web service that generates a relevant XML response. For more information, see Configuring Visitor Segmentation for Authenticated Users. |
What is the impact of the CardioLog JavaScript tracking code on the SharePoint page response time? | The CardioLog agent has minimal impact on SharePoint page load and response time. The CardioLog agent is composed of 300 Kb of JavaScript code, with 270 Kb (90%) of the code cached in the client browser. The tracking code is loaded on "page load", and connects with the CardioLog server in asynchronously, to avoid affecting the SharePoint page. |
Can I change the URL for the CardioLog web applications and services in order to include a fully qualified domain name (FQDN) or a different port number? | You can update the domain, machine name or port number for the various CardioLog web applications and services by following these steps:
|
How can I change the location of the CardioLog Logs folder? |
|
Does CardioLog Lite work on a SharePoint farm with multiple front ends? | No, only the commercial editions support multiple front ends. |
Why do I get an authentication login box for the CardioLog server when I browse my SharePoint portal even though I have added the tracking code to core.js/init.js? | There are two ways to remove the authentication prompt:
|
How do I fix the CardioLog Tracking Agent solution when it appears stuck on "deploying" in SharePoint? | Sometimes SharePoint will not fully activate the CardioLog Tracking Agent solution. You can check the status in SharePoint Central Administration by clicking on System Settings and then Manage Farm Solutions. If the CardioLog Tracking Agent never changes from "Deploying", follow these steps: 1. Make sure that the SharePoint timer service is started on all SharePoint servers . This includes both web front ends (WFEs) as well as application servers and central admin servers. 2. Restart the SharePoint Administration service on all SharePoint servers This includes both WFEs as well as application servers and central admin servers. 3. Restart all of your SharePoint servers 4. Make sure all of your SharePoint servers in your farm are correctly in the same time zone 5. Execute the following command on all the SharePoint servers in the farm stsadm -o execadmsvcjobs 6. Cancel the deployment job from within SharePoint Central Administration, remove the CardioLog Tracking Agent solution completely and then add the solution again to SharePoint. 7. Check the status of the jobs by executing the following command. It will show you a list of all pending and active deployments. stsadm -o enumdeployments |