Versions Compared

Old Version 7

changes.mady.by.user Paul Berkowitz

Saved on

compared with

New Version Current

changes.mady.by.user Sigalit Hassid

Saved on

Key

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

...

...

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

These files are limited to 8MB each. 

In addition, CardioLog creates the following XML files -

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

...

  • ADTree web application (extended logging for Active Directory Updates) - ADXmlTree.log
  • SP20XXTree web application (extended logging for Portal Tree Updates for SharePoint 2007, 2010 and 2013) - SP20XXTree.log (XX - 07 for MOSS 2007, 10 for SharePoint 2010 and 13 for SharePoint 2013)
  • CardioLog Scheduling Service (extended logging for all service components, including Portal Tree Updates for SharePoint 2013 API method, SharePoint 2016 and SharePoint Online) - 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

The extended log files have no file size limit. It is recommended to turn off extended logging when it is not needed and archive/delete these log files periodically.

Anchor
cardiolog scheduling
cardiolog scheduling
CardioLog Scheduling Service

...

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

Anchor
active directory
active directory

...

Users and Groups Updates

Log File - ADAgent.log:

_____________________________________

// Loading users and groups from Active Directory

Time : 6/19/2008 12:00:07 AM

Message : Loading directory: corp.company.com

Message : Loading from web service: http://[CardioLog server name:port]/ADTree/default.aspx

_____________________________________

// Loading users and groups into the CardioLog database

Time : 6/19/2008 12:25:38 AM

Message : Loading xml to db...

Time : 6/19/2008 12:25:42 AM

Message : Loading xml to db: Success

_____________________________________

// Comparing both repositories and updating CardioLog database

Time : 6/19/2008 12:25:50 AM

Message : Refreshing users and groups...

_____________________________________

Time : 6/19/2008 12:25:50 AM

Message : Refreshing users and groups: Success

_____________________________________

// Updating service last run time in CardioLog database

Time : 6/19/2008 12:28:02 AM

Message : Updating last run global setting

_____________________________________

// Service finished successfully

Time : 6/19/2008 12:28:02 AM

Message : Done

...

In order to turn on message logging to trace the CardioLog service components, add the "Verbose,Message" switch to the "logType" key in the component configuration file -

<add key="logType" value="Verbose,Message,Warning,Error" />


In order to turn off message logging for the CardioLog service components, remove the "Verbose,Message" switch from the "logType" key in the component configuration file -

...