BUG Reports adhoc tree menu failed to load

Discussion created by RSA Admin

on Sep 11, 2008
Latest reply on Sep 11, 2008 by RSA Admin

Like • Show 0 Likes0
Comment • 3

HI, I have attach the image of the situation we are dealing.

Symptons:

1. We COULDN'T connect to enVision ES 2560 via web interface, remote desktop or directly in the envision (no video), we have to make a forced shutdown.

2. Then after booting we went to Reports module and found this message on this option reports > ad hoc reports an error message

Note: We were working on some custom reports based on an adhoc report.

We have put a case in support, and when they answer we will post their solution, but in the mean time, if someone has have this situation we will appreciate your help.

Message Edited by soporteIntelector on09-11-200802:23 PM

Attachments

envision-reports-adhoc.JPG76.8 KB

Outcomes

RSA Admin

Sep 11, 2008 8:47 PM

Hello soporteIntgelector,

I have seen this before and it could be a damage jar file or damage reports xml files/link. On another case, a report that had illegal characters as their report naming convention. You can zip up the nic\3xxx\sitename\etc\reports\custom folder and forward them to your support contact and have them test out those reports for you. Or have them check the integraty of the privatei.jar file or one of the relate files.

Also, make sure that the NIC DB Reporter Server is running.

Actions

RSA Admin

Sep 15, 2008 1:29 PM

The solution was made by RSA support, what they did in our case was look into the reports folder of each device type (.xml files with the names of the reports). And rename the "bad" reports files to a .bad extension and rename the .bck (backup files of the original report) to .xml

So they name one and try if that solves it, case by case. Then restart de NIC webserver service and it was done.

Actions

ericlevin Sep 1, 2009 10:15 AM

We ran into this as well after the VAM and Signature Update from 8/31/2009. We had to delete a couple custom VAM reports and restart the NIC Web Server service to get around this error.

Actions

3 Replies

RSA Admin Sep 11, 2008 8:47 PM
Hello soporteIntgelector,

I have seen this before and it could be a damage jar file or damage reports xml files/link. On another case, a report that had illegal characters as their report naming convention. You can zip up the nic\3xxx\sitename\etc\reports\custom folder and forward them to your support contact and have them test out those reports for you. Or have them check the integraty of the privatei.jar file or one of the relate files.

Also, make sure that the NIC DB Reporter Server is running.
Like • Show 0 Likes0
Actions
RSA Admin Sep 15, 2008 1:29 PM
The solution was made by RSA support, what they did in our case was look into the reports folder of each device type (.xml files with the names of the reports). And rename the "bad" reports files to a .bad extension and rename the .bck (backup files of the original report) to .xml

So they name one and try if that solves it, case by case. Then restart de NIC webserver service and it was done.
Like • Show 0 Likes0
Actions
ericlevin Sep 1, 2009 10:15 AM
We ran into this as well after the VAM and Signature Update from 8/31/2009. We had to delete a couple custom VAM reports and restart the NIC Web Server service to get around this error.
Like • Show 0 Likes0
Actions

BUG Reports adhoc tree menu failed to load

Attachments

Outcomes

Related Content

Recommended Content