I am getting an "An unexpected error occurred in Report Processing" error
when attempting to navigate to the next page in a report. The first page of
the report comes up in the browser OK but produces the error when clicking on
the "next" arrow. The main report uses a subreport that accepts two
parameters, one of which can be null. The subreport is used to display
subtotals at the 1st and 2nd grouping level. Each report runs fine
standalone and everything works as expected in the designer. The number of
rows returned by the stored procedure is small (29). I have reviewed
recommended log files but nothing stands out. Is there more I can do to
troubleshoot this problem. TIA
DIt apprears that the subreport is the problem as paging works if the
subreport is removed. The subreport has 23 columns and is placed into a
merged cell in the main report, also 23 columns. Are there limitations on
the use of the subreport?
dp
"dp" wrote:
> I am getting an "An unexpected error occurred in Report Processing" error
> when attempting to navigate to the next page in a report. The first page of
> the report comes up in the browser OK but produces the error when clicking on
> the "next" arrow. The main report uses a subreport that accepts two
> parameters, one of which can be null. The subreport is used to display
> subtotals at the 1st and 2nd grouping level. Each report runs fine
> standalone and everything works as expected in the designer. The number of
> rows returned by the stored procedure is small (29). I have reviewed
> recommended log files but nothing stands out. Is there more I can do to
> troubleshoot this problem. TIA
> D
Friday, March 9, 2012
Paging
Labels:
attempting,
database,
error,
microsoft,
mysql,
navigate,
occurred,
oracle,
page,
paging,
processing,
report,
server,
sql,
unexpected
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment