Troubleshooting Guide for Cisco Unity Release 8.x (With Microsoft Exchange)
Troubleshooting Reports in Cisco Unity 8.x
Downloads: This chapterpdf (PDF - 79.0KB) The complete bookPDF (PDF - 4.85MB) | Feedback

Troubleshooting Reports in Cisco Unity 8.x

Table Of Contents

Troubleshooting Reports in Cisco Unity 8.x

About Problems With Reports in Cisco Unity 8.x

A Requested Report Was Not Generated

Report Notification Not Generated


Troubleshooting Reports in Cisco Unity 8.x


About Problems With Reports in Cisco Unity 8.x

Problems and troubleshooting procedures specific to reports are described in this chapter.

A Requested Report Was Not Generated

To Research a Report


Step 1 In Internet Explorer, browse to http://<Cisco Unity server name>/Status or double-click the desktop shortcut to the Status Monitor.

Step 2 In the Status Monitor, click the Report Queue Status icon.

Step 3 On the Report Queue Status page, locate the report you are waiting for in the list of submitted reports. The wait time for a queued report will vary depending on the size of the database and on how busy the system is.

Step 4 If wait time for the report seems excessive, do one or more of the following:

Cancel the queued report and request it again at a time when the system is not as busy.

Cancel the queued report, refine the selection criteria, and then submit the report again.

On the Windows Start menu, click Programs > Administrative Tools > Services. Locate the AVRepDirSvrSvc service. If reports are not working properly or are locked, restarting this service will remove the locked state and the reports process will be restarted. Note that some queued reports may be lost due to restarting the service.

Step 5 If a requested report is missing from the Report Queue Status page because the Cisco Unity server or the AvRepDirSvrSvc service was restarted, request the report again.

Step 6 If the requested reports are still missing from the Report Queue Status, on the Windows Start menu, click Programs > Cisco Unity > Unity Diagnostic Tool.

Step 7 In the Cisco Unity Diagnostic Viewer, click the Configure Micro Traces icon.

Step 8 Check the check boxes for the following micro traces:

ReportCrunch

ReportExtractor

ReportPostprocess

ReportPreprocess

ReportPump

ReportRunrep

Step 9 In the Cisco Unity Diagnostic Viewer, click Start New Log Files.

Step 10 Request the reports again at a time when the system is not busy. Wait for a time equal to the wait time previously experienced. If the reports print successfully, skip to Step 15. If the reports do not print, continue with Step 11.

Step 11 To view the log files, click Process > AvCsMgr, and then click the Current log file. The selected log file is formatted and displayed in the right pane.

Step 12 To export or save a copy of the log file, click Action > Export List.

Step 13 Name the file and save it to a location of your choice in .txt or .csv format.

Step 14 If the requested reports still are not produced, and you are unable to determine the cause of the problem from the diagnostic logs, contact the Cisco Technical Assistance Center (TAC).

Step 15 To turn off the traces set in Step 8, in the Cisco Unity Diagnostic Viewer, click Reset to Default Traces.

Step 16 In the Reset to Default Traces wizard, check the Reset to Default Traces check box, and click Finish.


Report Notification Not Generated

The Installer account has no mailbox. Therefore, if reports are requested when using the Installer account, no notification will be received when a report is complete. If you are using the Installer account (or another account that has no mailbox) to request reports, you can view the completed reports in the \CommServer\Reports directory.