PL/SQL Developer does not start

[Jaizkibel]

I have upgraded PL/SQL Developer to 12.0.1 and it worked fine.
But after a reboot over the weekend it does not start any more.

When i type "plsqldev" on the command line the program returns immediately without any error message.

Is there a way to enable some sort of logging?

OS: Windows 7
PL/SQL Developer Version: 12.0.1 64 bit

 

[Marco Kalter]

To obtain some more diagnostic information, can you modify the shortcut and add the DebugSQL parameter? For example:

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

Reproduce the problem and send me the debug.txt file that is generated in the PL/SQL Developer directory or in the %APPDATA%\PLSQL Developer 12 directory (e.g. C:\Users\\AppData\Roaming\PLSQL Developer 12).

 

[Jaizkibel]

Hi Marco,

executed

"C:\Program Files\PLSQL Developer 12\plsqldev.exe" DebugSQL

but there is no file "debug.txt".
Not in "%APPDATA%\PLSQL Developer 12\" or anywhere else.

 

[Marco Kalter]

If you start PL/SQL Developer with the DebugSQL parameter and go to Help > Support Info, you can find the location of the debug.txt file on the "Info" tab page under the "Debug file" section.

 

[Jaizkibel]

How can i do this when the program does no start?

The plsqldev.exe process appears in the process monitor and disappears after a second.

Thats all. No splash screen, no GUI, simply nothing.

 

[mike]

I find my debug.txt files in the same directory that pl/sql developer is installed in. For example, C:\Program Files\PLSQL Developer 12.

You might try uninstalling it and reinstalling plsql developer. It's just a guess, but that's one thing I try when programs go crazy.

 

[Jaizkibel]

Hi Mike,

Thanks for your help.

I searched my whole file system for the debug.txt file without success.

I allready tried a uninstall/reinstall. This did not help.
But it seems to me an uninstall does not really clean up the system.
The PLSQL Developer directory remains unchanged in %APPDATA% and the registry entries for Allround Automations stay there as well.

I am thinking about a manual cleanup after the uninstall to get a really fresh new installation.

Marco, do you think this is a good idea?

 

[fcwojtul]

I have the same problem.
Manual cleanup, clean the registry, install 32-bit, 64-bit, reinstal, restart... Nothing help...
It's a big problem for me.

 

[fabrice]

Have you a licence for version 12?
If you try version 11, what's happen?

 

[fcwojtul]

Yes, I have a licence for version 12.
Version 11 doesn't start too.
I think McAfee maybe blocks?

 

[fcwojtul]

OK. Fixed. I created new windows profile and all works fine. It's not McAfee.

 

[fcwojtul]

After two weeks problem return ;/ I won't create another profiles. Anyone can help?

 

[fcwojtul]

Table Of Contents
plsqldev.exe_180316_122037.dmp

Faulting Thread

Faulting Module Information

Report for plsqldev.exe_180316_122037.dmp

Report for plsqldev.exe_180316_122037.dmp
Type of Analysis Performed Crash Analysis
Machine Name WTRZCIALKOWSKI
Operating System Unexpected
Number Of Processors 4
Process ID 13148
Process Image C:\Program Files (x86)\PLSQL Developer 12\plsqldev.exe
System Up-Time 00:00:00
Process Up-Time 00:00:05

Thread 0 - System ID 672
Entry point plsqldev!TMethodImplementationIntercept+16c927c
Create time 16.03.2018 12:20:32
Time spent in user mode 0 Days 0:0:1.62
Time spent in kernel mode 0 Days 0:0:1.359

Full Call Stack

