|
Rank: Newbie Groups: Member
Joined: 7/27/2012 Posts: 4
|
Hi,
We have been using your EO.Pdf.dll - version 3.0.104.2 - date 24/4/2012 15:54.
On our website running on IIS 6 on Windows Server 2003, everytime someone places an order, we generate a PDF document with a barcode in it (by using <img src=''> to the bar code image).
The problem we have is about 1 in every 100 orders causes the following error to occur: Convertion failed. Failed to initialize conversion.
We have tried everything but it is very hard to reproduce. Can you help us please? Below is the event viewer details:
Event code: 3005 Event message: An unhandled exception has occurred. Event time: 7/27/2012 3:42:30 PM Event time (UTC): 7/27/2012 2:42:30 PM Event ID: 64070d2733cd45cc84c243f939e229ee Event sequence: 50071 Event occurrence: 22 Event detail code: 0 Application information: Application domain: /LM/W3SVC/89/ROOT-1-129878437041465000 Trust level: Full Application Virtual Path: / Process information: Process ID: 10752 Process name: w3wp.exe Account name: NT AUTHORITY\SYSTEM Exception information: Exception type: HtmlToPdfException Exception message: Convertion failed. Failed to initialize conversion.
Request information: User: Is authenticated: False Authentication Type: Thread account name: NT AUTHORITY\SYSTEM Thread information: Thread ID: 14 Thread account name: NT AUTHORITY\SYSTEM Is impersonating: False Stack trace: at EO.Pdf.HtmlToPdfException.b(Exception A_0) at EO.Pdf.Internal.kq.a() at EO.Pdf.Internal.kq.b() at EO.Pdf.HtmlToPdf.a(kq A_0) at EO.Pdf.HtmlToPdf.ConvertHtml(String html, PdfDocument doc) at Magico.MagiBiz3.Document.ConvertHTMLToPDF(String HTMLToConvert) in C:\SVN\Libraries\Version03.01.01\Trunk\MagiBiz3\Modules\Document.cs:line 1170 at Magico.MagiBiz3.Document.ConvertHTMLToPDF_IntoFile(String HTMLToConvert, String FilePath) in C:\SVN\Libraries\Version03.01.01\Trunk\MagiBiz3\Modules\Document.cs:line 1161 at Magico.MagiBIZGoTemplate.WebsiteCommonCode.Doc_SaveDocumentToFile(MagiBizDocument_Doc CurrentDoc, Guid ReferenceID) in C:\SVN\Websites\MagiBIZTemplate\Trunk\go\_privateAppCode\MagiBizDocument.cs:line 254 at Magico.MagiBIZGoTemplate.MagiShopOrder.CheckForAutoCreateDocuments(Guid CurrentOrderID) in C:\SVN\Websites\MagiBIZTemplate\Trunk\go\_privateAppCode\MagiShopOrder.cs:line 2311 at Magico.MagiBIZGoTemplate.ShopCheckout.OnTabPostValidation(Object o, DetailViewEventArgs e) in C:\SVN\Websites\MagiBIZTemplate\Trunk\Shop_Checkout.aspx.cs:line 2115 at Magico.MagiBIZGoTemplate.MagiBizControl_Tabs.RaiseTabPostValidationEvent(MagiBizTab CurrentTab) in C:\SVN\Websites\MagiBIZTemplate\Trunk\Controls\MagiBizControl_Tabs.ascx.cs:line 762 at Magico.MagiBIZGoTemplate.MagiBizControl_Tabs.DisplayTabs() in C:\SVN\Websites\MagiBIZTemplate\Trunk\Controls\MagiBizControl_Tabs.ascx.cs:line 396 at Magico.MagiBIZGoTemplate.MagiBizControl_Tabs.OnPreRender(EventArgs e) in C:\SVN\Websites\MagiBIZTemplate\Trunk\Controls\MagiBizControl_Tabs.ascx.cs:line 130 at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,195
|
Hi,
There are a number of things that can cause this error. Usually when this happens another event entry with an error code will be logged in your event viewer. Please see if you see that entry. If you see that entry, let us know the error code and we might be able to make sense out of it.
You can also download the latest version and see if that fixes the problem ----- it should be backwards compatible with your version, you do need to revisit your license key page to get a new license key though.
Thanks!
|
|
Rank: Newbie Groups: Member
Joined: 7/27/2012 Posts: 4
|
Thank you for your fast response. Each time this error happens, there is not a second event entry in the event viewer - is there something we need to do to turn this on?
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,195
|
Hi,
No. This is nothing you need to do to turn this on. You may want to try the same feature from a blank test application and see if that works for you. If that still does not work for you, we will need you to open up your server to us so that we can troubleshoot further.
Thanks!
|
|
Rank: Newbie Groups: Member
Joined: 7/27/2012 Posts: 4
|
I downloaded the latest version (seems to have been just released in the last 2 days).
However, we have set up a simple stress test environment to try and reproduce this issue where we spin off 10 threads and each thread creates 10 PDF documents one at a time - and these are very large PDF documents with 88 pages in each one. With the new version, there were delays of about 4 minutes to create the first 10 documents across the 10 threads and then the next 10 minutes werent generated for another 2 minutes. And so on.
When I switched back in the 2011.2 version of EO.PDF, it worked fine with each document taking about 5 seconds to generate.
So I think there may be a bug in the new release unfortunately or the HTML that we are using does not seem to work well with the new features in it. So I wont be able to try out the new version to see if that fixes the error.
I have done some more analysis on our issue by looking at the 3 orders where the error was generated over the last week (there were about 100 orders in total so 97 orders worked fine). The error seems to happen approximately 40 seconds after trying to generate the PDF document. But in our stress testing environment, the error has never occurred even once after generating hundreds of documents. Is there anything in a web server environment that would make the dll time raise a "Convertion failed. Failed to initialize conversion" error after approximately 40 seconds?
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,195
|
Hi,
We were aware of the "failed to initialize conversion" error with early builds of the old versions but that was fixed. Also we weren't aware of the 40 seconds delay, nor were we aware of significant time difference between the EO.Pdf 2011 and EO.Pdf 2012. So we do not really have anything else to tell you. If we can send us a sample with the new version, we will be happy to investigate further.
Thanks!
|
|
Rank: Newbie Groups: Member
Joined: 7/27/2012 Posts: 4
|
Hi,
I have more information about this error - I ran a test last night to generate 5,000 very large PDF documents across 10 threads and it fell over with the error after 1,157 documents were created. The error message says: "Convertion failed: Operation times out"
I looked at our logs and the time taken for each document to be created was 16-42 seconds - I have a suspicion that if it takes more than 45 seconds (or something like that), your component will automatically time out and throw an error.
Is this correct? And if so, is there a setting which makes this longer?
Thanks, Paul
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,195
|
Hi,
No. It has nothing to do with 45 seconds. When you generate 5000 very large PDF across 10 threads, your server has probably temporarily overloaded. It's quite normal that you get times out error when your server overload. So it should not be a concern. You could try to increase the time out value but that will bring you other problems. This is like occasionally there are more than 4 people trying to ride in your car and you have the choice to say no or try to squeeze them in. If you try to squeeze 5 in then you will face the same problem again when 6 people want to ride with you, and eventually you have to say no at some point. So an overload is an overload and we do not believe it should be concern for either you or us.
Thanks
|
|