Hi,

I've the same errors with the new assemblies and the route ignoring.

I've also tried to export by 

var fichier = "ReportExport_" + DateTime.Now.ToShortDateString() + ".pdf";

var reportUri = new Uri("avitax-total;component/Ventes.igr", UriKind.Relative);

using (var exporter = ServerExporterFactory.CreateExporter(reportUri))
{

var memoryStream = new MemoryStream();

var data = new DataSourceValue { Name = "Sales", Value = model.SalesList };

IEnumerable<DataSourceValue> dataList = new List<DataSourceValue>() { data };

exporter.DataSources = dataList;

exporter.Export(memoryStream, "PDF");

SendStreamToResponse(memoryStream, fichier, "application/pdf");

memoryStream.Close();
}

And I have the following error message

[NullReferenceException: Object reference not set to an instance of an object.]
   Infragistics.Documents.Reports.TTF.Font.Subset(Boolean regular) +56
   Infragistics.Documents.Reports.PDF.Font.EmbedData() +46
   Infragistics.Documents.Reports.PDF.PdfDocument.Generate(Stream stream) +142
   Infragistics.Documents.Reports.Report.Report.Publish(Stream stream, FileFormat format) +2580
   Infragistics.Reports.Pdf.PdfDocument.Export(Stream targetStream) +138
   Infragistics.Reports.Engine.ReportExporter.ExportInternal(IReportItemVisitor reportItemVisitor, IDocument document, Stream targetStream, ExportCallback callback, IReportItemRendererFactory factory, ICancelationProvider cancelationProvider) +201

Hi,

do you have any news about this problem ?

For the moment the only "fix" we find is to install a webservice to perform the export from an azure virtual machine but it could not be a long term solution. 

Hi All,

Thank you for your feedback and outlining the possible cause of the issue. we are currently working on reproducing this at our end in order to determine its cause.

I will keep you posted of any developments regarding this matter.

Sorry to nag but this is showstopper issue for my client.  The reports aren't much good if we can't get them "out".  Is there a fix in works or is there someone who could help me with a workaround?

Hello All,

Thank you for your replies

We are looking into this matter with high priority and will keep you posted of any available information.

Hello,

Thank you for your patience.

After further investigation, I have asked our engineers to examine the scenario further. In order to ensure that the matter receives attention, I have logged it in our internal system with an ID of 145297. The next step would be for a developer to review my findings and offer more feedback and suggestions.

Please do not hesitate to contact us with any questions or updates in the meantime.

Did this issue ever get resolved? As we are seeing similar behavior also using version 13.2.

Has it been addressed in later versions of Infragistics?

Thanks