Hi,
I am getting following error while executing reports in Managed Reporting Environment.

An HTTP 500 error has been returned when attempting to communicate with the WebFOCUS web components. The application server log contains information on why this error has occurred. Contact your WebFOCUS Administrator or Information Builders Customer Support Services for further assistance.

I checked various many blogs for following error. I tried the suggested method. I deleted personal.xml file. But, it doesn't work out. Can somebody please suggest anything i can do to get it working.

Thanks,
Chirag

Try to locate the servlet log file. It may contain some more information about what is going on. If you're using tomcat, it is located in tomcat's program directory, subdir logs.
The error can be in any one of the files, most likely one is the stderr file.
If something like this happens to me, first thing I do is to stop tomcat, delete all files in the logs directory, restart tomcat and reproduce the problem. That way you will have a fresh set of files to work with.

Hope this helps ...

Check the Tomcat log to see what errors you are getting.

I have tried HTTP 500 help. I deleted personal.xml file and checked again. But with no luck.
JG, I am using Websphere application server and IHS server.

Thanks,
Chirag

You will have to give us the code and the servlet trace.

I assume you can successfully run the same code as applications from ds for instance.

For issues like this, I would open a case with Technical Support. That's what they are there for.

Chirag,

You still need to look at the application server log because that is where the
error detail will give you a probable cause.

Look at the error message.

"The application server log contains information on why this error has occurred.""

This error occurs for many different reasons, usually a coding issue. I would use the process of elimination. If it's a long program with many HOLD files before the final report, I'd stick a -EXIT after the first END staement. The the program works, move the -EXIT to after the next END, until you arrive to the piece of code that generates the error. Simplify that piece of code, then keep adding the lines back until the error occurs - you may then see what the problem is. On the other hand, could it be a timeout issue, the program running too long?