We have several reports generated as Merged Compound PDFs. In one example, the report includes a report for Customer information, a report for account charges, a report for inventory, and yet a couple more reports. The main report can be run across multiple businesses and everything is merged upon a couple fields that each of the sub reports share.

In 7.6.5, we went through these reports and ensured that each and every subreport contained results that were consistent with the other subreports. This was done to avoid issues with merges failing when one of subreports came up empty (E.g. The business had inventory but no account charges).

Everything worked fine at that point. We've since upgraded to 7.6.9 which, as I understood, would eliminate the problems with merging empty reports. However, these reports now crash with the error message of

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

The agent stats don't display an actual error message.

At this point, we have not changed the SQL stored procedures or the main reporting files. We have created a couple testing reports to try out updates in an effort to get this fixed. I'll post code from the simplified testing report (containing only one subreport).

Note that, if we set MERGE=OFF, the report does run...it's just unusable. As soon as MERGE=ON, it fails.

Did something change with 7.6.9? Is it more picky about code? If so, what are we missing/doing wrong? It's entirely possible I'm overlooking something.

Any help would be greatly appreciated.

*****************
** Main Report **
*****************
SET HTMLARCHIVE=ON
COMPOUND LAYOUT
UNITS=IN, $
SECTION=section1, LAYOUT=ON, METADATA='0.5^0.5^0.5^0.5', MERGE=ON, ORIENTATION=LANDSCAPE, PAGESIZE=Letter, $
PAGELAYOUT=1, NAME='Page layout 1', text='Page layout 1', TOC-LEVEL=1, BOTTOMMARGIN=0.5, TOPMARGIN=0.5, METADATA='BOTTOMMARGIN=0.5,TOPMARGIN=0.5,LEFTMARGIN=0,RIGHTMARGIN=0,', $
COMPONENT='report1', TEXT='report1', TOC-LEVEL=2, POSITION=(0.521 0.521), DIMENSION=(* *), METADATA='Z-INDEX: 100; POSITION: absolute; WIDTH: 9.981in; HEIGHT: 1.04in; OVERFLOW: auto; TOP: 0.521in; LEFT: 0.521in', $
END
SET COMPONENT='report1'
-INCLUDE app/receivabledetailsinglereport_customerprofile1
END
COMPOUND END

*****************
** Sub Report **
*****************

