Page 1 of 1

2017.1 Will not print properly with windows 10

Posted: Thu May 04, 2017 12:35 pm
by chrisfeltman
Symptoms are:
Windows 7: prints properly except for print to pdf produces a corrupted file.

Windows 10: with a directly attached printer, will produce printed output on windows 10 but headers are cut off
with a network printer, produces no output. Print to pdf produces a corrupted file.

Re: 2017.1 Will not print properly with windows 10

Posted: Thu May 04, 2017 1:58 pm
by Andrew
Hello,

Please try to upload the archive as a link to google or dropbox.

Thank you.

Re: 2017.1 Will not print properly with windows 10

Posted: Thu May 04, 2017 2:01 pm
by chrisfeltman
Test case attached

Re: 2017.1 Will not print properly with windows 10

Posted: Thu May 04, 2017 2:01 pm
by chrisfeltman
My network will not allow access to file sharing services.

Re: 2017.1 Will not print properly with windows 10

Posted: Fri May 05, 2017 12:21 pm
by Alex K.
Hello,

We couldn't reproduce this bug.
Please check the modified project and results in the attachment.

Thank you.

Re: 2017.1 Will not print properly with windows 10

Posted: Mon May 08, 2017 4:39 pm
by chrisfeltman
It seems to work properly when we let stimulsoft open its own viewer window, but when showing in the StiViewerControl it behaves differently. Why would this be?

Re: 2017.1 Will not print properly with windows 10

Posted: Wed May 10, 2017 12:45 pm
by chrisfeltman
Ok, worked around that problem by hosting the winforms version in WPF with the <winformshost> provision, and now printing works in windows 10, BUT

We use FIPS and when I try to register the license key on a FIPS-enabled windows 10 machine, I get the following:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

We cannot delay our release much longer, please help!

Re: 2017.1 Will not print properly with windows 10

Posted: Fri May 12, 2017 7:19 am
by Alex K.
Hello,

We have added some improvements in this direction. It will be available in the release which will be available today.

Also, if the issue still present, please try to set the following option:
StiOptions.Engine.FIPSCompliance=true;

This changes will available in 2017.1.3 release.

Thank you.