Hi,
I am facing an issue while executing the focexec procedure for certain conditions. The exception is

Task error:Pcb2.: java.io.EOFException

I could not find out the root cause for this issue. Can anyone state what is the problem and solution for this kind of exception?

Thanks,
Suji.

Try running the focexec from Dev Studio or a browser to see if you get more/better error messages.

Also, please go to your profile and update your signature so that it includes your product suite, releases, and platforms.

We've faced that many times in older versions. The code may run just fine everywhere but from Report Caster, which uses a different code set, I believe. I know this sounds silly, but in one instance what fixed it was putting a space between the double quote ending a heading and the character just before it. Other times just deleted and added back a row. The really bad issue for us was a job had been running forever and then boom, java socket exception. The administrator always insisted it had to be the code, which it wasn't. We've had the issue recently on a job that gets the exception, queue it in again and it runs fine. I empathise with you completely on this one.

I'm not sure what release you are on...

...but back on 5.2.8 we've seen this error many times when someone makes a change to a config file or adds a data connection and restarts the services or kills a job by accident.

We cannot try in Dev studio since we use standalone reports that run in browser. Is there any standard solution for this problem? We cannot queue the requests manually since that action is done independent of our control.

Thanks,
Suji.

Then run from a browser or an adhoc window. You need to test in another environment to verify that the program does work before you blame RC for the problem.

Do you mean in the managed reporting environment? If so do you edit the code? Are you allowed to run other than with Report Caster, such as in deferred mode or 'live' mode?

We currently have an open issue similar to this where we occasionally we getting these types of failures. This is on release 7.6.1.

What it came down to was having 2 ReportCaster jobs scheduled to run at the same exact time (i.e. 11:05:00). Sometimes they would both work. Other times 1 would fail. Sometimes both would fail.

We finally did get a patch to address the issue. It did work. However it has since caused us another problem that has forced us to remove the patch.

By this time we had identifed all schedules that were doubling up on the execution time. So, removing the patch is not that big a deal.

Bryan Klimek
Mayo Clinic

Hi,
The same code is working fine in the browser "online".

Thanks,
Suji.

I would suggest putting

-SET &ECHO = ALL;

in you fex and run it in reportcaster with full notification of error to you. Sometimes this reveals what it doesn't like, otherwise, change some little thing and see what happens then.

Good Luck