[Ultimate PDF] Ultimate PDF: Error when exporting web screen to PDF (403) Forbidden
Forge component by Leonardo Fernandes
Published on 08 Jan 2021


I am trying to use the "Ultimate PDF" extension in OutSystems 11 to export a web screen to a new tab via the "ScreenToPDF" web block, but I am getting the following error:

"The remote server returned an error: (403) Forbidden.

at ssUltimatePDF.RssExtensionUltimatePDF.MssSetupLocalBrowser(HeContext heContext, Int32 inParamBrowserRevision)".

I assume this has to do with a security layer from the server (on-premises), but I wonder if there is any workaround or suggestion for this situation?

Thank you in advance for your attention.

Best regards,


Rank: #5

Hi Francisco.

UltimatePDF tries to download Chromium from https://storage.googleapis.com/chromium-browser-snapshots/Win_x64/637110/chrome-win.zip (by default), and it looks like this is the step that is failing in your case. You might have some firewall or other policy that is preventing your application server to download that file on demand.

What you can do is download this zip file yourself, and extract it into C:\Windows\Temp\.local-chromium\Win64-637110. Let me know if this solves your problem.

Rank: #317

For clarification purposes. If you download the binaries yourselves, they should be dropped on the server in this folder (exemple for version 758804)

Rank: #939

Hi Kurt,

We have met the same issue. How can we allow to download temp files into the server folder? Please advise

Rank: #317


If you have remote access to the server, the easiest is to download the libraries and put them on the server in the windows temp folder.

If you want to allow the server to download the binaries automatically, it needs to have a connection to the internet and more specifically to om https://storage.googleapis.com/chromium-browser-snapshots/Win_x64. If the connection is not open, then the network team will have to add a firewall rule to allow the connection. Or let it pass via the proxy.

Also make sure the site properties are set correctly. If you put binaries on the server yourselves, the site propertie for the version must have to number of the binarie you downloaded.

You also might want to check if the IIS_IUSRS has access to c:\windows\temp.

Does this help you further?