Why is proGetStack is not generating a protrace file

Why is proGetStack is not generating protrace file in the start-in directory ABL executable processes prowin32, prowin, _progres, _proapsv

PROTRACE files are not generated for processes started via published applications running on terminal server.

proGeStack only works for ABL clients (including Appserver, WebSpeed)
progetstack shows request to generate stack accepted in the command line:

The user running the process does not have rights to write to the start-in directory.
The Process Monitor logs verify that the user is trying to write to the protrace file and is receiving an ACCESS DENIED error from the file system.

Verify that the user that started the process has write permission to the start-in directory.
protrace files are created in the directory where the failing process was started from which is not necessarily the work directory

On Windows, antivirus packages can prevent protrace file generation when a Progress process dies.
If protraces are not being created consider testing excluding the Progress executables in DLC/bin from the antivirus.
 

Progress Articles:

 Which directory does Progress generate the core, procore and protraces files in?  
 What is the purpose of .PDB files?  
 The proGetStack command fails against a _mprosrv process  
  proGetStack does not work with PASOE agent