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. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at myibi@ibi.com and provide your corporate email address, company, and name.


Connect to myibi
Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED] Saving WF Reports to Excel 2007 Generates EDASERVE Error.

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] Saving WF Reports to Excel 2007 Generates EDASERVE Error.
 Login/Join
 
Member
posted
When trying to run reports to Excel 2007 output, the following message is generated. This happens for several reports I and several other users run.

"Unknown error occurred. Agent on reporting server EDASERVE may have crashed or request was halted by the operator. Please investigate reporting log."

The reporting log doesn't show anything out of the normal.

Other reports create the Excel 2007 output successfully.

Thank you.

This message has been edited. Last edited by: <Kathryn Henning>,


WebFOCUS 7.7
Windows, All Outputs
 
Posts: 4 | Registered: February 10, 2011Report This Post
Guru
posted Hide Post
Are you able to repro using CAR? If not, please post your original code.


-Rifaz

WebFOCUS 7.7.x and 8.x
 
Posts: 406 | Location: India | Registered: June 13, 2013Report This Post
Member
posted Hide Post
Hi Rifaz, I don't know what you're asking. repro - is that reproduce?
CAR - no idea what that means.


WebFOCUS 7.7
Windows, All Outputs
 
Posts: 4 | Registered: February 10, 2011Report This Post
Master
posted Hide Post
Rifaz does mean reproduce. And the CAR.FOC file is included with every distribution of FOCUS / WebFOCUS so that problems can be identified within a common environment.

I have to say that I'm shocked by the number of folks on here who haven't even taken the basic, WebFOCUS Reporting course - where you would be introduced to the CAR file as the very first step.

WebFOCUS is an expensive product to purchase and licence so any organization that has the product can certainly afford to send you to school for some basic training.


WebFOCUS 7.7.05 Windows, Linux, DB2, IBM Lotus Notes, Firebird, Lotus Symphony/OpenOffice. Outputs PDF, Excel 2007 (for OpenOffice integration), WP
 
Posts: 674 | Location: Guelph, Ontario, Canada ... In Focus since 1985 | Registered: September 28, 2010Report This Post
Master
posted Hide Post
You should use SET &ECHO='ALL'; and with -EXIT command find out which lines of code is causing this issue. In the final display PRINT/SUM, try using PRINT * END - to check if the issue is in final table file command.
 
Posts: 542 | Location: Dearborn, MI | Registered: June 03, 2009Report This Post
Gold member
posted Hide Post
Have you tried replacing EXL07 with EXL2K and rerunning it? I've found that EXL07 is very intolerant of special characters and you may get an error. EXL2K seems to handle invalid characters better.


WebFOCUS 7.7.05M, gen 144, Windows 2008 Server R2 64-bit, Tomcat 6.0.33, IIS 7.0, SQL Server, Excel 2013, PDF, HTML, FOCUS files.
 
Posts: 88 | Location: Seattle | Registered: March 29, 2007Report This Post
Gold member
posted Hide Post
I had a problem with some special characters in Excel but I was getting blown up in the Excel not webFocus but here is the results of that case. the solution worked so good luck woth checking these settings though.



Thank you for providing the requested files and information.
It's great that the suggestion from Focal Point resolved your issue.
There are two options possible in this case:
1. You can either stay with the solution offered in the forum,
that is using character encoding 137.
2. Or you can use a different character encoding - Windows-1252 -
which is a new standard for HTML 5, and should also work in your case.
The Windows-1252 char encoding is a superset of ISO 8859-1, and I am
including a link to the description of this encoding below:
http://en.wikipedia.org/wiki/Windows-1252
For this option you will need to set
Reporting Server Admin Console in Workspace -> NLS to
CODE_PAGE "1252 - Windows (Latin 1)"
Client Admin Console -> Configuration -> NLS Settings to
1252 - Western European
Tomcat Configuration for Java Options to
-Dfile.encoding=ISO8859_1


Duane

WebFOCUS 8.0.7
DS 8.0.7 AS 8.0.7
Windows
Output: Excel, HTML, PDF, AHTML,Mobile
In Focus 1982
 
Posts: 83 | Location: Princeton NJ | Registered: October 26, 2007Report This Post
Guru
posted Hide Post
You can better use EXL2K. EXL07 has problems with charachters and for larger files you can get memory issues with the server side compression of the excelfile.


Test: WF 8.2
Prod: WF 8.2
DB: Progress, REST, IBM UniVerse/UniData, SQLServer, MySQL, PostgreSQL, Oracle, Greenplum, Athena.
 
Posts: 454 | Location: Europe | Registered: February 05, 2007Report This Post
Gold member
posted Hide Post
There are various cases because of which this error appears. Better to try the report first in HTML. If that works then it might be huge data or special characters. In next step try to limit the records eg. 1000, 5000, 50000 etc.
If that works then check for special characters.
Sorry but no sure shot root cause and solution. It can be done step by step only.
SET &ECHO='ALL'; and with -EXIT Given by Ram Prasad is a very good option to debug.

Thanks,
Pravin Singh


WebFOCUS 7703
Windows, All Outputs
pravinsinghwebfocus.blogspot.com
 
Posts: 51 | Location: WebFOCUS 7.7.03 | Registered: June 19, 2014Report This Post
<Emily Duensing>
posted
George Patton,

Just FYI - our classes haven't used the CAR file in many, many years. Our need for more robust technical training examples exceeded the awesome simpleness of the CAR file long ago. Most of our classes now use a pretty robust SQL Server data mart which allows us to address many relational situations. And since a huge percentage of our user base access relational tables of some kind, this is a better approach. However, the CAR file lives on in every installation, so it can still be used for reproductions, and old car price jokes! Ha!
 
Report 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     [CLOSED] Saving WF Reports to Excel 2007 Generates EDASERVE Error.

Copyright © 1996-2020 Information Builders