SetProcessDpiAwareness failed

jhogewoning · November 27, 2017, 9:26am

When printing a report in the app everything is fine but in the application.log file this is the error message:

2017-11-27 10:19:18 com.cubewise.servlets.PrintServlet ERROR PrintServlet:75 |SetProcessDpiAwareness failed: “COM error 0x80070005 (Unknown error 0x0ffffffff80070005)”

com.cubewise.k: |SetProcessDpiAwareness failed: “COM error 0x80070005 (Unknown error 0x0ffffffff80070005)”

at com.cubewise.i.a(SourceFile:55)
at com.cubewise.servlets.PrintServlet.doGet(SourceFile:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:624)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.filters.ExpiresFilter.doFilter(ExpiresFilter.java:1201)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:445)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1115)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)

This is the value in settings.json:

“printDPI”: 170

What is here the error?

plim · November 27, 2017, 11:21pm

Hi @jhogewoning,

That is related to the underlying library that Canvas uses for printing to PDF.

github.com/ariya/phantomjs

COM error 0x80070005

opened 10:02AM - 14 Mar 16 UTC

closed 11:55PM - 28 Dec 19 UTC

branneman

Need more information stale

Using: - npm package [phantomjs-prebuilt](https://www.npmjs.com/package/phantomj…s-prebuilt) version 2.1.5 - tested with Node.js versions 4.0, 4.4, 5.0 and 5.8 - tested on Windows Server 2012 R2 (x64) at AppVeyor, [more specs here](https://www.appveyor.com/docs/installed-software#visual-studio-2015) Error: ``` SetProcessDpiAwareness failed: "COM error 0x80070005 (Unknown error 0x0ffffffff80070005)" ``` Possibly related to: - [appveyor/ci/issues/666](https://github.com/appveyor/ci/issues/666) - [karma-runner/karma/issues/598](https://github.com/karma-runner/karma/issues/598) - [QTBUG-38993](https://bugreports.qt.io/browse/QTBUG-38993)

Can you please submit a ticket for this? Thanks.

–
Paul

plim · November 29, 2017, 9:56pm

Hi @jhogewoning,

And just to clarify on to this, the PDF when printed/created is complete?

–
Paul

jhogewoning · November 30, 2017, 7:09am

Hi @plim,

The PDF’s are complete but this message is generated for every printed report.
It’s on both the production and the development server.

JD.

plim · November 30, 2017, 9:51pm

Hi @jhogewoning,

Thanks for that update! As for that error, you can ignore it for the meantime.

The underlying library somehow is generating that even though it still generates the PDF. We have put in a minor patch in the meantime for this particular situation so that it can still be usable while we look into finding an update for the underlying library.

Thanks for the ticket! We will keep that for reference on that error issue.

Cheers!

–
Paul