Page History
Below are common questions and concerns with their solutions relating to installing and activating CardioLog Analytics.
This guide is recommended for Administrators and technical support individuals.
Questions or Concerns | Solutions |
---|---|
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 |
...
...
What are the CardioLog installer prerequisites? | The CardioLog installer requirements can be found here, and the permissions required can be |
...
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
found here. |
Which CardioLog Analytics Installer should be used with Support for SQL 2014
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.
|
...
| |
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 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:
| |
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,
|
...
|
...
|
...
|
...
|
...
| |||||||
| Please perform the following steps to complete the product configuration and ensure system health: A. System Requirements B. Usage Data Collection |
...
C. System Configuration and Monitoring
|
...
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.
| |
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:
- In Server Manager, select Dashboard, and click Add roles and features.
- In the Add Roles and Features Wizard, on the Before you begin page, click Next.
- On the Select installation type page, select Role-based or feature-based installation, and click Next.
- On the Select destination server page, select Select a server from the server pool, select your server, and click Next.
- On the Select server roles page, select Web Server (IIS).
- Under the Web Server (IIS) role, expand the Web Server node and then select all of the components of Common HTTP Features.
- On the Web Server node, expand the Application Development node, and then select ASP.NET 3.5.
- On the Web Server node, expand the Security node, and then select Windows Authentication.
- On the Web Server node, select all of the components of Management Tools.
- Click Next.
- On the Select Features page, select all of the components of .NET Framework 3.5 Features, and click Next.
- On the Confirmation page, confirm your selections, and then click Install to start the installation process.
- Click Close to close the Add Roles and Features Wizard.
Windows Server 2008:
- In Server Manager, under the Roles node, select the Web Server (IIS) role.
- In the Role Services section, click Add Role Services. The Add Role Services wizard appears.
- Under the Web Server role service, select all of the components of Common HTTP Features.
- Under the Web Server role service, expand the Application Development node, and then select ASP.NET.
- Under the Web Server role service, expand the Security node, and then select Windows Authentication.
- Under the Web Server role service, select all of the components of Management Tools.
- Click Next and verify the role service changes to be applied.
- Click Install to start the installation process.
- Click Close to close the Add Role Services wizard.
Windows Server 2008 R2
- In Server Manager, under the Roles node, select the Web Server (IIS) role.
- In the Role Services section, click Add Role Services. The Add Role Services wizard appears.
- Under the Web Server role service, select all of the components of Common HTTP Features.
- Under the Web Server role service, expand the Application Development node, and then select ASP.NET.
- Under the Web Server role service, expand the Security node, and then select Windows Authentication.
- Under the Web Server role service, select all of the components of Management Tools.
- Click Next and verify the role service changes to be applied.
- Click Install to start the installation process.
- Click Close to close the Add Role Services wizard.
- In Server Manager, under the Features section, click Add Features. The Add Features wizard appears.
- Select the .NET Framework 3.5.1 Features. Click Next and verify the feature changes to be applied.
- Click Install to start the installation process.
- Close to close the Add Features wizard.
Anchor |
| CardioLog includes several system components which access multiple ports, including:
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
| |
Which SQL versions are supported by CardioLog? | CardioLog supports SQL Server 2008, SQL 2012, SQL 2014, SQL 2016, SQL 2017 and SQL 2019. |
Can I use CardioLog with SharePoint 2007 or WSS 3.0? | CardioLog does not support these older versions of SharePoint or WSS. CardioLog currently runs on SharePoint 2010 or higher, although we recommend upgrading your SharePoint farm to the latest version to gain the full range of features that CardioLog offers. |
Why do I receive the following error when I try to activate the license file: "ERROR: This access control list is not in canonical form and therefore cannot be modified." | Make sure you have installed CardioLog with an administrator account. If you still see the error message, follow these steps depending on the if you are running a 32-bit or 64-bit system:
|
Why do I receive a "Service Unavailable" message when I launch CardioLog? | Verify that ASP.NET is enabled in IIS, and that the CardioLog application pool account is a member of your local IIS_WPG group (for IIS 6.0 only). If you still receive a "Service Unavailable" message, then you need to reconfigure the CardioLog application pool identity:
|
If I host the CardioLog application on one server, and the CardioLog database on a second server, which one of the servers should be meet the system requirements? | The server that hosts the CardioLog Database should be the more powerful one, regarding processor speed, memory (RAM), and hard disk space. |
I have uninstalled CardioLog, but the tracking code has not been removed from my portal pages, why? | By design, some components are not removed when uninstalling the product, in order to ensure continuity of data collection. Please follow the steps in our setup guide to completely remove the remaining components. |
What is the minimum server specification if the database is on a different physical server? | If the servers are isolated, disk drive space is not crucial. However, you should allocate at least 8GB of memory for CardioLog Pro, and at least 16GB of memory for CardioLog Enterprise. The amount of resources needed for the CardioLog web application and services depends on:
|
Why do I receive the error: "Cannot establish a connection to SQL Server" during installation? | Make sure your SQL server allows remote connections. You can test the connection to the SQL server by using a UDL file: If you are using a SQL alias, you can configure it on the CardioLog application server using the clicnfg.exe utility. Please note that the account used for installing CardioLog should have the following SQL roles and permissions:
|
Why do I receive the error "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'"? | If your SQL server is hosted on a remote machine, make sure that the CardioLog application pool identity is assigned a domain user that has been assigned a db_owner role for the CardioLog database. |
Which one of our SharePoint farm servers should we run the setup file on? | You can install CardioLog on any SharePoint farm server (App / Front End / SQL) that meets the system requirements. |
Does CardioLog work with SharePoint 2007? | No, the CardioLog commercial editions support SharePoint 2010, 2013, 2016, 2019 and Online. |
Do I need extra hardware in order to install CardioLog? | CardioLog Free and Standard editions can be hosted on your existing hardware. To ensure optimal operation, it is recommended to host the CardioLog Professional and Enterprise editions on a dedicated x64 application server. The CardioLog SQL database can be hosted either on an external SQL server or cluster. See the full system requirements for more information. |
Can I install CardioLog on a virtual server? | Yes. CardioLog can be installed on a virtual server as long as the system requirements can be met. |
Why do I receive a "HTTP Error 500 - Internal Server Error" message when I launch CardioLog? | When Installing CardioLog on Windows Server 2008 or Windows Server 2012, verify that the required web server role services are installed. |