Uniface runtime errors: "Error opening files" "Error reading files"

Have you tried using UNC instead of mapped drive references?

Hi Gianni
About:
.\log\[NETWORK_NODE_NAME]_[PROCESS_PID].log)
The “network_node_name” ist the name of a server or the clients?

What you're describing sounds more like a network issue. In other words, the network (LAN/Wi-Fi) might go down briefly, causing the handles to become invalid. 

As Larry said, use UNC—it's more reliable.

BTW: About the  UNIxxxxx.log output: When ever Uniface got an error to use a Logfile, the fallback is the simple LOG-File in the working directory :-)

Hi Ingo & Larry,

first of all thanks for your replies, here our follow ups:

• It’s for sure that part of or broken sessions are generated from small hiccups in the network; network connectors are sometimes not properly locked into their position and users with a notebook are often moving their notebook on the desk causing their connection to go down briefly. We accept that causes but we do NOT think 100% of the broken sessions are generated in these ways.
• The “network_node_name” is the name of a server or the clients? Yes.
• You both answered directly or indirectly “UNC is more reliable”: under which perspective?
  We made a research about disk shares mapped to a letter before posting our “request for help” because I remember they to be discouraged to be used in the period WinVista / Win7; as of today we did NOT found any post or documents against them. Do you have any link to official documents or field experiences about “UNC are more reliable and better”?
• When a Uniface runtime is shared from a network disk the name UNIxxxxx.log would be better to be changed to [network_node_name]xxxxx.log to avoid potential log overlapping between sessions and to describe the origin of the log file in a more consistent way.

Best Regards,
Gianni

Hi Gianni,

In response to your question: “Do you have any link to official documents or field experiences about ‘UNC are more reliable and better’?”

Over the decades, I have reported many issues to Uniface support and in every situation when a drive mapping was in some way related to the problem, the suggestion was to “try UNC”. That being said, for simplicity, I always use network drive mappings in ASN (and INI) files, but when those fail or are problematic, I use UNC. I tried searching my closed tickets on the support site and it gave me documentation about every product that Rocket makes so completely useless -- that’s a separate issue altogether. I can’t find any documentation at the moment that states when to use UNC over drive mappings or that they are preferred -- I’m not even saying to use one over the other. Instead, I am suggesting to use one when the other doesn’t work. If the problem still persists, then you have to look elsewhere for a solution.

Hope this helps,

Larry