Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
When attempting to generate images we are getting the following error:
the preview request failed with message: object 'xxx' from sense app 'xxx' had problems when rendering. Error cef. rendering exception. error during GRPC request. error: engine.Navigator.QlikSense.sdk.rendering.mashuploadexception: request with id 'xxx' failed with remote error errorloadurltimeoutresult, mashup failure
We're on the April 2020 version of Qlik Sense and Nprinting.
Running the Benchmarks resulted in error:
System.Exception: Object <objectID> of Sense app <appID> failed to render. Error Buffer cannot be null
The Benchmarks error log records it as:
2021-02-12 13:03:37,117 [11] ERROR Engine.Navigator.QlikSense.SDK.Extensions.SdkExtensionMethods - Engine.Navigator.QlikSense.SDK 18.40.0.0 Engine.Navigator.QlikSense.SDK.Extensions.SdkExtensionMethods 20210212T130337.117-05:00 ERROR <RedactedServerNameHere> 0 0 0 0 0 0 0 0 ERROR: System.ArgumentNullException: Buffer cannot be null.??Parameter name: buffer?? at System.IO.MemoryStream..ctor(Byte[] buffer, Boolean writable)?? at Engine.Navigator.QlikSense.SDK.Extensions.SdkExtensionMethods.ExportToImage(IGenericObject sheetObject, SenseApp app, Guid requestId, Dictionary`2 propertyValues, Int32 width, Int32 height, Int32 dpi, Double zoom, KeepAspectRatioStrategy keepAspectRatioStrategy, FallbackStrategy fallbackStrategy)
I think I've tried everything.
I've extended the timeouts, checked and reinstalled certificates, setup https. Any help would be greatly appreciated. I'm not sure whatelse to try.
Yes if you are connecting directly to a proxy node that is not linked to a virtual proxy, this could be the issue. Further, NPrinting only support NTLM authentication, head and saml auth for example, are not supported authentication methods.
Microsoft Windows NTML authentication on the Qlik Sense proxy. SAML and JWT are not supported. If your virtual proxy uses SAML or JWT authentication, you need to add a new virtual proxy with NTLM enabled for Qlik NPrinting connections.
The following must be correctly set up:
In your case I suspect you 'may' need to set up Virtual Proxy that uses windows authentication (ticketing, windows) then link your proxy node to the new virtual proxy via the virtual proxy settings.
If all the requirements have been met and your QS client.pfx cert has been exported correctly and copied to C:\Program Files\NPrintingServer\Settings\SenseCertificates folder on the NP server, then we may need to have a closer look at your environment to investigate more thoroughly. If so, please start a support request with the Qlik Support desk at your convenience.
Kind regards...
Hi @WMLouis
It's not clear which certificates you are referring to. Also did you recently upgrade to April 2020 Qlik Sense.
If so, please check the following article to ensure you have exported your certificates accurately from Qlik Sense and copied to the expected folder on the NP server.
Kind regards...
The certificate I was referring to were the Qlik Sense ones.
I've since updated the Nprinting server to November 2020 and run into what feels like the same error.
Thank you
Yes if you are connecting directly to a proxy node that is not linked to a virtual proxy, this could be the issue. Further, NPrinting only support NTLM authentication, head and saml auth for example, are not supported authentication methods.
Microsoft Windows NTML authentication on the Qlik Sense proxy. SAML and JWT are not supported. If your virtual proxy uses SAML or JWT authentication, you need to add a new virtual proxy with NTLM enabled for Qlik NPrinting connections.
The following must be correctly set up:
In your case I suspect you 'may' need to set up Virtual Proxy that uses windows authentication (ticketing, windows) then link your proxy node to the new virtual proxy via the virtual proxy settings.
If all the requirements have been met and your QS client.pfx cert has been exported correctly and copied to C:\Program Files\NPrintingServer\Settings\SenseCertificates folder on the NP server, then we may need to have a closer look at your environment to investigate more thoroughly. If so, please start a support request with the Qlik Support desk at your convenience.
Kind regards...
Setting up a Virtual Proxy connection in Sense and added the prefix to the url fixed my issue. Thank you so much!
No worries @WMLouis!
Glad to help...fs