Do you know if there is any problem with PB and the windows user profile?

We use API windows functions a OleOjects...

When the crash happens, if we access in the same PC with another user and do the same operation 
in the application, it works.

It seems that the crash happens more often to users who keep the windows session open several days.

We have included a GarbageCollect() instruction when the user closes the application in case 
the problem was due to memory leaks. But the problem continues to occur from time to time.

Regards.

I just realized that we ourselves declare the function like this too:

Function long ShellExecute( long hwnd,  string lpOperation, string lpFile, string lpParameters,  string lpDirectory,  integer nShowCmd) Library "shell32.dll" alias for "ShellExecuteW" 

but ... 

shouldn't that be:

Function long ShellExecute( long hwnd,  ref string lpOperation,  ref string lpFile, ref string lpParameters,  ref string lpDirectory,  integer nShowCmd) Library "shell32.dll" alias for "ShellExecuteW"

At least that's what msdn suggests: https://docs.microsoft.com/en-us/windows/win32/api/shellapi/nf-shellapi-shellexecutew, 

I'm not sure if this might be a problem, as it seems to work for us without the "ref" but maybe it's a good idea to change the calls also to include the "ref" word when calling the function from Powerscript.
I'll give it a try tomorrow.

HINSTANCE ShellExecuteW(
  HWND    hwnd,
  LPCWSTR lpOperation,
  LPCWSTR lpFile,
  LPCWSTR lpParameters,
  LPCWSTR lpDirectory,
  INT     nShowCmd
);

From your debug log, I'm wondering what you are doing in the itemchanged() event as I also see an AcceptText().

Could you post the itemchanged() code?

Thanks Roland, I am very grateful to receive the help of a master like you.

I have an example of how to use that function:

http://www.topwizprogramming.com/freecode_runandwait.html

Hi,

The random problem continues, could it be a problem with ShellExecute function and KERNELBASE.DLL?

I have found several entries on the web related to this ...

Or there may be some error in the code:

We have defined a user object to include the api call (Local External Functions) and we are using a global function that we call to open the file indicated 
by parameter.

forward

global type n_cst_api_windows from nonvisualobject
end type
end forward

global type n_cst_api_windows from nonvisualobject autoinstantiate
end type

type prototypes
/* JIR (10/10/2019) EV119097: Pasamos a utilizar la versión UNICODE de las funciones del API de Windows */
FUNCTION long ShellExecute &
    (ulong ihwnd ,string lpszOp, &
     string lpszFile, string lpszParams, &
     string lpszDir, int wShowCmd) &
LIBRARY "shell32.dll" ALIAS FOR "ShellExecuteW"
end prototypes

on n_cst_api_windows.create
call super::create
TriggerEvent( this, "constructor" )
end on

on n_cst_api_windows.destroy
TriggerEvent( this, "destructor" )
call super::destroy
end on

global type f_abrir_documento from function_object
end type

forward prototypes
global function integer f_abrir_documento (string as_fichero)
end prototypes

global function integer f_abrir_documento (string as_fichero);/*************************************************************************************
* Funcion        : f_abrir_documento
* Descripción    : Muestra el contenido del fichero que se pasa como parametro. Abriendolo
*                      a partir del programa que tenga asociado la extension. Si no encuentra una
*                      asociación se ejecuta el "Abrir con ..." de Windows
*
*                      El último argumento es el estilo de la ventana:
*
*                        SW_HIDE 0                            SW_SHOWNORMAL 1                     SW_SHOWMINIMIZED 2            
*                        SW_SHOWMAXIMIZED 3            SW_SHOWNOACTIVATE 4                SW_SHOW 5                    
*                        SW_MINIMIZE 6                    SW_SHOWMINNOACTIVATE 7            SW_SHOWNA 8                    
*                        SW_RESTORE 9                    SW_SHOWDEFAULT 10            
*
* Argumentos    :    as_fichero
*
* Devuelve        :     -1 Error
                        -2 No existe el fichero
                         1 Ok
*
**************************************************************************************
*        Fecha              Autor                    Comentarios
*    --------------        ----------        -------------------------------------
*    11/10/2019            JIR            EV119097: Versión Inicial        
************************************************************************************/
string ls_Null, ls_msg
long   ll_rc

if f_es_vacio(as_fichero) then Return -1
If Not FileExists(as_fichero) then Return -2

SetNull(ls_Null)

TRY    
    ll_rc = gnv_API.ShellExecute (handle( this ), "open", as_fichero, ls_Null, ls_Null, 1)
CATCH (runtimeerror er1)
    messageBox("Atención", "Se produjo un error de ejecución (ShellExecute) al abrir el fichero " + as_fichero)
    RETURN -1
END TRY

if ll_rc = 27 OR ll_rc = 31 then

    TRY    
        Run ('rundll32 shell32,OpenAs_RunDLL ' + as_fichero)
    CATCH (runtimeerror er2)
        messageBox("Atención", "Se produjo un error de ejecución (rundll32) al abrir el fichero " + as_fichero)
        RETURN -1
    END TRY