DEFINE FILE REPORT_RECEIVABLEDETAILONEREPORT_BUSINESSDETAIL
'City, State, ZIP:'/A65 = CITYSTATEZIP;
END
TABLE FILE REPORT_RECEIVABLEDETAILONEREPORT_BUSINESSDETAIL
PRINT
'REPORT_RECEIVABLEDETAILONEREPORT_BUSINESSDETAIL.ANSWERSET1.BUSINESSNAME'
AS 'Name:' OVER
'REPORT_RECEIVABLEDETAILONEREPORT_BUSINESSDETAIL.ANSWERSET1.BUSINESSNUMBER'
AS 'Dealer Id:' OVER
'REPORT_RECEIVABLEDETAILONEREPORT_BUSINESSDETAIL.ANSWERSET1.ADDRESSLINE1'
AS 'Address Line 1:' OVER
'REPORT_RECEIVABLEDETAILONEREPORT_BUSINESSDETAIL.ANSWERSET1.ADDRESSLINE2'
AS 'Address Line 2:' OVER
'REPORT_RECEIVABLEDETAILONEREPORT_BUSINESSDETAIL.ANSWERSET1.City, State, ZIP:' OVER
'REPORT_RECEIVABLEDETAILONEREPORT_BUSINESSDETAIL.ANSWERSET1.PHONE'
AS 'Phone:' OVER
'REPORT_RECEIVABLEDETAILONEREPORT_BUSINESSDETAIL.ANSWERSET1.FAX'
AS 'Fax:'
BY 'REPORT_RECEIVABLEDETAILONEREPORT_BUSINESSDETAIL.ANSWERSET1.MERGEBYFIELD' NOPRINT
BY 'REPORT_RECEIVABLEDETAILONEREPORT_BUSINESSDETAIL.ANSWERSET1.BUSINESSDISPLAYTEXT' NOPRINT
HEADING
"Customer Profile"
WHERE ( @FILTERTYPE EQ &FilterType ) AND ( @FILTERID EQ '&FilterId' ) AND ( @BUSINESSID EQ '&BusinessId' ) AND ( @DELINQUENCYFLAG EQ &DelinquencyFlag ) AND ( @ACCOUNTMANAGERID EQ '&AccountManagerId' );
ON TABLE SET PAGE-NUM OFF
ON TABLE NOTOTAL
ON TABLE PCHOLD FORMAT PDF
ON TABLE SET HTMLCSS ON
ON TABLE SET STYLE *
UNITS=IN,
PAGESIZE='Letter',
LEFTMARGIN=0.250000,
RIGHTMARGIN=0.250000,
TOPMARGIN=0.055556,
BOTTOMMARGIN=0.055556,
SQUEEZE=ON,
ORIENTATION=LANDSCAPE,
$
TYPE=REPORT,
FONT='ARIAL',
SIZE=12,
COLOR='BLACK',
BACKCOLOR='NONE',
STYLE=NORMAL,
$
TYPE=DATA,
SIZE=7,
BACKCOLOR=( 'WHITE' RGB(235 235 235) ),
$
TYPE=DATA,
COLUMN=N3,
JUSTIFY=LEFT,
$
TYPE=TITLE,
BORDER-TOP=LIGHT,
BORDER-BOTTOM=LIGHT,
BORDER-LEFT=LIGHT,
BORDER-RIGHT=LIGHT,
BORDER-TOP-STYLE=RIDGE,
BORDER-BOTTOM-STYLE=RIDGE,
BORDER-LEFT-STYLE=RIDGE,
BORDER-RIGHT-STYLE=RIDGE,
BORDER-TOP-COLOR='BLACK',
BORDER-BOTTOM-COLOR='BLACK',
BORDER-LEFT-COLOR='BLACK',
BORDER-RIGHT-COLOR='BLACK',
SIZE=7,
COLOR='BLACK',
BACKCOLOR='LIGHT GRAY',
STYLE=BOLD,
$
TYPE=TABHEADING,
BORDER-TOP=LIGHT,
BORDER-BOTTOM=LIGHT,
BORDER-LEFT=LIGHT,
BORDER-RIGHT=LIGHT,
BORDER-TOP-STYLE=RIDGE,
BORDER-BOTTOM-STYLE=RIDGE,
BORDER-LEFT-STYLE=RIDGE,
BORDER-RIGHT-STYLE=RIDGE,
BORDER-TOP-COLOR='BLACK',
BORDER-BOTTOM-COLOR='BLACK',
BORDER-LEFT-COLOR='BLACK',
BORDER-RIGHT-COLOR='BLACK',
STYLE=BOLD,
JUSTIFY=CENTER,
$
TYPE=TABFOOTING,
SIZE=8,
STYLE=BOLD,
$
TYPE=HEADING,
BORDER-TOP=LIGHT,
BORDER-BOTTOM=LIGHT,
BORDER-LEFT=LIGHT,
BORDER-RIGHT=LIGHT,
BORDER-TOP-STYLE=RIDGE,
BORDER-BOTTOM-STYLE=RIDGE,
BORDER-LEFT-STYLE=RIDGE,
BORDER-RIGHT-STYLE=RIDGE,
BORDER-TOP-COLOR='BLACK',
BORDER-BOTTOM-COLOR='BLACK',
BORDER-LEFT-COLOR='BLACK',
BORDER-RIGHT-COLOR='BLACK',
SIZE=9,
COLOR=RGB(105 105 105),
BACKCOLOR='WHITE',
STYLE=BOLD+ITALIC,
JUSTIFY=CENTER,
$
TYPE=HEADING,
LINE=1,
OBJECT=TEXT,
ITEM=1,
COLOR='BLACK',
STYLE=BOLD,
$
TYPE=FOOTING,
SIZE=9,
COLOR=RGB(105 105 105),
BACKCOLOR='WHITE',
STYLE=BOLD+ITALIC,
$
TYPE=SUBHEAD,
BORDER-TOP=LIGHT,
BORDER-BOTTOM=LIGHT,
BORDER-LEFT=LIGHT,
BORDER-RIGHT=LIGHT,
BORDER-TOP-STYLE=RIDGE,
BORDER-BOTTOM-STYLE=RIDGE,
BORDER-LEFT-STYLE=RIDGE,
BORDER-RIGHT-STYLE=RIDGE,
BORDER-TOP-COLOR='BLACK',
BORDER-BOTTOM-COLOR='BLACK',
BORDER-LEFT-COLOR='BLACK',
BORDER-RIGHT-COLOR='BLACK',
SIZE=7,
BACKCOLOR=RGB(225 225 225),
STYLE=BOLD+ITALIC,
$
TYPE=SUBFOOT,
BORDER-TOP=LIGHT,
BORDER-TOP-STYLE=RIDGE,
BORDER-TOP-COLOR='BLACK',
SIZE=8,
STYLE=BOLD,
$
TYPE=SUBTOTAL,
BORDER-TOP=LIGHT,
BORDER-TOP-STYLE=RIDGE,
BORDER-TOP-COLOR='BLACK',
SIZE=8,
STYLE=BOLD,
$
TYPE=ACROSSVALUE,
SIZE=8,
STYLE=BOLD,
$
TYPE=ACROSSTITLE,
SIZE=8,
STYLE=BOLD,
$
TYPE=GRANDTOTAL,
BORDER-TOP=LIGHT,
BORDER-TOP-STYLE=RIDGE,
BORDER-TOP-COLOR='BLACK',
SIZE=8,
STYLE=BOLD,
$
ENDSTYLE
END

BG,

Your best course of action for this would be to contact CSS and raise a case on it.

T

Although it should not error, MERGE=ON with one report ?

Waz, you're right. It doesn't make any real sense to use MERGE=ON for just one report. In production, there are several other reports included. Using only one report was my attempt to simply things as much as possible. It at least eliminated problems that may have existed in the other subreports.