Capturing Dashboards error messages

[Former Member]

Hi all,

Quite new to BO. I'm trying to capture any error message (not just the error code or error type, but the entire error message verbatim) Dashboards may throw while it's being run. Any advice/tip would be appreciated.

Thanks,

Will

[Former Member]

Hi William,

Firstly for this error message confirm the universe you are using .

Try re-publishing the universe to the repository and test the dashboard.

For tracing the error logs you could use a fiddler tool. This tool is a tracing tool which captures http request.

You would get a free version of  this tool on fiddler2.com.

Apart from this as Niraj suggested, you could capture the dashbpard procesing server logs.

Following is the note which would provide you the details of it.

1804748 - How to enable tracing on Dashboards server.

The captured dashboard processing server logs you would get in the following location.

BO installation folder\ logging.

Let me know if the above information was helpful.

Regards,

Noopur

[Former Member]

Hi William,

Error messages related with dashboards can be captured in the bo server trace files. By default bo server traces are generated in the logging directory.

You can set tracing on dashboards processing and/or cache services to capture the errors and to do a root cause analysis for the error.

Regards,

Niraj

[Former Member]

Hi,

What Kind of Error your are getting,please share the screenshot \

Regards

NK

[Former Member]

Hi NK,

One example of an error message is

"Request processing failed. (XLS 000009)

Request processing failed. (XLS 000009) []
<com.businessobjects.dsl.commons.exception.NestedException; Failed to execute:

  SELECT .........."

Or any similar error messages.

I would like to capture those error messages. Maybe some sort of trace log or event log?

Cheers,

Will

[former_member182541]

Hi,

What is your source ?

what is your dashboard version ?

If your source is Bex query then check the query in RSRT or Check the universe whether its working fine, may be create a sample webi report and test it.

--SumanT