Hi.
I'm in a situation where I try to connect to ASE (v.16), through Powerbuilder IDE. I've created a database profile, but when I try to connect using Powerbuilder 2017 R3 or Powerbuilder 2019 R3, the IDE crashes...
In Windows Application Log I see the following for PB 2017 R3:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: PB170.EXE
P2: 17.2.0.1915
P3: 5df05d77
P4: PBSHR170.dll
P5: 17.2.0.1915
P6: 5df05d0b
P7: 80000003
P8: 00123f10
P9:
P10:
Attached files:
C:\Users\Majg\AppData\Local\Temp\WER185A.tmp.appcompat.txt
C:\Users\Majg\AppData\Local\Temp\WER3C4E.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_PB170.EXE_c4dd54b48b8f7db6aa50ad2dcab7eefbd65362fb_e72575ab_cab_25283c4d\memory.hdmp
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_PB170.EXE_c4dd54b48b8f7db6aa50ad2dcab7eefbd65362fb_e72575ab_cab_25283c4d\triagedump.dmp
WERGenerationLog.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_PB170.EXE_c4dd54b48b8f7db6aa50ad2dcab7eefbd65362fb_e72575ab_cab_25283c4d
Analysis symbol:
Rechecking for solution: 0
Report Id: 64872324-98d7-4669-9b55-edf803365176
Report Status: 2
Hashed bucket:
and for PB 2019 R3:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: PB190.EXE
P2: 19.2.0.2556
P3: 5f58e5f2
P4: PBSHR.dll
P5: 19.2.0.2556
P6: 5f58e56b
P7: 4000001f
P8: 0014b610
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_PB190.EXE_dbe4195420d64bcc2797e323ef69fca917d2bd1_21219bd6_1f14ab92
Analysis symbol:
Rechecking for solution: 0
Report Id: 63da933d-1a68-4c9b-b8f4-6566333c7b8a
Report Status: 2
Hashed bucket:
Does anyone has encountered such an issue? What can I do to resolve this problem? I will mention that I can connect to the same DB Server using PB 12.6.
Andreas.
As you saw I opened a case for that. I provide the link for anyone who wants to see what happened with that "problem".
https://www.appeon.com/standardsupport/search/view?id=5528
I don't know why I'm having these problem. But I will answer to points 1-4.
- Do not use the old "SYC" DB Client driver for ASE 15.0 or higher. Only use the new "ASE" driver in PB.
I'm not using the old SYC DB Client.
SQLCA.DBMS = "ASE Adaptive Server Enterprise"
SQLCA.Database = "indexing"
SQLCA.ServerName = "IID2003R2"
SQLCA.LogId = "sa"
SQLCA.AutoCommit = False
SQLCA.DBParm = "Release='15.5',CharSet='cp1253',AppName='PBNET_1252',Host='MAJG-PC-10'"
- Make sure that you are using the new ASE DB Client that came with your latest ASE DBMS (see your DBA team ).
Yes. I'm using ASE SDK (I think SAP renamed the client to ASE SDK). Not the last version, but as you can see in the support case, I've checked it with two different versions of ASE.
- Make sure that your DBParm specifies the correct ASE release number that exactly matches your environment.
I tried to connect with release 15.5 and 16. PB 2017 R3 & PB 2019 (R2 & R3) crash.
- Check your ASE DB CLient's SQL.ini file for the proper ASE DBMS settings (see your DBA team ).
If there was a problem to the ini, then it wouldn't be possible to connect using PB 12.6 (or qwerybuilder and the executable of my application that was produces using PB 2017 or PB 2019)... The problem is only in the IDE! And I saw it in three different pc.
Andreas.
Yes, I see the ticket. However, I cannot reproduce your connection issue on my ASE 16 based test PC's nor can our main Appeon support team. Please try a new PC / VM and a DB Client from your ASE 15.5 installation ( I do not have ASE 15.5 any longer on my test PCs).
Regards ... Chris