Issue with comperhensive risk report
Updated: 21 May 2010 | 11 comments
Query Failed error come when comprehensive risk repot is run. It give below reasons.
This query could not be processed for one of the following reasons:
1. The database query timed out. Try reducing the number of filters, or increasing the SQL Server query timeout value.
2. An unexpected error occurred. Try running the query again by using default filter values.
3. String encoding was possibly not UTF-8, and may result from copying and pasting data instead of typing data. Try typing data in the input fields.
If i run comprehensive risk report with * in group box it work fine but if i select group name instead of * it gives query failed error. what could be possible reason.
Regrds
Hiren
discussion Filed Under:
Comments
Which version of SEP is installed ?
"Query Failed" displays when exporting log data after sorting the Monitor Log reports by specific columns within the Symantec Endpoint Protection Manager console.
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008080608471048
This problem is fixed in Symantec Endpoint Protection 11 Maintenance Release (MR) 4. For information on how to obtain the latest build of Symantec Endpoint Protection, read Obtaining an upgrade or update for Symantec Endpoint Protection.
http://service1.symantec.com/SUPPORT/ent-security....
If the implementation of SEP 11 MR4 is not currently possible, the below steps can be used as a workaround:
Sort by one of the other non-affected column headers in the Computer Status or Scan Log reports.
Click export to receive the comma-delimited file with the expected data.
Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)
Yup the Upgarde to MR4 MP2
Yup the Upgarde to MR4 MP2 should work for you
It is already MR4 MP2
I said i am facign problem with Comprehensive RISK REPORT and not with logs.
please see the attcahed screen shot
please see the attcahed screen shot it will give u better insght of what i am talking
may I ask if only happened on
may I ask if only happened on the risk comprehensive report? did you tried to generate a report using another type?
:-)
may I ask if only happened on
may I ask if only happened on the risk comprehensive report? did you tried to generate a report using another type?
:-)
Yes only with comprehensive report
Yes this happens only with comprehensive repots all other report works fine.
i assume it's SQL DB. have
i assume it's SQL DB.
have you increased the SQL connection timeout value?
Pete
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
no
can u pls tell me how to do that?
check this link and let know
check this link and let know if it fixes the issue
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/9afb5e151ee9feff8825713300765438?OpenDocument
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
Hi Hiren, You will alos need
Hi Hiren,
You will alos need to install the the fast CGI along with this.
Would you like to reply?
Login or Register to post your comment.