Hi all,
I am trying to trace down an annoying issue related to opening files in Uniface Runtime but unfortunately I am not able to identify an origin and a solution.
Here it is the scenario:
- A centralized server (Windows 2019 Datacenter) sharing a disk
- All users (normally 120 but up to 150 concurrent) refers to this server to startup a Uniface application in C/S mode
- Log is activated for all sessions ($ioprint = 1)
The system is up’n running 24x7 and issues I am going to list are happening mainly from 8:00 to 20:00 when most users are at work but there are cases also outside this timeframe like in the evening (20:00 to 24:00) and also in the middle of the night (00:00 to 06:00).
Issues:
- 20% (extimated) = daily Uniface sessions terminating without any signal or message or other… nothing!
- 79% = Session unable to write log file on shared disk (message:
ULOG Error: Failed to write to .\log\[NETWORK_NODE_NAME]_[PROCESS_PID].log) in this case a UNIxxxxx.log file is created into working directory
- 1% = Session unable to read shared disk(messages like:
ZIP error:(IOSERR_FILE_READ_WRITE) on [L:\prod97\common\usys\usys.uar] '' - File read/write failure
8003 - Open error on assignment file 'L:\prod97\common\adm\usys.asn'.
8008 - Assignment error: 'L:\prod97\adm\tarros97.asn') also in this cases a UNIxxxxx.log file is created into working directory
My feeling is that we are hitting against some system or network limit related to file opening or more generally to socket opening, but:
- On Uniface client side: $MAX_FILES = 255
- The shared server is largely configured for CPU and RAM; Datacenter version of Windows server has very high limit for whichever need
I’m looking here for suggestions, tips or tricks… thanks for any reply.
Best regards,
Gianni
