Kbase P22024: Errno=22 reading PROMSGS file, it may have been deleted due to possible file contention
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/07/2005 |
|
Status: Verified
FACT(s) (Environment):
Citrix MetaFrame XP for Windows 2000 Terminal Server
Windows NT 32 Intel/Windows 2000
SYMPTOM(s):
The latest Microsoft and Citrix service packs have been installed on every machine that is member of the Citrix Server Farm.
Errno=22 reading PROMSGS file, it may have been deleted
Progress application files are deployed on each and every member of the Citrix Server Farm using the same path
The application's registry key or .ini file are configured to reflect the same Progress installation directory and application propath
Supported configuration of Progress
Progress was not installed as NetSetup on the Citrix Farm
CAUSE:
The PROMSGS file can be accessed a vast amount of times during a normal client session, if you multiply this by the number of clients using this install on a TS/MF configuration along with the database, the resulting Network overload can then cause file contention and the above errors received.
FIX:
There are two possible Solutions to this issue, the first is strongly recommended for reasons that become apparent in the second.
Option 1: Will alleviate both the Network overload and the file contention
0. Make sure Progress IS installed local to the Terminal Server/MetaFrame machine.
1. Copy the promsgs file located in the %DLC% folder from the main installation machine to the local machine.
2. Define the PROMSGS environment variable and point this to the local copy of the promsgs file on each machine.
3. Set the -T startup parameter on the Client machines to point to where the local copy of promsgs are stored.
Option 2: It is not always possible to use the local machine. The following will therefore alleviate the file contention but increase traffic:
0. Make sure Progress IS installed local to the Terminal Server/MetaFrame machine.
1. Create an individual user directory for each user on the TS/MF machine
2. Copy the PROMSGS file from the %DLC% directory to each of the individual directory's for each user
3. Set the PROMSGS variable in Environment/Registry/INI (depending which is used) to point to each individual directory for each user.
4. Set the -T startup parameter to point to where the individual copy of promsgs are stored
What Option 2 will now facitilitate is to allow each user to have their own copy of PROMSGS on the Terminal Server / MetaFrame machine, therefore not causing anymore file contention on this file.