Required Log levels For HRC Scheduler

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(New page: == Required Log levels == {| border="1" |- ! '''Problem Summary''' | What logs should be enabled before debugging a HRC Scheduler problem? |- ! '''Error Message''' | NA |- ! '''Possible C...)
Line 27: Line 27:
|-
|-
! '''Release'''
! '''Release'''
-
| Release 8.0(1)
+
| Release 7.0(1),Release 8.0, Release 8.5
|-
|-
! '''Associated CDETS #'''
! '''Associated CDETS #'''
Line 33: Line 33:
|-
|-
|}
|}
 +
 +
[[Category:Unified CCX, Release 7.0]]
 +
[[Category:Unified CCX, Release 8.0]]
 +
[[Category:Unified CCX, Release 8.5]]

Revision as of 12:32, 3 December 2010

Required Log levels

Problem Summary What logs should be enabled before debugging a HRC Scheduler problem?
Error Message NA
Possible Cause NA
Recommended Action While escalating issues to DE, please set the following log levels in the file SCH.ini. This is generally available under the folder where Historical Reporting Client is installed. On a windows system, [assuming HRC is installed on the C: drive] it would be 'C:\Program Files\Cisco UCCX Historical Reports\Scheduler'.

Log Levels while escalating issues to DE are

logLevel=5
 Note - Once a new log level is set, HRC Scheduler has to be restarted [by right clicking on the scheduler icon on the system tray] for the logs level to take effect. 

Logs should be collected from 'C:\Program Files\Cisco UCCX Historical Reports\Scheduler\'. Log level has to be reverted to level 1, for HRC Scheduler to perform optimally.

Release Release 7.0(1),Release 8.0, Release 8.5
Associated CDETS #

Rating: 0.0/5 (0 votes cast)

Personal tools