Kbase P112266: PROPATH setting in the Windows Registry is intermittently reset to its default value
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/5/2006 |
|
Status: Unverified
FACT(s) (Environment):
Windows NT 4.0 Terminal Server Edition
Windows 2000
Windows 2003
SYMPTOM(s):
Using PROPATH value stored in the Registry
PROPATH is periodically reset to the default value
Loss of user modifications to PROPATH causes programs to fail
Only PROPATH value stored in HKEY_CURRENT_USER is changed; HKEY_LOCAL_MACHINE is not touched
PC has been configured to run as a Terminal Server
Terminal Server is running in Application mode
USERINIT.EXE identified as the process making the adjustments to the PROPATH Registry value
USERINIT.EXE process is executed by Windows when a user logs on to the computer, and runs various network and user-setup related tasks to initialise the user's session on the computer
etwork
CAUSE:
This problem is not caused by Progress. Progress will only modify the Registry when instructed i.e. when a user modifies settings or programmatically via 4GL.
The behaviour is caused by the registry compatibility mechanism that is included in Terminal Server and Terminal Services in Application Server mode, which reverts the settings to the default settings when it detects that the settings on the server are newer than those in a user's profile.
FIX:
Refer to the following Microsoft article for more information about the problem and how to fix/workaround it:
Programs Can Revert to the Default Settings on Terminal Server
http://support.microsoft.com/default.aspx?scid=kb;EN-US;297379
For further assistance, please contact Microsoft Technical Support