The report could not be queued - no report will be generated
Trying to run reports on call handler traffic. Whenever I click on run, I get "The report could not be queued - no report will be generated". I got a suggestion from TAC for making changes in DCOM and in the registry listed below:
GPTCSL Remedy Ticket 227846
Issue: After clicking the Run button for the Call Handler Report the user will receive the following screen pop.
In addition, the Application Log will have 4 errors listed.. The errors are 20017, 20018, 20019 and 10001 in sequence. They will look similar to:
12/6/01,1:06:21 PM,AvRepDir_MC,Error,REPDIR ,10001,N/A,XPRESSIONS471,REPDIR FATAL ERROR FILE h:\CommSvr\Sources\ReportDirector\AvRepDirSvr\AvRepDir.cpp LINE 1543 VALUE 0x8004020D
12/6/01,1:06:21 PM,AvRepMgr_MC,Error,REPMGR ,20019,N/A,XPRESSIONS471,REPMGR GETPARMS FAILED REPORT NAME HRESULT 0x8004020B
Re: The report could not be queued - no report will be generated
I had this same problem with an AD120 box, which is the NEC digital OEM version of Unity. In certain configurations this report fails, (i.e. a standalone box versus true unified messaging versus NT versus 2000). NTAC emailed me a patch that took care of the problem. Cisco has to know of the problem and the patch that NEC has. I cannot imagine NEC wrote the code for the patch all on their on. The patch probably would not work on anything other than AD120 22.214.171.124.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.