Has anyone used EvoPdf library on DASP ?

Discussion in 'Third-party applications' started by Clairassur, Dec 16, 2011.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. Hello everyone,

    We're trying to use pdf generator library from EVO (evopdf.com). Works perfect on local, but we get an error on host.

    EVO support says it's due to permissions on dll file evointernal.dll
    DAsp support says we've got all rights on all files.

    Thanks.
     
  2. What is the full error you are getting? And can you ask the vendor of this product to verify if this is a .Net component or does it require to be installed directly on the server.
     
  3. Thanks Raymondp for your interest.

    "Could not get conversion result header. Data receive error. Could not receive data. Error code: 109 "
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.Exception: Could not get conversion result header. Data receive error. Could not receive data. Error code: 109

    Source Error:
    Line 44: Byte[] pdfBytes = pdfConverter.GetPdfBytesFromHtmlString(strHtmltoconvertPDF);
    Line 45: System.IO.File.WriteAllBytes(strPdfFilename, pdfBytes);
    Line 46:


    Source File: e:\web\clairsysnet\htdocs\EvoPdfSample\Default.aspx.cs Line: 44

    Vendor says :
    - no installation or setup is required on server / Can be deployed on the server by simple xcopy deployment

    - "it might be good to try to give Everyone execute access to that file(evointernal.dll). I insist with this because it is the only situation when we know the conversion can fail with that message"
     
  4. Do you have a URL we can look at to see this error message. You may need to outline us some steps to get this error message to appear on our end.
     
  5. RayH

    RayH DiscountASP.NET Lackey DiscountASP.NET Staff

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page