invalid window handle

Ren

Member²
Hi all.
When click on cell button in LONG, BLOB, CLOB cells I got 'invalid window handle' error box.
Using latest version I'm still getting this stupid error. Apeared during 6.x release and from when never disapeared. I found some posts here on forum but no solution. OS is XPSP2 Eng, with very few additional apps installed.

--- Info ---

PL/SQL Developer
Version 7.0.2.1076 (MBCS)
01.33773 - 10 user license
Windows XP version 6,0 (build 2600) Service Pack 2

Physical memory : 1
 
I have the same problem but only when I use PL/SQL Developer with windows remote desktop.

Still have the problem with V7
 
To obtain some more diagnostic information, can you modify the shortcut and add the debug parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" debug

Reproduce the problem and send me the debug.txt file that is generated in the PL/SQL Developer directory.
 
Sorry for the lack of feedback, it's a bit of a puzzling problem. Can you send me a registry export of:

HKEY_CLASSES_ROOT\MSXML
HKEY_CLASSES_ROOT\MSXML2
 
MSXML CLSID {CFC399AF-D876-11D0-9C10-00C04FC99C8E}
MSXML2 CLSID {F6D90F10-9C73-11D3-B32E-00C04F990BB4}

There's MSXML 6.0 Parser installed on all affected machines. But removing changed nothing.
 
I have the same problem too: 'invalid window handle' error box.

Info PL/SQL Developer
Version 7.0.3.1123 (MBCS)

Was the problem solved?
 
I received a tip from a user that this problem can occur if the "Print Spooler" service is not running. I tested this, and it does indeed lead to an "Invalid Window Handle" error. We'll fix this, but it may be useful to check if this service is not running on your PC as well, and start it if this is indeed the case.
 
I got this problem too.
My default printer is a Net Printer and i got the message of "invalid window handle" everytime i was not connected to the LAN of this printer.
I have only set another printer as default printer and this has been the solution.

I hope this tip could be useful.
Bye
 
I too was using a printer on a print server. I changed the default to the PDF Writer and things started working. Then I checked the printer status. My network printer was not *Ready*. I readied it, then changed the default printer back, started a new copy of PL/SQL Developer, and things were fine.

So the issue seems to occur if the default printer is not in a ready state. Note that the dialog that opens when viewing a CLOB has a print icon. Most likely, the print control attempts to initialize and gets an invalid window handle.

So there's your clue, development team. I would be willing to bet that if you investigate the inititialization of the print control that you will iedentify your problem. You may be able to keep the print control there but not initialize it until the user actually attempts to print. That way we won't all have to suffer the consequences of a missing or malfunctioning printer that we weren't going to use anyway, eh?
 
Back
Top