This articles describes several causes for an application that receives file status 35 on an OPEN OUPUT of a disk file.
The application runs on a Windows XP client PC and occasionally receives file status 35 (File Not Found) on OPEN OUTPUT. The statement is creating a new disk file on a Windows 2003 Server which is accessed by the client via a mapped drive. The error happens unpredictably and is not reproducible at will.
There are many reasons why an OPEN OUTPUT of a new disk file may produce file status 35 (or 94,20 if you’re using 74 status codes). The following items may apply not only to Windows, but to any operating system.
Based on the intermittent nature of the problem reported in this case, causes 5 and 6 are likely candidates. In other cases investigating each of these should reveal the cause of the error.