FW: fP error message file

[Kenneth Brody]

Quoting Don Coleman (Fri, 2 Dec 2005 11:50:35 -0500):
[...]
> > Windows 2000 Advanced Server & Win2000 & WinXP clients
> [...]
> > *** A filePro error has occurred ***
> > On file: \QS1\TODO\FILEPRO\SIG\LOCKFILE
> > line number:157
> > Prmessg: Cannot open E:\FP_SETUP_FILES\FP5.0.13\FP\LIB\ERRMSG
> > errno is 11
> >
> > filePro error number:1
> [...]
[...]
> > Note that the error 11 is the system error number regarding the failed
> > open on errmsg.  Assuming this is the native Windows version of
> > filePro (the error message indicated an "fp5.0.13" directory), then
> > error 11 is "resource temporarily unavailable".
>
> > It was a filePro error 1 that filePro was attempting to display.
[...]
> It appears that at least one other person (Richard Kreiss) has run into
> this issue.  Can you elaborate further as to what my problems/issues are
> in regard to this?
>
> On a Win network, for one or more of my fP files to be temporarily
> unavailable, might I assume this to be caused by a "network blip"?
> I wonder why it errors out on the occasional conditional lookup but not
> to one of the lookups that occurs every time the process runs.  This
> makes me think it is not a network blip.  Any suggestions on how to
> structure a test to pin this down?

Is there any pattern as to when/where this occurs?

> Also, What can I do to resolve fP being able to open/access the errmsg
> file?

Without any more details, my guess would be that, whatever caused the
error on the lockfile to occur prevented filePro from being able to open
the errmsg file.

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com