Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Below are common questions and concerns with their solutions relating to installing and activating CardioLog Analytics.

 

Is CardioLog Analytics available as SaaS?

CardioLog Analytics is available both as an on-premise solution and as a SaaS solution (software as a service).

For more information please visit our website - http://www.intlock.com/intlocksite/productsandservices/cardiolog-analytics-saas-on-demand.asp

 What are the CardioLog installer prerequisites?

The CardioLog installer requirements can be found here, and the permissions required can be found here.

Which CardioLog Analytics Installer should be used with Support for SQL 2014

When using SQL 2014, please download the following CardioLog Analytics installer - version 2.0.8.3:

64-bit: http://www.intlock.com/intlocksite/Downloads/cardiolog/CardioLog-Analytics-x64-2.0.8.3-2014.zip

Why do I get the following error "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms" when I launch CardioLog?

This issue may occur when a security policy with Federal Information Processing Standards (FIPS) is enforced on the server. To resolve this issue, you will have to disable the FIPS Algorithm Check in the registry.

  1. Go to Run and type regedit to open the registry editor.
  2. In the Registry Editor, click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy
  3. Right-click FipsAlgorithmPolicy, and then click Modify.
  4. In the Value data box, type 0, and then click OK.
  5. Quit the Registry Editor, and restart your computer

Why do I get the following error "HTTP Error 403.1 - Forbidden" when I launch CardioLog

When you launch CardioLog, do you receive an error message that resembles the following:

HTTP Error 403.1 - Forbidden
HRESULT: 0x80070005
Description of HRESULT: You have attempted to run a CGI, ISAPI or other executable program from a directory that does not allow executables to run.

This problem occurs when CardioLog is hosted with Internet Information Services (IIS) 7.0 and the appropriate script handler permission or executable handler permission are not set for the CardioLog directory where the requested resource resides. 

To resolve this issue, follow these steps:

  1. In IIS Manager, locate the CardioLog website.
  2. In Features view, double-click Handler Mappings.
  3. In the Action pane, click Edit Handler Permissions.
  4. Click to select Script and Execute, and then click OK.

Why do I get the error "This app can't run on your PC" when I run the setup file?

This issue occurs when the setup file is corrupted, or not suitable for the operating system platform.

In order to resolve this issue,

  1. Install the product on a machine (physical or virtual) running a Windows Server, according to our system requirements.
  2. Download the correct version suitable for your operating system platform (x86 installer for 32-bit operating systems and x64 installer for 64-bit operating systems).
  3. Make sure the setup file size is 20.3 MB (21,352,448 bytes). If the setup file was not fully downloaded, it will be corrupted and will not open.

How do I complete my installation and optimize my system?

Please perform the following steps to complete the product configuration and ensure system health:

A. System Requirements
Verify that your system meets the minimum hardware and software requirements.
B. Usage Data Collection
  1. Verify usage data collection on each web application. 
  2. Verify that you do not exceed the number of page views, SharePoint Farms and WFEs allowed in your license (see the [CardioLog Installation Folder]\CardioLogSchedulingServices\Logs\Maintenance.log and OMAgent.log files).
  3. Consult our support team if your website is accessed via NLB, VPN, FW/Proxy, SSL, public/alternate URLs, internal/external, direct/remote. 
  4. Consult our support team if you have made any customizations in your SharePoint environment (i.e customized search pages).
C. System Configuration and Monitoring
  1. Assign an administrator who will be responsible for product maintenance. 
  2. Assign roles for users.
  3. Configure email alerts for scheduled services and event collection thresholds that will be sent to the administrator.
  4. Configure the Active Directory Updates service in order to segment authenticated visitors by their user names and their groups.
D. Optimization and Fine Tuning

The fine tuning process is essential to ensure accurate and useful data. It is highly recommended to perform this process 2-3 weeks after the initial installation on the production environment.

  1. Execute the SQL script to identify lost events and send the results to our support team. 
  2. Define URL mappings if needed.

Why does the tracking agent pop-up not show up when I click Ctrl+F12, or the Agent Console shows up without any content?

In order to troubleshoot data collection issues, see the complete troubleshooting guide.

 Why do I receive an error in Agent Console ("CardioLog" tab)?

In order to troubleshoot data collection issues, see the complete troubleshooting guide.

What are the required web server (IIS) role services?

Follow the following role services installation instructions depending on your server operating system:

