Rank: Newbie
Groups: Member
Joined: 2/20/2012
Posts: 1
|
First I want thank Essential Objects for putting together a spectacular product, haven't been able to use a component (3rd party or MS) this easily ever!
We are getting a warning periodically, when our code that utilizes the EO.Pdf.dll. Here's the windows event:
Provider: EO.Pdf
EventID: 0
Level: 3
Task: 0
Keywords: 0x800000000000000
TimeCreated: 2012-03-29T18:30:23.000000000Z
EventRecordID: 1901
Channel: Application
Computer: **************
Security: (blank)
EventData:
System.ComponentModel.Win32Exception: Error creating window handle. at
System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp) at
System.Windows.Forms.Control.CreateHandle() at
System.Windows.Forms.Control.CreateControl(Boolean fignoreVisible) at
System.Windows.Forms.Control.CreateControl() at EO.Pdf.Internal.hc.f() at
EO.Pdf.Internal.kl.a(Int32 A_0, IntPtr A_1, Int32 A_2)
Here's the scenario:
This is a console application being run as a scheduled task. Every 5 minutes it runs pulls some data from a database and then converts the html in to a pdf, in some cases combining the html with a text file. The application has it's own user that it runs as.
The thing is it doesn't seem to be affecting the creation or conversion of pdf documents. All of them that have been created at or around the time of the warning seem to contain all the elements that they should.
Not sure what other information you need.
And here is the question: What might be causing this issue? Does it seem to be a permissions issue?
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
Thank you very much for your compliment. We are glad to hear that you like our product.
I can not make sense out the error. Permission issue can cause failure to create handle but if permission was the issue, then it would have failed every time. Another common cause for this error is handle leak, but that usually only occurs if both these conditions are true: A. We have a leak; B. The process has been running for a long time. In your case since you are running it from Scheduler, so it starts fresh every time. Thus that is not likely to be the cause either.
Currently the exception message "Error creating window handle" does not contain any error code. What we can do is to change our code to log the error code as well and then have you run it. Obviously that won't fix the problem but it might reveal what's the root cause for this issue. Please let us know if you would like us to do that.
Thanks!
|