Function Arg 1 Arg 2 Arg 3 Arg 4 Source
comdlg32!PrintSetupDlgProc+944 0022032a 00000110 001f0d0e 0019f728
user32!_InternalCallWinProc+2b 741f8190 0022032a 00000110 001f0d0e
user32!InternalCallWinProc+20 00000110 001f0d0e 0019f728 7ba76234
user32!UserCallDlgProcCheckWow+2f5 0022032a 00000110 001f0d0e 0019f728
user32!DefDlgProcWorker+c0 033a8740 00000000 00000110 001f0d0e
user32!DefDlgProcW+54 0022032a 00000110 001f0d0e 0019f728
user32!_InternalCallWinProc+2b 773b2320 0022032a 00000110 001f0d0e
user32!UserCallWinProcCheckWow+30a 773b2320 00000000 00000110 001f0d0e
user32!DispatchClientMessage+f0 033a8740 00000000 00000110 001f0d0e
user32!__fnDWORD+49 0019f044 00000020 0019fc5c 773a07b0
ntdll!KiUserCallbackDispatcher+36 75c70da8 0022032a 00000110 001f0d0e
win32u!NtUserMessageCall+c 0022032a 00000110 001f0d0e 0019f728
user32!SendMessageWorker+118 033a8740 00000000 0019f728 00000000
user32!InternalCreateDialog+a72 74190000 068a42e0 00000000 00250c9e
user32!InternalDialogBox+f8 00250c9e 741f8190 0019f728 00000001
user32!DialogBoxIndirectParamAorW+32 74190000 068a42e0 00250c9e 741f8190
comdlg32!PrintDisplaySetupDlg+109 0019f728 0019fc24 0019fbe8 00000000
comdlg32!PrintDlgX+185b0 0019fbe8 0019fbe8 00000000 00000000
comdlg32!PageSetupDlgX+1c4 06058610 0beaa8e8 00000001 0beabfa8
comdlg32!PageSetupDlgW+49 0019fbe8 00000000 00000000 00000054
plsqldev!TMethodImplementationIntercept+1edc26 0019fd04 0019fcb4 004f04c9 0019fd04
plsqldev!TMethodImplementationIntercept+53e09 0019fd38 004f064a 0019fd30 00000000
plsqldev!TMethodImplementationIntercept+540de 0019fd68 004f0573 0019fd4c 0b81b210
plsqldev!TMethodImplementationIntercept+5401d 005fce68 06311fcc 04ca3cd0 04ca3cd0
plsqldev!TMethodImplementationIntercept+61682 0019fda8 0070bd03 0019fda0 06311fcc
plsqldev!TMethodImplementationIntercept+26f5bc 0019fdb4 004f1577 0019fe30 0019fdc0
plsqldev!TMethodImplementationIntercept+54fcc 0019fe58 004eb6ac 0019fe50 00400000
plsqldev!TMethodImplementationIntercept+4f15b 0019fe7c 004e3184 0019fe74 01b657b4
plsqldev!TMethodImplementationIntercept+46c34 0019fea0 004e4894 0019fe94 009fe654
plsqldev!TMethodImplementationIntercept+48344 0019fec4 0019feac 004e4940 0019fec4
plsqldev!TMethodImplementationIntercept+483d2 0019fed8 0070b351 0019ff10 0019fee4
plsqldev!TMethodImplementationIntercept+26edbf 0019ff34 0040ab21 0019ff64 0b81b210
plsqldev!TMethodImplementationIntercept+56136f 0030c000 0019ffcc 0040bb94 0019ff80
plsqldev!TMethodImplementationIntercept+16c92dd 0030c000 75dd62a0 3e4e24fb 0019ffdc
kernel32!BaseThreadInitThunk+24 0030c000 6ec96cc1 00000000 00000000
ntdll!__RtlUserThreadStart+2f ffffffff 773b2ed2 00000000 00000000
ntdll!_RtlUserThreadStart+1b 01b657b4 0030c000 00000000 00000000

Exception Information
In plsqldev.exe_180316_122037.dmp the assembly instruction at comdlg32!PrintSetupDlgProc+944 in C:\Windows\System32\comdlg32.dll from Microsoft Corporation has caused an unknown exception (0xc000041d) on thread 0

Module Information
Image Name: C:\Windows\System32\comdlg32.dll Symbol Type: PDB
Base address: 0x00905a4d Time Stamp: Fri Nov 11 08:04:27 2016
Checksum: 0x00000000 Comments:
COM DLL: False Company Name: Microsoft Corporation
ISAPIExtension: False File Description: Common Dialogs DLL
ISAPIFilter: False File Version: 10.0.14393.479 (rs1_release.161110-2025)
Managed DLL: False Internal Name: comdlg32
VB DLL: False Legal Copyright:

 

[fcwojtul]

Ok, the problem is solved. The problem is access to the printer. When the default printer is a network printer to which you do not have access during the start of PLSqlDeveloper, the splwow64.exe process is started, which kills our process.
Solution: set as the printer the default printer to which you have access.
Tip: In Windows 10, your default can be the printer you last used. To turn on this mode, open Start and select Settings> Devices> Printers & scanners. Select the checkbox beside Let Windows manage my default printer.