ExportDocument - AccessViolationException

Stimulsoft Reports.NET discussion
Post Reply
luczan
Posts: 32
Joined: Wed Jan 19, 2011 3:50 am
Location: Slovakia

ExportDocument - AccessViolationException

Post by luczan »

Hello,
can you help me with this problem?
....
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at Stimulsoft.Report.StiReport.ExportDocument(Stimulsoft.Report.StiExportFormat, Stimulsoft.Report.Export.StiExportService, System.IO.Stream, Stimulsoft.Report.Export.StiExportSettings)
at Stimulsoft.Report.StiReport.ExportDocument(Stimulsoft.Report.StiExportFormat, System.IO.Stream, Stimulsoft.Report.Export.StiExportSettings)
.....

my pdf settings:
var settings = new StiPdfExportSettings { ImageQuality = 1.0f, ImageResolution = 500, KeywordsString = this.TemplateValidFrom.ToString("dd.MM.yyyy HH:mm:ss") };
settings.UseDigitalSignature = true;
settings.GetCertificateFromCryptoUI = false;
settings.UseLocalMachineCertificates = true;
settings.SubjectNameString = certificateName;


Stimulsoft version: 2012.3.1404.0

..but i can't reproduce this issue.

thanks
marek
HighAley
Posts: 8430
Joined: Wed Jun 08, 2011 7:40 am
Location: Stimulsoft Office

Re: ExportDocument - AccessViolationException

Post by HighAley »

Hello.

It seems that there is an access error. Do you have access to the file where you tries to export report?

Thank you.
luczan
Posts: 32
Joined: Wed Jan 19, 2011 3:50 am
Location: Slovakia

Re: ExportDocument - AccessViolationException

Post by luczan »

hello,

i think, it's not a problem with access right to read/write file.

i find that this exception is thrown always when:
1. turn on computer
2. start my app to generate PDF documents in parallel (when documents are generated "one after another", no error is occured)

later - when app is started again with same data, all is ok.

do you have any idea, what's wrong?

thanks
marek
HighAley
Posts: 8430
Joined: Wed Jun 08, 2011 7:40 am
Location: Stimulsoft Office

Re: ExportDocument - AccessViolationException

Post by HighAley »

Hello.

To answer your question we need additional information:
• Your operational system (98, ME, 2000, XP, Vista or NT), its version and localization, installed service-packs;
• Version the of Microsoft .Net Framework package installed and its localization;
• Name of your development framework and its version;
• Additional information that can help us to solve your problem.

Thank you.
luczan
Posts: 32
Joined: Wed Jan 19, 2011 3:50 am
Location: Slovakia

Re: ExportDocument - AccessViolationException

Post by luczan »

all - EN localization

Windows 7 Professional (64) SP1 with all available updates
Microsoft .Net Framework Version 4.5.50709
Visual Studio Professional 2012 Version 11.0.50727.1
StimulsoftReports.Ultimate - the latest version

Memory dump is attached.

thank you
Attachments
MemoryDump.rar
(6.26 MiB) Downloaded 346 times
luczan
Posts: 32
Joined: Wed Jan 19, 2011 3:50 am
Location: Slovakia

Re: ExportDocument - AccessViolationException

Post by luczan »

we did (probably) find problem:
memcpy

if (Win32.CryptSignMessage(ptr7, 1, 1, ptr, rgcbToBeSigned, pbSignedBlob, ref pcbSignedBlob) == 0)
in StiPdfExportService.CreateSignature


http://msdn.microsoft.com/en-us/library ... 85%29.aspx
On input, buffer sizes are usually specified large enough to ensure that the largest possible output data will fit in the buffer.
HighAley
Posts: 8430
Joined: Wed Jun 08, 2011 7:40 am
Location: Stimulsoft Office

Re: ExportDocument - AccessViolationException

Post by HighAley »

Hello.

Could you send us a sample project to reproduce the issue?

Thank you.
luczan
Posts: 32
Joined: Wed Jan 19, 2011 3:50 am
Location: Slovakia

Re: ExportDocument - AccessViolationException

Post by luczan »

hello,

we sent you a mail with console app on monday - mail: [#PTD-815264]: Stimulsoft - system.AccessViolationException

marek
Alex K.
Posts: 6488
Joined: Thu Jul 29, 2010 2:37 am

Re: ExportDocument - AccessViolationException

Post by Alex K. »

Hello,

The issue is fixed.
The solution will be available in the next prerelease build.

Thank you.
Post Reply