Creating reports and dashboards | Stimulsoft community forum

Hello,
we've just finished migrating our web server to a new, 64-bits, machine.
All is working great, except StimulReport.
When we export the report to PDF, we have the following error message:
[NullReferenceException: Object reference not set to an instance of an object.]
Stimulsoft.Report.Export.StiPdfExportService.AssembleRtf(StiComponent component) +537
Stimulsoft.Report.Export.StiPdfExportService.ExportPdf(StiReport report, Stream stream, StiPdfExportSettings settings) +7857

The ASP.NET application is running is 64-bits mode.
Running it in 32-bits mode gives us the same error.
On the previous server, with the same application, it's working fine.
Running the WPF designer on the 64-bits server, with the same report, is working.

What can we do to have Stimulreport working again?

Patrick

Hello,

Are there any printer drivers installed on this server? There was a similar problem when no one printer was installed on PC.

To solve a problem rapidly we need the following information from you:
• Product name and its version;
• Version operational system and localization, installed service-packs;
• Version the of Microsoft .Net Framework package installed and its localization;
Also send us your .mrt file with database on support@stimulsoft.com for analyses.

Thank you.

Hi Aleksey,
The only printer driver is the Microsoft XPS driver.

Product: StimulReport.WPF 2010.1.700
O.S. Windows Web Server 2008 R2, english, no service pack.
.NET Framework 4.0.30319, full version, english.

How can I send the database to you?

Patrick

Hello,

Please, for this version of the designer, try to disable the Wysiwyg property for problem RichText components.
Also try to set some real printer on this server.
Also download the latest prerelease build and test a report on it.

Thank you.

Aleksey,
disabling the Wysiwyg property for the RichText component solves the error.
But it seems like a bug in StimulReport, no?
Patrick

Hello,

Patrick8639 wrote:disabling the Wysiwyg property for the RichText component solves the error.
But it seems like a bug in StimulReport, no?

Have you checked your report under the latest build? Because we made some fixes in that direction about some few weeks ago.

Thank you.

Aleksey wrote: Have you checked your report under the latest build? Because we made some fixes in that direction about some few weeks ago.

Aleksey,
I don't want to test on a prerelease version: the server is up and running and it's too dangerous to try on it.
Patrick

Hello,

Because we made some fixes in that direction about some few weeks ago.
If you have an opportunity to test the latest prerelease build and let us know about the result.

Thank you.