Page History
...
Processing the usage data can fail due to database connection problem.
Solution: Verify that: the
- The CardioLog Scheduling Service login account can connect to the CardioLog database and is assigned a db_owner role.
- Your system has enough resources according to system requirements.
- There is sufficient free space in the CardioLog database transaction log file and in the TEMP database transaction file.
Anchor report scheduling report scheduling
Report Scheduling
| report scheduling | |
| report scheduling |
...
_____________________________________
Time : 10/28/2008 4:59:59 AM
Message : Start Scheduler
_____________________________________
// Deleting cached reports versions (controls data and charts images)
Time : 10/28/2008 4:59:59 AM
Message : Deleting Temp Images
_____________________________________
Time : 10/28/2008 5:00:03 AM
Message : Deleting Controls Cache
_____________________________________
// Getting all the reports that should be generated automatically
Time : 10/28/2008 5:00:03 AM
Message : Getting scheduled reports
_____________________________________
// Generating the reports and sending emails to their distribution lists
Time : 10/28/2008 5:00:12 AM
Message : Report Id: 1a88f32d-fb86-4346-bcfb-005ed2661083 was generated successfully.
_____________________________________
Time : 10/28/2008 5:00:15 AM
Message : Report Id: bd3496ae-8e08-4df8-b1ab-027b4959d63a was generated successfully.
_____________________________________
Time : 10/27/2008 6:12:38 AM
Message : Mail sent to: james james.wright@intlock.com
_____________________________________
// Updating service last run time in CardioLog database
Time : 10/27/2008 6:12:38 AM
Message : Updating last run global setting
_____________________________________
// Service finished successfully
Time : 10/27/2008 6:12:38 AM
Message : End Scheduler
Possible Faults
The Generation of reports on the CardioLog database can fail due to:
1. Insufficient permissions
...
Errors in the log file:
"Error : Report Id: 060ad715-cd6e-4e02-9e3a-b94ab3f63d8f failed. Exception: The remote server returned an error: (500) Internal Server Error."
"Error : Report Id: 3dc7a74d-3445-450a-ad43-405fd2ad1ce8 failed. Exception: The operation has timed out."
Solution: see Intlock's tips for efficient report creation or contact us.
In order to identify the report causing the problem, run the following query against the CardioLog database:
where EntityId='[the report id]'
[the report id] - the report GUID from the error message in the log file. For instance: 060ad715-cd6e-4e02-9e3a-b94ab3f63d8f
...
_____________________________________
// Loading user categories data from custom web service (to categories.xml)
Time : 11/23/2008 12:59:58 AM
Message : Loading from: http://CategoriesServer/UserCategoriesHR/categories.asmx/GetEmployees
_____________________________________
// Loading user categories data from CardioLog database
Time : 11/23/2008 1:00:31 AM
Message : Creating category manager
_____________________________________
// Comparing both repositories and updating CardioLog database
Time : 11/23/2008 1:00:32 AM
Message : Persisting
_____________________________________
// Updating service last run time in CardioLog database
Time : 11/23/2008 1:00:40 AM
Message : Updating last run global setting
_____________________________________
// Service finished successfully
Time : 11/23/2008 1:00:40 AM
Message : Persist finished.
_____________________________________
// Adding new users to the CardioLog database
Time : 10/5/2008 12:58:47 AM
Message : User: 'Intlock\ronh' does not exist in the system - Adding.
Possible Faults
Loading from the User Categories web service can fail due to:
1. Timeout caused by a slow network
Solution: Increase the web service timeout.
The categories User Categories web service timeout can be configured in the Web.config file.
Edit Edit the <httpRuntime> element in the <system.web>section:
Execution . The Execution Timeout property - indicates the maximum number of seconds a request is allowed to attempt to execute before being automatically shut down by ASP.NET. The default timeout is 90 seconds.
Note - when : When using a custom user data web service, contact the web service developer to increase the user categories web service timeout.
...
_____________________________________
Time : 28/11/2012 00:00:00
Message : Start SEO Analysis
_____________________________________
Time : 28/11/2012 00:00:00
Message : Getting scheduled jobs
_____________________________________
Time : 28/11/2012 00:00:00
Message : Start crawling 'http://www.intlock.com/'
_____________________________________
Time : 28/11/2012 00:02:42
Message : Crawling 'http://www.intlock.com/' finished successfully.
_____________________________________
Time : 28/11/2012 00:02:42
Message : Updating last run global setting
_____________________________________
Time : 28/11/2012 00:02:42
Message : End SEO Analysis
_____________________________________
Possible Faults
Crawling a website can fail due to:
1. Insufficient permissions to browse the website
Solution: set credentials Set sufficient permissions for the SEO crawl.
2. Reading and writing the user data to the CardioLog database can fail due to insufficient permissions database connection problems.
...
Note: In order to troubleshoot issues during the crawl process, turn on extended logging for the CardioLog web application, execute the crawl immediately via the CardioLog UI and view the log file - CardioLogUI.log.
...
Configuration Files -
- ADTree web - Web application (extended logging for Active Directory Updates, creates the ADXmlTree.log file) - [CardioLog Installation Folder]\ADTree\web.config
- SP20XXTree web - Web application (extended logging for Portal Tree Updates, creates the SP20XXTree.log file) - [CardioLog Installation Folder]\SP20XXTree\web.config (XX - 07 for MOSS 2007, 10 for SharePoint 2010, 13 for SharePoint 2013)
- CardioLog Scheduling Service (extended logging for service components, creates the CardioLogServiceComponents.log file) - [CardioLog Installation Folder]\CardioLogScheduleServices\CardioLog.Services.exe.config
- VisitorSegments web - Web application (extended logging for User Categories Updates, creates the VisitorSegments.log file) - [CardioLog Installation Folder]\VisitorSegments\web.config
- CardioLog web - Web application (extended logging for the CardioLog UI, creates the CardioLogUI.log file) - [CardioLog Installation Folder]\CardioLog\web.config