Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] This report is invalid because the data retrieval has been killed or

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] This report is invalid because the data retrieval has been killed or
 Login/Join
 
Wep5622
Virtuoso
posted
I get above error when I output my report as PDF, but not if I output it as HTML or EXL2K - go figure...

Any idea how to figure out what's causing this issue?

The report isn't particularly big, it's probably caused by something in the (rather gimmicky) layout. Removing the styling didn't help though.

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


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 2010Report This Post
Francis Mariani
Expert
posted Hide Post
Perhaps there's another message accompanying this one, view source in the HTML version and look for other "(FOC" errors...


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
Wep5622
Virtuoso
posted Hide Post
I double and triple-checked - no errors in the HTML source.

The problem only snuck in after optimizing some of the code, but I don't remember what I changed exactly. Unfortunately, at that point I hadn't added it to our version control software yet, so I can't trace back what change broke it :/

It's probably not the amount of data (TABLE=76 LINES=60), but much more likely something in the way the data is laid out (some MacGuyvering going on in this report).

I'll try disabling parts of the code some more to see if I can find the culprit, but it only occurring with PDF output limits my options a bit...


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 2010Report This Post
Wep5622
Virtuoso
posted Hide Post
I did find some concatenated fields that didn't fit in the result field (no error or warning), which possibly caused some memory allocation errors and a subsequent crash of the involved application. Fixing that got me a bit further.

However, now I got stuck on a field that's used in the report straight from the data-source, with no alterations. It's an A1950V type field, and it's crashing the PDF's... There's a style for that column to wrap it in 17cm, but enabling/disabling that isn't helping (in fact, enabling that style with the field disabled causes a crash as well).

It would seem the code for generating PDFs in WebFOCUS is rather fragile.


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 2010Report This Post
Wep5622
Virtuoso
posted Hide Post
Wrapping NOPRINT fields and content going over the page boundaries seem to cause problems too.

It's working now, but that required baby steps to get from one minimalist working state to the next. Holy cow!


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 2010Report This Post
ABT
Master
posted Hide Post
Admin killed your agent.

- ABT


------------------------------------
WF Environment:
------------------------------------
Server/Client, ReportCaster, Dev Studio: 7.6.11
Resource Analyzer, Resource Governor, Library, Maintain, InfoAssist
OS: Windows Server 2003
Application/Web Server: Tomcat 5.5.25
Java: JDK 1.6.0_03
Authentication: LDAP, MRREALM Driver
Output: PDF, EXL2K, HTM

------------------------------------
Databases:
------------------------------------
Oracle 10g
DB2 (AS/400)
MSSQL Server 2005
Access/FoxPro
 
Posts: 561 | Registered: February 03, 2010Report This Post
Mager
Member
posted Hide Post
When it suddently started happening to us, we realized that it occurs in PDF when the report is too wide. It used to yield page 1.2 etc. Now we get the server error. Sometimes SET ERROROUT=OFF helps. Most of the time we WRAP the longer txt fields in the output. That takes care of it.
 
Posts: 2 | Location: Washington | Registered: June 11, 2008Report This Post
Wep5622
Virtuoso
posted Hide Post
quote:
Originally posted by ABT:
Admin killed your agent.
- ABT


I did no such thing! Wink

This is a development box with a local WF installation, so there are no admins secretly killing my reports in the background. It is possible that Windoze killed the process for some reason, but it seems more likely that the process just crashed. There wasn't enough load on the system to warrant the OS shooting processes down (if Windoze can even do that).

After all, the content was going over the page edge, was trying to wrap non-printed fields and did assign more data to some fields than would fit in them. An access violation or a segmentation fault or something of the kind seems quite likely in such scenario's. That does indicate a bug in WF though, even though you need to write faulty code to trigger it.


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 2010Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] This report is invalid because the data retrieval has been killed or

Copyright © 1996-2020 Information Builders