elseif ll_rc <= 32 Then

    Choose Case ll_rc
        Case 0
            ls_msg = "The operating system is out of memory or resources"
        Case 2
             ls_msg = "El fichero no existe"
        Case 3
             ls_msg = "Ruta no encontrada"
        Case 5
             ls_msg = "El sistema operantivo no permite el acceso al fichero indicado"
        Case 8
             ls_msg = "No hay suficiente memoria para completar la operación"
        Case 10
             ls_msg = "Versión incorrecta de Windows"
        Case 11
             ls_msg = "Invalid EXE file or error in EXE image"
        Case 12
            ls_msg = "Application was designed for a different operating system"
        Case 13
            ls_msg = "Application was designed for MS-DOS 4.0"
        Case 15
            ls_msg = "Attempt to load a real-mode program"
        Case 16
            ls_msg = "Attempt to load a second instance of an application with non-readonly data segments"
        Case 19
            ls_msg = "Attempt to load a compressed application file"
        Case 20
            ls_msg = "Dynamic-link library (DLL) file failure"
        Case 26
            ls_msg = "A sharing violation occurred"
        Case 27
             ls_msg = "Asociación a fichero no válida o incompleta"
        Case 28
             ls_msg = "The DDE transaction could not be completed because the request timed out"
        Case 29
             ls_msg = "DDE transaction failed"
        Case 30
             ls_msg = "The DDE transaction could not be completed because other DDE transactions were being processed"
        Case 31
             ls_msg = "No existe ninguna asociación con la extensión del fichero"
        Case 32
             ls_msg = "DLL not found"
        Case Else
             ls_msg = "Unknown error"
    End Choose
    
    MessageBox("Error", ls_msg)
    return -1
    
end if

Return 1
end function

Thanks for your help.

If you can narrow it down to a particular Win API function, post it here. There is a good chance the declaration is wrong.

Hello,

We have detected that it happens when the user's Windows session has been open for several days, 
because when the user restarts the session on Windows it seems to stops crashing.


- 
- 
   
  1000 
  2 
  100 
  0x80000000000000 
   
  70848 
  Application 
  PCE0236.anecval.local 
   
  
- 
  planning.exe 
  11.0.0.0 
  5ce82bed 
  KERNELBASE.dll 
  6.1.7601.24524 
  5d8045b2 
  c0000005 
  0000845d 
  7a4 
  01d5842927b6d29e 
  C:\Planning\planning.exe 
  C:\Windows\system32\KERNELBASE.dll 
  878ab65e-f01c-11e9-8ded-6cf0492a8224 
  
  
 

I'm not sure, but the error seems to occur when a value is autocompleted in a field with DDDW and 
the user changes to another field without accepting the value (NO AcceptText)

End event +ITEMCHANGED for class U_DW_ANE, lib entry U_DW_ANE
                    Executing object function +DESTROY for class DWOBJECT, lib entry _TYPEDEF
                      Executing instruction at line 2557
                      Executing object function __DESTROY_OBJECT for class DWOBJECT, lib entry _TYPEDEF
                        Executing system dll function
                      End class function __DESTROY_OBJECT for class DWOBJECT, lib entry _TYPEDEF
                      Executing instruction at line 2558
                    End class function +DESTROY for class DWOBJECT, lib entry _TYPEDEF
                  End class function ACCEPTTEXT for class DW_1, lib entry W_PLANNING_COMERCIAL_CONSULTA
                  Executing instruction at line 1
                  Executing instruction at line 2
                End event +LOSEFOCUS for class U_DW_ANE, lib entry U_DW_ANE
                Executing object function +DESTROY for class DWOBJECT, lib entry _TYPEDEF
                  Executing instruction at line 2557
                  Executing object function __DESTROY_OBJECT for class DWOBJECT, lib entry _TYPEDEF
                    Executing system dll function
                  End class function __DESTROY_OBJECT for class DWOBJECT, lib entry _TYPEDEF
                  Executing instruction at line 2558
                End class function +DESTROY for class DWOBJECT, lib entry _TYPEDEF

Hi Roland,

I have look for ";Ansi" on project libraries and I have found same functions declarated with ";ANSI" (in our own libraries and in PFC libraries). Could this be the problem?

Regards.

PB7 uses ANSI (single byte) strings while PB10 and higher use Unicode (double byte) strings.

I would check for Windows API functions that might be causing it to abort.

Some functions that take a string also have a length argument. Some are character length and some are byte length so you have to review the documentation for the function to make sure it is correct. Also, make sure you are using the W version of functions instead of the A version. The conversion process adds ";ANSI" to the end of external function declarations. That won't be needed if you use the W version.

Thanks for the answers.

We are going to test executing the application in the compatibility mode proposed by windows.


I keep you informed. 
Regards.

Hi Julian;

  FYI: https://social.technet.microsoft.com/Forums/windows/en-US/9e83c5fc-caa4-4d64-82a2-342bda0b8673/exception-code-0xc0000005?forum=w7itproappcompat

  FWIW: Try using the RHMB on your PB App's EXE and using W10's "Troubleshoot compatibility" option.

Regards ... Chris

Hi Julian;

   I wonder if the cause of these random "not responding" errors are due to either a network or more likely DB resource issue. For example, a long table / area lock that is not getting released? Anything suspicious in the O/S event and/or DB logs around the time this happens?

Regards ... Chris

Hello David:

We run Powerbuilder Runtime Packager, export the dlls in a new folder and copy it to pc user in the app directory.

How are you building your exe?

Do you have the same version of PB runtime DLLs deployed as used on the build machine?