Unity Connection reporting No 2021

[Michelle Awtrey]

Trying to run a report on a mailbox navigating to Cisco Unity Connection Serviceability. Tools>Reports>User Message Activity. For the date range 2021 is not there.  I have attached a Snipping capture. 

[Joe LaRosa]

While I don't have the TAC Case or BugID handy, TAC was engaged yesterday for this exact issue and they reported it is indeed a bug that affects ALL versions of CUC. There's nothing that can be done until a patch is released, and there was no ETA.

[Chris Pope]

I am seeing this issue also on v12.5(SU 2).  Did TAC give you a BUG ID?  Is it fixed in SU 3?

[Joe LaRosa]

Here's the bugID, also with very helpful workarounds:

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvw93402

Considering this has gotten 21 cases and listed as Severe, I doubt we'll have to wait for SU's. This will probably be fixed via cop file.

[Joe LaRosa]

This is the command I had to run from my Unity Connection Subscriber (not entirely sure why it doesn't work on the Pub):

run cuc dbquery unitydirdb select * from UnityRptDb:vw_CallHandlerTraffic where CallHandlerName = 'Your Call Handler Display Name' AND StartDateTime BETWEEN '2020-12-28 00:00:00.0' AND '2021-01-04 00:00:00.0' ORDER BY CallHandlerName, StartDateTime

[mmemchout]

HI,

How we can do Export to PDF or CSV file please??

[Joe LaRosa]

Copy your putty session and then paste into a text editor, such as Notepad++. Once in Notepad++, delete all text except the output of your CLI command, and also delete the dashes line under the headers. Once you ONLY have headers and result rows, copy this text and paste into Excel using the "Text Import Wizard" (click the down arrow under the past icon and select "Use Text Import Wizard"). Once in Excel you can easily save as CSV or PDF.

[jcwhiteside]

You can add us to the list of impacted users, which is basically anyone running CUCXN.  We haven't opened a ticket, since we know this is a bug.  Hopefully Cisco understands this severely impacts a lot more users than just who report it.

The provided workarounds in the bug ID are definitely not sufficient.  I've spent a little while playing with them and there's all sorts of output, for what I'm guessing are internal database references, that make it really impossible to interpret the results in a meaningful way.  (At least in the same way we might use the normal reporting function.)  It's also not entirely clear what variables one must put in, or massage, to achieve the outputs you want.  I've spent a couple hours now trying to figure out how to answer very basic questions and am no closer to that answer from when I started.

Also, please give us a COP.  I cannot begin to explain how much I do not want to process a major upgrade to get basic reporting functions operational.