Hello Focal Pointers,

we've got the following problem with one of our reports (the report gets called with the same input data and parameters):
- in 29 out of 30 times, the report runs fine
- in the 30th time, the report gives an EDASERVE error
- in the 31th time, the report runs fine again

The numbers are varying, but it makes it very hard to reproduce the problem.

We can't reproduce the problem in a simple TABLE FILE CAR fex, so it makes debugging a lot harder for us.

We tried to switch traces on, which gave the EDASERVE error a lot more often, so the traces were spammed with other EDASERVE errors.

Some more details about the report:
- using several INCLUDEs
- using a lot of variables
- using a lot of labels, loops and GOTOs
- reading large .foc files (around 6 GBs per file)
- output format is HTML
- there is enough free space on the file system


Does anyone know, how we can further debug this EDASERVE error?


Platform:
- Windows 2003 VMWare Server
- WebFOCUS 7.6.11
- Self Service application, no MRE installed

Thanks in advance,
Tobias

This message has been edited. Last edited by: Kerry,

Look carefully for duplicate dialog manager labels this could cause many problems that are not obvious and very difficult to debug.

Although this adds to the fexes, I would add in log file functionality.

FILEDEF a file outside the temp directory, in APPEND mode, and write where the execution is up to, to the file. This way you can at least determine if the crash is at the same place, or varies, and what code is potentially involved with the crash.

The other thing is what are the settings for Agent Refresh on the WebFOCUS server ?, are they set to one.

Hi,

thanks for your suggestions!

I'll try to add a log functionality and check the GOTO labels.
agent_refresh is on 100

Greetings,
Tobi

You may want to try to lower the agent_refresh first. Set it to 10 and see what happens. It may very well be that something is corrupting the agent's environment and it breaks the agent after so many attempts. If you set agent_refresh to 10 then you refresh the agent's environment before it gets to the corrupting point, tehreby effectively preventing crashes.

Hi,

thanks for the suggestion. I've changed the setting and I'll monitor if the problem still occurs.

I managed to save the generated .html file when the error occured with -SET &ECHO = ALL;

Looks like nearly the whole FEX ran fine, except one last -HTMLFORM statement.

The title bar of the generated HTML document sais:
"WebFOCUS Message[0]: NO_WEBERROR"

If the problem still occurs, I'll upload the HTML file to IBI.

Thanks again for your suggestions,
Tobias


[edit on 2011/09/21]
We solved the issue. We had a HEADALIGN=BODY in our HEADING / FOOTING which caused the crash. The issue is fixed in 7.6.12.

This message has been edited. Last edited by: tgall,