Hi Geza, questions:

• Do you have no error message on screen?
• Do you have steps to repro?
• PB version/build?
• O/S version?

Well, very little concrete to offer without details.

Have you tried to reproduce error running PowerBuilder's built-in Debugger?

If it only occurs runtime and it simple crashes hard without any info on screen => Consider running with /PBDEBUG enabled to capture log indicating exact spot where app crashes.

WARNING - /PBDEBUG: Performance degrades, log file is huge, and disk space is therefore consumed fast. Only use /PBDEBUG when really needed.

HTH /Michael

Dear Support!

Sorry, but I'm not speaking very good in English, sorry for my mistakes.

My program very old, but this crash have got in older versions of powerbuilder as well. The visual studio can catch the exception of older version of powerbuilder (10.5.2 several build, we are trying 11.5, 12.5, and now 17 versions, but this error have no solution) We are try several OS, for example, XP (the older version of powerbuilder), and windows 7, windows 8, and windows 10 as well.

The exception
pbdwe105.dll

in dwControlStyleDlgProc function

I think it is memory overflow, But the crash exception of powerbuilder 2017 cannot catch the old version of Visual studio (2008).

The event log from my computer:

Windows 10 Pro

-
-

1002
2
101
0x80000000000000

1446
Application
mcemer014.matrix2.meditcom.hu


-
PB170.EXE
17.2.0.1880
1170
01d53e385ae1632f
37
C:\Program Files (x86)\Appeon\PowerBuilder 17.0\PB170.EXE
0b22ca81-085e-4ef4-ba17-7dafa093154b


55006E006B006E006F0077006E0000000000



-------------------------------------------------------------------------------------------------------------

-
-

1002
2
101
0x80000000000000

2223
Application
mcemer014.matrix2.meditcom.hu


-
PB170.EXE
17.2.0.1880
1fd8
01d545e9898d8004
41
C:\Program Files (x86)\Appeon\PowerBuilder 17.0\PB170.EXE
b3d7d14b-8039-4572-8555-b9a2258a0cd8


55006E006B006E006F0077006E0000000000



-------------------------------------------------------------------------------------------------------------

And we are waiting my customers' machines event logs now. They promise tomorrow. Sorry.

- 
- 
   
  1002 
  2 
  101 
  0x80000000000000 
   
  1446 
  Application 
  mcemer014.matrix2.meditcom.hu 
   
  
- 
  PB170.EXE 
  17.2.0.1880 
  1170 
  01d53e385ae1632f 
  37 
  C:\Program Files (x86)\Appeon\PowerBuilder 17.0\PB170.EXE 
  0b22ca81-085e-4ef4-ba17-7dafa093154b 
   
   
  55006E006B006E006F0077006E0000000000 
  
  
  
  -------------------------------------------------------------------------------------------------------------
  
  - 
- 
   
  1002 
  2 
  101 
  0x80000000000000 
   
  2223 
  Application 
  mcemer014.matrix2.meditcom.hu 
   
  
- 
  PB170.EXE 
  17.2.0.1880 
  1fd8 
  01d545e9898d8004 
  41 
  C:\Program Files (x86)\Appeon\PowerBuilder 17.0\PB170.EXE 
  b3d7d14b-8039-4572-8555-b9a2258a0cd8 
   
   
  55006E006B006E006F0077006E0000000000 
  
  
  
  -------------------------------------------------------------------------------------------------------------

For better readable.

The xml is not attachable, and not viewable :(.

Hi Géza ;

    It sounds like this issue is also reproducible in many PB versions from your current 10.5.2 through to the almost end of the Sybase versions 12.5.x. So it sounds like your application might be the source of all your woes.

    Can you tell us ...

1) Have you run the Migration Assistant in a higher PB IDE version against your old PB 10.x App's source code to if possible coding issues exist before you migrate?

2) If you perform a Full Build ... is the compilation clean (no warnings or errors)?

3) Have you tried optimizing all your PBL's?

Regards ... Chris

Hi Chris!

Thanks for your help.

1) Have you run the Migration Assistant in a higher PB IDE version against your old PB 10.x App's source code to if possible coding issues exist before you migrate? 

NO, but I've tried now the previous source and got a lot notification. We are going to verify, but the most of notification is environment.pbmajorrevision, or monitor screen width and height or This match may be valid PowerScript syntax, but also matches an identifier in the search file. 

The second case for example in function

public function integer of_parsepath (string as_path, ref string as_out_dir, ref string as_out_file);
Long li_pos
li_pos = Pos(Reverse(as_path), "\")
If li_pos > 0 Then
as_out_dir = Left(as_path, Len(as_path) - li_pos)
as_out_file = Right(as_path, li_pos - 1)
Else
as_out_file = as_path
as_out_dir = ""
End If

Return 1
end function

 How to resolve they?

  

2) If you perform a Full Build ... is the compilation clean (no warnings or errors)?

No error, but there are a lot of warning, we will try to explode them.

3) Have you tried optimizing all your PBL's?

No, but we will optimize all pbl.

Regards, Géza

I think, the problem is another pbvm170.dll. We've installed the R3 1880, but the runtime use earlier version of pbvm170.dll, because it found another directory. After we deleted all earlier versions of runtime dlls, the number of crash significant lower.

We want to apply all of your offerings, but the remove of warnings is impossible.

The webservice has got inheritance, when i have generated object stub, the superclass variables are showing in the inherited class variables next to, but this inherited variables appear than own variable (redefine super variable), in the server of webservice these variables defined only the parent (super) class.

class A {

int x;

}

class B inherited from class A (

  int f;

}

B.f = 1 is possible, because its owner variable

B.x = 1 is possible, because the super class of variable

But the .NET webservice generate definition of x varisable in the b class, they appears owner variables, after we get warnings.