We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

List of possible server errors in PDF Viewer

Platform: ASP.NET Core - EJ 2 |
Control: PDF Viewer |
Published Date: April 12, 2019 |
Last Revised Date: April 12, 2019

EJ2 PDF Viewer

The Essential JS 2 PDF Viewer is a modern UI Controls library that has been built from the ground up to be lightweight, responsive, modular, and touch-friendly. It is written in TypeScript and has no external dependencies. It also includes complete support for Angular, React, Vue, ASP.NET MVC, and ASP.NET Core frameworks.

List of possible server errors in PDF Viewer

The Essential JavaScript PDF Viewer have server-side dependency to get the details from PDF documents for rendering. The following are the list of possible server-side errors and their solutions:

  1.  Failed to load resource: The server responded with a status of 404 (Not Found) error. Refer to the following list of possible solutions:
  1. Details: Web service is not mapped properly using the serviceUrl property in the PDF Viewer. So, map to the web service properly in the serviceUrl property.
  2. Details: Due to the limitation of allowed content length in the application. You can resolve this issue by setting the maxAllowedContentLength in the Web.Config.  Refer to the following code for the same.

Web.Config

 <system.webServer> 
<security> 
    <requestFiltering> 
      <requestLimits maxAllowedContentLength="2147483647" />  <!-- 2 GB--> 
    </requestFiltering> 
  </security> 
</system.webServer> 
 

  1. Failed to load resource: ERR_CONNECTION_REFUSED

Details: Either the Web service is stopped or the network connection to the web service is not proper. Check whether the connection to the web service (Web API controller) is proper to resolve this error.

  1. 500 Internal Sever error

Details: Internal sever error will be thrown if any exception was thrown in the Web service. Enable the exception settings to find the cause of the exception and share the exception details and StackTrace details to our support team. So that they can investigate further and provide the solution.

  1. 500 Internal Sever error: /api/PdfViewer/RenderPdfPages 

Failed to load resource: The server responded with a status of 500 (Internal Server Error). Unable to find an entry point named 'FPDFTextObj_GetText' in DLL 'Pdfium.dll' exception will be thrown in server side

Details: This issue occurs when refer the old Pdfium assemblies in the project. Remove the bin, obj and x86 or x64 (which contains the Pdfium assemblies) folders from the project and run it.

Note:

If the Pdfium assemblies are already available in the project location, it will not be replaced again and again. So, delete the mentioned folders while updating to the latest version.

2X faster development

The ultimate ASP.NET Core UI toolkit to boost your development speed.
ADD COMMENT
You must log in to leave a comment

Please sign in to access our KB

This page will automatically be redirected to the sign-in page in 10 seconds.

Up arrow icon

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon

Live Chat Icon For mobile