Rank: Newbie
Groups: Member
Joined: 9/3/2011
Posts: 6
|
EO.Pdf.HtmlToPdfException: A generic error occurred in GDI+
..any way to trace this?
|
Rank: Newbie
Groups: Member
Joined: 9/3/2011
Posts: 6
|
Alright, allow me to elaborate.
Basically I posted a few days back about how the ConvertHtml function simply did not respect or execute the javascript in your virtual browser. If there was some script throwing an error in your virtual environment, I had no way of knowing. However, taking the raw html string, placing it in a text file and simply changing the extension to html worked.
Making a temporary file and then converting the url to the temporary file worked, so I continued with that. unfortunately, now if the file gets too large, I get "A generic error occurred in GDI+.
can you offer any insight? What causes html to fail in your virtual environment, but runn succesfulyl when i drop it in a text file and simply open it in a browser? why might I get the error i posted above, if the file size gets even remotely large? Is there a maximum file size setting for your stuff to work?
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
Thanks for the additional information. File size shouldn't be the issue. Some of our customers use our converter to convert "books" with hundreds of page. Usually if a browser can handle it with little effort, then we should be able to handle it. Besides, the first problem you will hit when your HTML is too large is usually out of memory exception instead of a GID+ exception.
Like the previous JavaScript problem, there is little else we can tell you on this one. I would recommend you to send us a test project so that we can investigate further in order to give you a definite answer. We could guess left and right and you might hit something that would appear to have resolved the issue for you. But the root issue would still be there and it may just popup in another form another day, so in the end the whole exercise would just be a waste of time for both of us. For simple issues that are usually the result of misunderstanding/misusing/not knowing some of our properties/methods, we can tell a solution right away. But obviously you already know our objects quite well, so a test project is the best way to move forward.
One thing that you can try is to update to the current build. The current build changed the way the exceptions are thrown so it would give you more detailed and accurate stack trace. That will not fix the problem, but hopefully will give you/us more information.
Thanks
|
Rank: Newbie
Groups: Member
Joined: 9/3/2011
Posts: 6
|
placing
Thread.Sleep(40);
after I closed/disposed my filestream seemed to resolve this issue, hope that helps
|