Intermittent UOPEN failures Options

[cdarling]

We are running on mvbase 2.1 PS1. We have several processes that run frequently during the day that interact with the DOS file system, mostly via unc network paths. Some of our processes have a network 'test' built-in where they UOPEN a known static file on the target system before attempting to UOPEN to read data for real. We get maybe one or 2 failures a week where the programs report they cannot UOPEN the static test file. Since these programs run on a schedule, they just stop and are then run at the next scheduled time. Usually the next run is just fine.

My question is what is causing these random UOPEN failures? Or, how can I figure out why they are happening. Since they are random and since the processes usually runs just fine on the next attempt, I am at a loss to figure out what the issue is.

The server mvWorkstation is running on is Windows Server 2003 SP2.

I suspect that it may be the code in mvWorkstation is either old or not handling some type of event properly, but I have no way to know.

We have a medium to large network with dedicated network support staff. They say they don't see any obvious network issues.

Any suggestions?

[Claude]

Run a modified version of the same program which will stop and leave the error on the port.