"cannot write to a read only file" and "unable to process error& 1

[apelecanus]

has anyone seen these errors??

we had foxpro for dos 2.5 exe and data running on a novell 3.12 server with the desktops and printers running on win2k network (and office xp on the desktops). then the novell server decided to commit suicide.

so we moved everything onto the win2k file server (exes and data joined everything else on the win2k fileserver.) things tested fine (although testing was hurried) printing worked, files were being updated, etc.

over the past two weeks we've been getting "cannot write to a read only file" and "unable to process error" boxes returned to users having more than one cmd window open. ending task on the cmd windows and eventually rebooting seems to be the only relief....

the fox related directories are all read/write for everyone as are all of the dbfs/exes individually. most printing is done to lpt1.

anyone have any ideas why we're getting these errors?

thanks,

ann

 

[suttonae]

Just a thought, perhaps your server file locks aren't clearing quickly enough?

 

[apelecanus]

additional information: we do no file locking within our programs. we have a programmatic record locking system in place which is not the issue. the errors returned are in the dreaded red box and they offer no explanation other than the error message.

 

[suttonae]

It may not be relevant, but we have seen this with MS Excel files and our Novell 4.11 server. Additionally we have issues with Novell and the Network Client and Windows 2000 workstations, not what is listed here though.

 

[DSummZZZ]

You may have a temp files issue. By temp files issue, I mean that the app may not have sufficient write/erase rights where the temp files are being written. Try using a different directory where the name was DOS 8.3 locatable instead of the default directory where long file name support is required. Use a 'TMPFILES= .....' setting in your CONFIG.FPW file to set it to something like C:\TEMP.
Dave S.