Kbase P123941: AppBuilder Progress 4GL Options are not saved
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  5/17/2007 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge Language Category: ADE Tools
Windows
SYMPTOM(s):
AppBuilder
Modifying Progress 4GL Options in AppBuilder (Options > Editing Options > Options)
Changes to DO/END Style (and other settings) are lost when AppBuilder is closed
Original settings are restored
AppBuilder settings are correct
UseSourceEditor=yes
EditorConfigPath points to the correct location
Expected files exist in <Working Directory>\ProEdit
p4gl.als
vslick.sta
vusrdefs.e
Both vslick.sta and vusrdefs.e are updated on a working PC when AppBuilder is closed
Neither vslick.sta nor vusrdefs.e are updated on a failing PC when AppBuilder is closed
FileMon displays the following entry when PROWIN32.EXE attempts to open vslick.sta for writing:
#### HH:MM:SS prowin32.exe:<PID> OPEN <Working Directory>\proedit\vslick.sta SHARING VIOLATION Options: Open Access: 0012019F
CAUSE:
Another process is touching vslick.sta and prevents PROWIN32.EXE from updating the file. By default, PROWIN32.EXE checks whether the state file (vslick.sta) is writable. If it is not updatable then AppBuilder will not attempt to save settings, resulting in neither vslick.sta nor vusrdefs.e being modified.
FIX:
Identify the process that is touching vslick.sta. If the process is system critical, disable it, and change the Progress 4GL Options in AppBuilder. Close the AppBuilder session and restart the process.
Commonly, the problem is caused by AntiVirus software. In this case, the problem can be avoided by adding the working directory/proedit directory/files within proedit directory to the lists of files/locations excluded from the AntiVirus scan list.