Windows Server 2012, Windows Server 2012 R2:

  1. In Server Manager, select Dashboard, and click Add roles and features.
  2. In the Add Roles and Features Wizard, on the Before you begin page, click Next.
  3. On the Select installation type page, select Role-based or feature-based installation, and click Next.
  4. On the Select destination server page, select Select a server from the server pool, select your server, and click Next.
  5. On the Select server roles page, select Web Server (IIS).
  6. Under the Web Server (IIS) role, expand the Web Server node and then select all of the components of Common HTTP Features.
  7. On the Web Server node, expand the Application Development node, and then select ASP.NET 3.5.
  8. On the Web Server node, expand the Security node, and then select Windows Authentication.
  9. On the Web Server node, select all of the components of Management Tools.
  10. Click Next.
  11. On the Select Features page, select all of the components of .NET Framework 3.5 Features, and click Next.
  12. On the Confirmation page, confirm your selections, and then click Install to start the installation process.
  13. Click Close to close the Add Roles and Features Wizard.

Windows Server 2008:

  1. In Server Manager, under the Roles node, select the Web Server (IIS) role.
  2. In the Role Services section, click Add Role Services. The Add Role Services wizard appears.
  3. Under the Web Server role service, select all of the components of Common HTTP Features.
  4. Under the Web Server role service, expand the Application Development node, and then select ASP.NET.
  5. Under the Web Server role service, expand the Security node, and then select Windows Authentication.
  6. Under the Web Server role service, select all of the components of Management Tools.
  7. Click Next and verify the role service changes to be applied.
  8. Click Install to start the installation process.
  9. Click Close to close the Add Role Services wizard.

Windows Server 2008 R2

  1. In Server Manager, under the Roles node, select the Web Server (IIS) role.
  2. In the Role Services section, click Add Role Services. The Add Role Services wizard appears.
  3. Under the Web Server role service, select all of the components of Common HTTP Features.
  4. Under the Web Server role service, expand the Application Development node, and then select ASP.NET.
  5. Under the Web Server role service, expand the Security node, and then select Windows Authentication.
  6. Under the Web Server role service, select all of the components of Management Tools.
  7. Click Next and verify the role service changes to be applied.
  8. Click Install to start the installation process.
  9. Click Close to close the Add Role Services wizard.
  10. In Server Manager, under the Features section, click Add Features. The Add Features wizard appears.
  11. Select the .NET Framework 3.5.1 Features. Click Next and verify the feature changes to be applied.
  12. Click Install to start the installation process.
  13. Close to close the Add Features wizard.

Which ports are used by CardioLog?

CardioLog includes several system components which access multiple ports, including:

  1. CardioLog SQL database - the CardioLog web application and Windows services connect to the CardioLog database using the default SQL port with Windows or SQL authentication.
  2. CardioLog web application (UI) - CardioLog users browse the CardioLog web application using HTTP (the default port is 29999 and is configurable) or HTTPS (the default SSL port is 443) with windows authentication (NTLM).
  3. CardioLog Tracking Agent - the portal users browse to the SharePoint portal and the CardioLog JavaScript code is downloaded to their browser. The client browser connects to the CardioLog Tracking Agent web application (located on the CardioLog server) using HTTP (the default port is 29999) or HTTPS (the default SSL port 443) with Windows authentication. The usage events are sent asynchronously to the CardioLog server via the SharePoint WFE server. The SharePoint WFE server connects to the CardioLog Event Collector web application using HTTP (the default port is 29999) or HTTPS (the default SSL port 443) with anonymous access. Note - when the CardioLog Tracking Agent web application is installed directly on the SharePoint WFEs, there is no need for the client browser to be able to access the CardioLog server using HTTP/HTTPS.
  4. CardioLog Diagnostics Service (Windows service) - sends error alerts via email to CardioLog administrators using SMTP (the default SMTP port is 25) 
  5. CardioLog Scheduling Service (Windows service) - includes the following components:  
    • Usage Data Processing - connects to the CardioLog database using the default SQL port with Windows authentication.
    • Portal Tree Updates - connects to: 
      1) CardioLog database and the SharePoint configuration and content databases using the default SQL port with Windows or SQL authentication.
      2) SharePoint 'TEMPLATE' directory - \\<sharepoint server name>\C$\Program Files\Common Files\Microsoft Shared\Web Server Extensions\XX\TEMPLATE\ (XX - 12 for MOSS 2007, 14 for SharePoint 2010, 15 for SharePoint 2013) - creating a share - \\<sharepoint server name>\TEMPLATE is recommended - using the default Windows File and Printer Sharing port with Windows authentication.
      3) SharePoint API (web services) using HTTP/HTTPS.
    • Report Scheduling - connects to the CardioLog database using the default SQL port with Windows authentication and sends scheduled reports via email to CardioLog users using SMTP (the default SMTP port is 25) 
    • Active Directory Updates - connects to the Active Directory using LDAP (the default LDAP port is 389)
  • No labels