Page History

The CardioLog Diagnostics Service checks the status of the CardioLog Scheduling Service components, and can send sends error alerts via email. You can access the current status of the services through the navigation pane by clicking on Administration > System Diagnostics > Diagnostics Dashboard. By default, all CardioLog Scheduling Service components run daily at 12:00 AM, except Usage Data Processing which runs every hour on the hour, and the CardioLog Diagnostics Service which runs every day at 08:30 AM. For assistance in troubleshooting service errors, please open a new support ticket. 

...

Both the CardioLog Scheduling Service and the CardioLog Diagnostics Service write messages to log files. You can There are two ways to view the log files in two ways:

• Locally on the CardioLog server in the service logs file path.
• Remotely from via the navigation pane under Administration > System Diagnostics > System Diagnostics Dashboard. 

Viewing logs Log files can be performed accessed by a user with a local administrator account on the CardioLog application server and with a CardioLog Administrator role. The CardioLog log files are located in the [CardioLog Installation Folder]\CardioLogScheduleServices\Logs folder.

The following log files are created by default -:

• CardioLog Scheduling Service - CardioLogServices.log
• CardioLog Diagnostics Service - CardioLogSystemMonitoringServices CardioLogSystemMonitoringServices.log
• Active Directory Updates - ADAgent.log
• Portal Tree Updates - OMAgent.log
• Usage Data Processing - Maintenance.log
• Report Scheduling - CardioLogScheduler.log
• User Categories - CategoryAgent.log
• SEO Analysis - SEO.log

...

• Active Directory Updates - ADTree.xml (contains the data about AD users and groups)
• Portal Tree Updates - OMTree.xml (contains the structure of the SharePoint website)
• User Categories Updates - Categories.xml (contains additional personal user data)

The XML files are not limited in size. When extended have no file size limit.

When extended logging is turned on for troubleshooting on for troubleshooting purposes, the following log files are created -:

• ADTree web application (extended logging for Active Directory Updates) - ADXmlTree.log
• SP20XXTree web application (extended logging for Portal Tree Updates) - SP20XXTree.log (XX - 07 for MOSS 2007, 10 for SharePoint 2010 and 13 for SharePoint 2013)
• CardioLog Scheduling Service (extended logging for service components) - CardioLogServiceComponents.log
• VisitorSegments web application (extended logging for User Categories Updates) - VisitorSegments.log
• CardioLog web application (extended logging for the CardioLog user interface) - CardioLogUI.log

...

...

2. The CardioLog Scheduling Service is started but all the jobs fail. 
Error in the log file: "Exception has been thrown by the target of an invocation".

Solution: Click here for more detailsSee the Configuration FAQ for more information.

Anchor
cardiolog diagnostics cardiolog diagnostics

CardioLog Diagnostics Service

...

...

1. Starting the service can fail  fail when SMTP is not configured.

Error in the log file: 
"Error: CardioLog Diagnostics Service failed to start. (Exception: SMTP mail server is not configured)".

Solution: Click here to See Report Scheduling to configure SMTP settings.

2. Sending email alerts can fail due to a SMTP connection problem.

...

Solution: Verify that the CardioLog Scheduling Service login account has all details completed and can connect to the SMTP server.

...