Posted 26 June 2019, 5:49 pm EST
We’ve been using AR to generate a pdf for the last year with very few errors.
We recently deployed a new version and now we are seeing a drastic increase in the number of errors while trying to generate the PDF report. The stack trace is as follows.
at GrapeCity.ActiveReports.Document.PageDocument.Render(IRenderingExtension renderingExtension, StreamProvider streams, NameValueCollection settings, Boolean forceDataRefresh, Boolean forceParameterDataRefresh)
at GrapeCity.ActiveReports.Document.PageDocument.Render(IRenderingExtension renderingExtension, StreamProvider streams)...
and the Error is
An unexpected error occurred. Additional information: ‘Parameter is not valid.’ inner exception level 1: Parameter is not valid.
We did some minor work on the reports for this release but after reviewing that code I don’t believe those changes are to blame.
The other things that changed when we released.
-We added another server instance to our azure API so now we are running 2 servers instead of 1 server.
- we scaled up from Azure S3 to Azure P2V2 servers (Better processors)
Our usage statistics for the functionality that generates the PDF’s has stayed pretty constant across the two releases. But the error numbers are pretty stark.
Before release: 32 errors over about 10 months of usage
After release: 1900 errors over 3 weeks of usage
This error occurs on about 15% of the calls to generate a pdf.
The only related tickets I could find in the forums pertained to a GDI issue with azure and Image rendering (which we are doing, rendering an dataurl to an image and injecting it onto the report) but most of those issues seemed to be resolved back in 2014
Are there still known issues with Azure and AR? How can I go about addressing this drastic increase in errors?
