Unknown error occurred.
Agent on reporting server EDASERVE may have crashed.
Please investigate reporting server log.

ERROR:

Hi this is an attempt to group things that have caused the reporting agent to crash on the server.

1. Self referencing -INCLUDE eg

-* jph.fex
-INCLUDE JPH

Please can others add to this post so there is some sort of list we can work through

Regards

John

I have had agents crash when using functions (don't remember which ones) and I coded the variables in the wrong order.

Thanks jgelona: coding alphas instead of numerics can result in a reference to an unpredictable area of memory which results in corruption or a protection exception (bit like buffer overflow exploits favoured by hackers)!
This causes agent crashes.

Another one I remember is USE statements that refer to illegal or not existent directories.
So I would always do a check on any files explicitly coded to see if they are legal.

HAPPY WEEKEND EVERYONE!

Another one: HOLD FORMAT FOCUS INDEX XX where XX is not in the hold file. The following example crashes because the AS with ASNAMES ON changes the name in the held output.

TABLE FILE COMPANY_PERSON_ALL
SUM
WSA_DAY_SCHED_CODE AS 'Day Sched Code'
SCH_DAY_SCHED_NAME AS 'Day Sched Name'
BY CPA_EMP_NO AS 'Emp No'
IF CPA_SUBCONTRACTOR EQ 'Matchtech'
IF CPA_EMP_CAT_NAME EQ 'SUB CON'
WHERE WSA_DRF LE '&TODATE' AND WSA_DRT GE '&TODATE'
ON TABLE HOLD AS HR1067A FORMAT FOCUS INDEX CPA_EMP_NO
END
-EXIT

HAPPY MONDAY EVERYONE!

A missing quote in a define before conatenating 4 single quotes, without an end on a define.
DEFINE FILE ONE
MYFIELD/A20 = 'text || '''' || 'text';
TABLE FILE ONE

Maybe a bit far fetched, but how do you think I found it....

Got error: "Unknown error occurred. Agent on reporting server EDASERVE may have crashed. Please investigate reporting server log. "

I had a SQLOUT file from running a direct SQL query. In the TABLE FILE SQLOUT query, I had the wrong WebFOCUS syntax -- missing one "BY", for example

Wrong --
TABLE FILE SQLOUT
PRINT
FIELD1
BY
FIELD2
FIELD3
END

Corrected --
TABLE FILE SQLOUT
PRINT
FIELD1
BY
FIELD2
BY
FIELD3
END

Can you tell I'm a SQL coder?

This causes a crash:

DEFINE FILE CAR
TOTAL_SALES/D12.2=RETIAL_COST*SALES
END
TABLE FILE CAR
SUM TOTAL_SALES/D15.2
END

RETAIL_COST spelt as RETIAL_COST.
Remove the format in the TABLE and it errors correctly.

Another 2 hours of my life stolen!

ON MATCH UPDATE fieldname_not_in_the_master

Causes the crash so check what updates you are doing in a modify which will crash things.

-DEFAULTS OBJECT_TYPE='P

Whacks the server

quote:

DEFINE FILE CAR
TOTAL_SALES/D12.2=RETIAL_COST*SALES
END
TABLE FILE CAR
SUM TOTAL_SALES/D15.2
END

The above is fixed in 761 server.

The -DEFAULTS crash - that is suppose to produce an error msg. But a fix that was placed in 761 caused a crash while producing this specific error msg. Programming is fixing.

This is another bit of invalid syntax that is a server killer!

-? SET

don't even get me started on agent crashes.

OLAP crashes with COLUMN-TOTAL

With OLAP set on

ON TABLE COLUMN-TOTAL works fine but if you supply a fieldlist eg.

ON TABLE COLUMN-TOTAL GLS_AMOUNT GLS_QUANTITY

then it works fine on the first invocation but crashes the first time you ask the OLAP to sort on a column by clicking on it etc

---

Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2
Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo

As a general aside on this one.

Can we have something that helps us determine the cause from the initial agent crash screen?

1. I don't think the users mind if they get a screen dump rather than the neat agent crashed message - they still have not got their output they want.

2. The edaprint.log provides little further information. Here is a typical trace.

12/17/2007 16:57:34 request by edapmon to notify agent has crashed (tscomid=95)
12/17/2007 16:57:34 agent started (tscomid=96, pid=1412, svc=DEFAULT)
12/17/2007 16:57:34 request by t3rp1412 to notify agent is ready (tscomid=96)
12/17/2007 16:57:34 edapth: email sent to webfocusteam@fleet-support.co.uk

3. The only solution to attempt diagnosis is to rerun the code with a full trace on and look at diagnostics which where you have multi-use agents will tend to include the output of other users that used the same agent. You need to wait till everyone's gone home before trying things.

It should not be beyond the wit of man to produce some simple diagnostics.

A. I am assuming that an agent crash is an exception handler that catches events such as array index out of bounds, null pointers, zero divides etc. Currently it justs prints a message "Agent Crashed" but it could do so much more since the stack will probably be intact even after a failure.

B. First of all a stack traceback would be handy.

C. There should be a pointer maintained to a string descriptor of where wf is within its processing which is always maintained and printed after the stack trace.

Stage: Application of Styling Information

D. An additional pointer to the structure being processed should be maintained and an attempt to print something sensible such as 256 bytes either side of the pointer.

eg

TYPE=DATA,COLUMN=NEW_DRILLON,WHEN=NEW_DRILLON EQ 'J  M92',     FOCEXEC=R1294D2.fex(TOD='&TOD' WFFMT='&WFFMT'PROJECT_ID=&PROJECT_ID.QUOTEDSTRING ACTIVITY_SEQ=ACT_ACTIVITY_SEQ KEY=GLS_MPCCOM_ACCOUNTING_ID VOU<-----execution failed ------>CHER_TYPE=GLS_VOUCHER_TYPE VOUCHER_NO=GLS_VOUCHER_NO ROW_NO=GLS_ROW_NO AMOUNT=GLS_AMOUNT), $TYPE=DATA,COLUMN=NEW_DRILLON,WHEN=NEW_DRILLON EQ 'J  M93',
     FOCEXEC=R1294D2.fex(TOD='&TOD' WFFMT='&WFFMT'PROJECT_ID=&PROJECT_ID.QUOTEDSTRING ACTIVITY_SEQ=ACT_ACTIVITY_SEQ KEY=GLS_MPCCOM_ACCOUNTING_ID VOUCHER_TYPE=GLS_VOUCHER_TYPE VOUCHER_NO=GLS_VOUCHER_NO ROW_NO=GLS_ROW_NO AMOUNT=GLS_AMOUNT), $
TYPE=DATA,COLUMN=NEW_DRILLON,WHEN=NEW_DRILLON EQ 'MPLM50',
     FOCEXEC=R1294D3.fex(TOD='&TOD' WFFMT='&WFFMT' PROJECT_ID=&PROJECT_ID.QUOTEDSTRING ACTIVITY_SEQ=ACT_ACTIVITY_SEQ KEY=GLS_MPCCOM_ACCOUNTING_ID VOUCHER_TYPE=GLS_VOUCHER_TYPE VOUCHER_NO=GLS_VOUCHER_NO ROW_NO=GLS_ROW_NO AMOUNT=GLS_AMOUNT ), $

Which is a mess but gives you some idea of where the problem is.

From IBI's point of view this would make crash diagnosis so much more simple and would eventually save them money and less disgruntled customers.

Also as another poster points out OLAP does not like this

quote:

Ok, I figured out what was making the Agent crash...BY TOTAL HIGHEST