Hi Team,

We are facing an issue with EO.Pdf after deployed in to the azure app service (i.e) time out exception, as per our observations we got some info related to this from queries already raised by some one in EO portal.As per your comments instead of Azure app service better to put the code int to Azure Worker Role , but currently it is not possible for our project.Please let us know if there is any other solution.??

Please find the below link and sample code which we are using.
https://www.essentialobjects.com/forum/postst8015_Error-creating-PDF-document-in-Azure-Website.aspx

Code:
MemoryStream pdfStream = new MemoryStream();
{

HtmlToPdf.ConvertHtml(contentDecodeString, pdfStream, op);

byte[] pdfFileBytes = pdfStream.ToArray();
MemoryStream outPutStream = new MemoryStream(pdfFileBytes);
response.Content = new PushStreamContent((responseStream, httpContent, tc) =>
{
outPutStream.CopyTo(responseStream);
responseStream.Close();
}, "application/octet-stream");
HttpStatusCode successStatus = HttpStatusCode.Created;
response.StatusCode = successStatus;
response.Content.Headers.ContentType = new MediaTypeHeaderValue("application/pdf");
response.Content.Headers.ContentDisposition = new ContentDispositionHeaderValue("attachment");
response.Content.Headers.ContentDisposition.FileName = "sample.pdf";
response.Content.Headers.ContentLength = new MemoryStream(pdfFileBytes).Length;
return response;
}

please provide solution asap and also we ready to discuss over video call if required.
Regards,
Gowtham.

Hi Support ,
Thanks for your reply . Currently we have deployed EO PDF in to a app service running under dedicated premium VM . not in to a shared VM . please recheck and suggest us on this .

Can you try to use remote desktop to connect to the computer directly, then run our installer on the computer and run the sample application locally and see if it works for you?

Hi Support,
Any update on this?

Thanks,
Kumo Team.

Hi,

Sorry about the late replying. We were trying to test this on our end.

During our test it did work --- our test steps are as follow:

1. Create a new blank MVC Test app based on .NET Framework 4.6;
2. Follow steps here to add MVCToPDF to it:

https://www.essentialobjects.com/doc/pdf/web/mvc.aspx

During our test, we simply added [EO.Pdf.Mvc.RenderAsPDF] attribute to the "About" method in HomeController;

3. Deply the site to Azure, then click "About" and it successfully generated a PDF file for download;

Please try the above step and see if it works for you. If that still does not work for you, add the following code to your Application_Start handler before you call EO.Pdf.Mvc.MVCToPDF.RegisterFilter (per instructions in step 2):



Please let us know if this works for you.

Thanks

Hi,

There should be no real difference between Web API app and a regular MVC app from the HTML to PDF point of view because they use the same pipeline. In fact in the same MVC test app we tried the following code and it also works fine:



The reason we also tested MVCToPDF attribute is because it will produce the result as download thus is easier to verify. This code while it produce no visible result if it succeeds, it should produce an exception if it fails.

You can run this test first and see whether it works for you. We understand this test code does very minimum and it will not achieve the same task you wanted to achieve in your application, but the above code will test whether the core browser engine is working correctly in your environment.

Thanks!

Team,

We are waiting for your response, please check above post and suggest us on this asap.

Thanks
Kumo Team

Thanks for the update.

But EOPDF dll is not responding while running on azure app service with below few lines when we make it as 64 bit.

When we update to 32 bit then the same code is working fine and again updated back to 64 bit then its not responding.

PdfDocument doc = new PdfDocument();
HtmlToPdf.ConvertHtml("test", doc);

I also tried in my local machine and its worked well in both 32 and 64 bit but when we deploy it in Azure app service, its not responding in 64 bit.

Do you have any success story with azure app service running on 64 bit or can you try once on Azure app service.

We kept below two lines of code only in the API call which worked well in 32 bit but not 64 bit. We debug the code while running on azure app service and have seen its hanging in the line HtmlToPdf.ConvertHtml("test", doc); of code.

PdfDocument doc = new PdfDocument();
HtmlToPdf.ConvertHtml("test", doc);

Good to hear.

Can you please share the sample code used and the settings placed in App service, so this will help us to compare the difference in our app service settings.

Can we have a quick call, please suggest your availability and contact details.

Thanks,
Kumo Team