34
Views
3
Comments
Solved
[Ultimate PDF] Could not load file or assembly 'Newtonsoft.Json, Version=13.0.0.0 on-premise server
ultimate-pdf
Reactive icon
Forge asset by Leonardo Fernandes
Application Type
Reactive
Service Studio Version
11.53.38 (Build 61903)
Platform Version
11.15.0 (Build 34858)


Hello!

Our project is traditional on-premise.

In dev the component works fine (with internet connection) but in the environment of the client (where we can't have internet connection) is not working properly.

I had to configure the local-chromium and it seems it's ok (please kindly confirm if the configuration looks ok):



Below the print in the webapp server. This folder is accessible by everyone in the security configuration.

The last error I have now is the one below:

Searching in the forum, I saw that the component requires at least the version 11.18.0 of the platform if I understood well. Is this indeed a requirement?

Any guidance to make this component work in a on-premise server without internet connection?

Thank you all in advance.

2020-01-24 11-50-44
Diego Meira
Solution

Hello Pedro!

I had this issue and I rolled back the version to fix and we're living this way.

Our platform version is very old and the UltimatePDF version is not compatible indeed (Version 11.15.0).

I noticed that our error was triggered after install the last version manually (downloaded the component and installed through the Service Studio).

I believe if we update the UltimatePDF using the forge installer, the last compatible version with our platform version is installed.

I hope it helps somehow.

2023-12-19 16-46-19
Castro Vieira

Hello, friend

I recommend using the... component.


https://www.outsystems.com/forge/component-overview/9761/reactive-print-pdf-button-o11


Easy to use =)

2015-09-28 00-04-44
Pedro Coelho

Hi,

After update the component to the last version I have the same issue, the platform version is Version 11.11.3, is this some incompatibility or is there some workaround?

@Diego Meira, were you able to resolve the issue?

Thanks,

Pedro

2020-01-24 11-50-44
Diego Meira
Solution

Hello Pedro!

I had this issue and I rolled back the version to fix and we're living this way.

Our platform version is very old and the UltimatePDF version is not compatible indeed (Version 11.15.0).

I noticed that our error was triggered after install the last version manually (downloaded the component and installed through the Service Studio).

I believe if we update the UltimatePDF using the forge installer, the last compatible version with our platform version is installed.

I hope it helps somehow.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.