Bug 3635

Debugging of PB2019 from MS Visual Studio is FAILING 13 May, 2020

Vinay Chandrashekar
18 November, 2019
Product: PowerBuilder Category: Other
Version: 2019 Build:
Classification: Appeon bug Publishing: Public
Priority: P3
Status: Verifying Reason:
Vinay Chandrashekar 13 May, 2020
#17
VS2008_PB2019_Bug.zip (1263KB)

(In reply to Mark Lee @Appeon from comment #16)
Hi Vinay,
 
1. Currently, if you want to debug PB2019 from MS Visual Studio, you need to
manually start pb190.exe and then debug it via the Attach to Process mode as
I said before.
If you cannot use this method to debug the pb190.exe, we suggest that you
provide a reproducible test sample case for us to reproduce it.
 
2. You can also use the PB compile exe file instead of the pb190.exe file in
your Visual Studio project by setting the debugging path with the PB compile
exe file.
 
3. For the security of PB, the PB190.exe no longer provides the option to
use Visual Studio or other tools to auto debug PB 2019 IDE.

Regards,
Mark Lee
Hi Mark, Please find the attached re-producible steps. Let me know if any further details required.
Mark Lee @Appeon 06 May, 2020
#16
Hi Vinay,
 
1. Currently, if you want to debug PB2019 from MS Visual Studio, you need to manually start pb190.exe and then debug it via the Attach to Process mode as I said before.
If you cannot use this method to debug the pb190.exe, we suggest that you provide a reproducible test sample case for us to reproduce it.
 
2. You can also use the PB compile exe file instead of the pb190.exe file in your Visual Studio project by setting the debugging path with the PB compile exe file.
 
3. For the security of PB, the PB190.exe no longer provides the option to use Visual Studio or other tools to auto debug PB 2019 IDE.

Regards,
Mark Lee
Vinay Chandrashekar 05 May, 2020
#15
(In reply to Mark Lee @Appeon from comment #14)
Hi Vinay,

BTW, as for your case, you can also add the pb190.exe command in the batch
file to start PB 2019 to work it around. (see comment 13)

Regards,
Mark Lee
Hi Mark, We were using PB2017 and it is working in opening from VS2008 in debugging mode. As per the comments pb190.exe cannot be opened in the Batch file. Can you please check why the PB190.exe is not opening Regards, Vinay
Mark Lee @Appeon 05 December, 2019
#14
Hi Vinay,

BTW, as for your case, you can also add the pb190.exe command in the batch file to start PB 2019 to work it around. (see comment 13)

Regards,
Mark Lee
Mark Lee @Appeon 05 December, 2019
#13
pb190
Mark Lee @Appeon 03 December, 2019
#12
Hi Vinay,

Thanks for your update.
We will escalate this problem to our development team for further analysis.
We will need some time to figure it out, and we will get back to you if any progress we would make.

Regards,
Mark Lee
Vinay Chandrashekar 03 December, 2019
#11
Hi Mark,

In the case you provided the PB2019 should be started and perform the Attach Process. 

In our case the the batch file is started to open the VS2008 in which the DB environment is mentioned, following to that the PB will opened by clicking on Debug -----> Start Debugging (F5) in VS2008.

But in the case you mentioned the DB details will be missed and application fails to launch


Thanks,
Vinay
Mark Lee @Appeon 28 November, 2019
#10
Hi Vinay,

Sorry for the late reply.
1. Do you mean you use VS2008 to debug PB2019? If not, please let us know what Visual Studio version you are using.
2. Please use another machine to test and see if the same issue exists.
3. If you set the Attach property value to Yes in Visual Studio and then open PB2019 to debug, does it work? (see commend 8)
4. If you click Debug ----> Attach to Process ---> select the PB190.EXE mode in Visual Studio and then debug, can you work it around?  (see commend 9)
We look forward to hearing from you!

Regards,
Mark Lee
Mark Lee @Appeon 28 November, 2019
#9
attach to process
Mark Lee @Appeon 28 November, 2019
#8
set attach value to yes.
Vinay Chandrashekar 27 November, 2019
#7
Hi Mark,

Do we have any update :)

Thanks,
Vinay
Mark Lee @Appeon 20 November, 2019
#6
Hi Vinay,

Thanks for reporting this problem.
I will working on it and will get back to you soon.
Thanks for your patience and understanding.

Regards,
Mark Lee
Chris Pollach @Appeon 19 November, 2019
#5
Hi Vinay;
 
  Thank you for trying that aspect. I will now transfer this issue over to the main Support / Engineering team for their review of your issue and perhaps some insight as to why this happens under VS.

Regards ... Chris
Vinay Chandrashekar 19 November, 2019
#4
Hi Chris,

Same issue even after starting the VS in Admin mode. PB2019 is not opening.

Regards,
Vinay
Chris Pollach @Appeon 19 November, 2019
#3
Hi Vinay;

  Thank you for the DLL "Load" report.

BTW: Did you try launching the VS IDE as ADMIN to see if that works OK then for the PB IDE?

Regards ... Chris
Vinay Chandrashekar 19 November, 2019
#2
Hi Chris,

Please check the below output while launching the PB19.EXE.

'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\PowerBuilder 19.0\PB190.EXE'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\ntdll.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\kernel32.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\KernelBase.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\sysfer.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\user32.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\win32u.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\gdi32.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\gdi32full.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\msvcp_win.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\ucrtbase.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\imm32.dll'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Avecto\Privilege Guard Client\PGHook.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\advapi32.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\msvcrt.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\sechost.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\rpcrt4.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\sspicli.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\cryptbase.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\bcryptprimitives.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\cryptsp.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\rsaenh.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\bcrypt.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\shell32.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\cfgmgr32.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\SHCore.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\combase.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\windows.storage.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\profapi.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\powrprof.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\umpdc.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\shlwapi.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\kernel.appcore.dll'
'PB190.EXE': Loaded 'C:\Program Files\Manufacturer\Endpoint Agent\prntm.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\ole32.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\oleaut32.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\secur32.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\winspool.drv'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\msvcr120.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\msvcp120.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\propsys.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\IPHLPAPI.DLL'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\QIPCAP.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\dnsapi.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\ws2_32.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\nsi.dll'
The thread 'Win32 Thread' (0x46a4) has exited with code 1691025408 (0x64cb0000).
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBSYS190.DLL'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\wintrust.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\msasn1.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\crypt32.dll'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pblicui190.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\comdlg32.dll'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBLicense190.dll'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBCSI190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbapl190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBCMP190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBDTS190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbdwp190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBLIB190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBSHR190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBVM190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBDWE190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBDEV190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBEAS190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbscr190.DLL'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\msvcp100.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\msvcr100.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\riched20.dll'
'PB190.EXE': Loaded 'C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.18362.476_none_2e71e7f2278b4e9b\comctl32.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\wininet.dll'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Sybase\Shared\PowerBuilder\libglog.dll'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbgshare190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBSQL190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBDPP190.DLL'
'PB190.EXE': Loaded 'C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.18362.476_none_5f5cdad7821dc869\GdiPlus.dll'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBUDO190.DLL'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\uxtheme.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\wsock32.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\msimg32.dll'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Sybase\Shared\PowerBuilder\libjcc.dll', Binary was not built with debug information.
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBUIS190.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\version.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\oledlg.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\atl100.dll'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBORC190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbwed190.DLL'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\usp10.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\msls31.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\activeds.dll'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbdpl190.DLL'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Sybase\Shared\PowerBuilder\libjutils.dll', Binary was not built with debug information.
'PB190.EXE': Loaded 'C:\Program Files (x86)\Sybase\Shared\PowerBuilder\libjtml.dll', Binary was not built with debug information.
'PB190.EXE': Loaded 'C:\Program Files (x86)\Sybase\Shared\PowerBuilder\nlwnsck.dll', Binary was not built with debug information.
'PB190.EXE': Loaded 'C:\sybase\OCS-15_0\dll\libsybunic.dll', Binary was not built with debug information.
'PB190.EXE': Loaded 'C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9659_none_d08cfd96442b25cc\msvcr80.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\oleacc.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\winmm.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\adsldpc.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\Wldap32.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\winmmbase.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\dwmapi.dll'
'PB190.EXE': Loaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbjson190.dll'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pblicui190.dll'
'PB190.EXE': Loaded 'C:\Windows\SysWOW64\iertutil.dll'
'PB190.EXE': Unloaded 'C:\Windows\SysWOW64\iertutil.dll'
'PB190.EXE': Unloaded 'C:\Windows\SysWOW64\wininet.dll'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Sybase\Shared\PowerBuilder\libglog.dll'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBLicense190.dll'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBCSI190.DLL'
'PB190.EXE': Unloaded 'C:\Windows\SysWOW64\wintrust.dll'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBCMP190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBORC190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbwed190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbdpl190.DLL'
'PB190.EXE': Unloaded 'C:\Windows\SysWOW64\Wldap32.dll'
'PB190.EXE': Unloaded 'C:\Windows\SysWOW64\adsldpc.dll'
'PB190.EXE': Unloaded 'C:\Windows\SysWOW64\activeds.dll'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbapl190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBLIB190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBDEV190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBDTS190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbdwp190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBSQL190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbscr190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBDPP190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBUDO190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbgshare190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBEAS190.DLL'
'PB190.EXE': Unloaded 'C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBSYS190.DLL'
The thread 'Win32 Thread' (0x5a84) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x5320) has exited with code 0 (0x0).
The program '[6748] PB190.EXE: Native' has exited with code 0 (0x0).
Chris Pollach @Appeon 18 November, 2019
#1
Hi Vinay;

   Do receive any errors when you try to launch PB190.EXE from VS? If so, please attach to this ticket.

Also, PB2019 is compiled with VS2010 - so using VS2008 might be the issue.

Regards ... Chris
Vinay Chandrashekar 18 November, 2019
#0
*Phenomenon:
We have a DLL file which is developed in Microsoft Visual C++ 2008 and we used to start the Powerbuider2019 from Visual Studio by setting the debugging path with the PB2019 EXE. But it is failing to open PB2019.

Same is working fine for PB2017R3.

*Reproduce Steps:
Steps:
1 - Create a New Project in MS Visual Studio
2 - Go To Property Manager and Set the Debugging Command to set the path of PB2019.exe
3 - Start Debugging to open the PB2019.


Remarks:
Same steps can be followed to PB2017 which will work fine
OS:
Windows 10
Platform:
64-bit
Database Type:
Not Applicable
Database Version: