FW: fP error message file

[Don Coleman]

-----Original Message-----
From: Kenneth Brody [mailto:kenbrody at bestweb.net] 
Sent: Saturday, December 03, 2005 1:02 PM
To: Don Coleman
Cc: filePro List
Subject: Re: FW: fP error message file

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.

--


Ken:

No pattern that I can discern.  The errors generally occur 1-10 times per
day and the file being referenced in the error are reference files which are
only infrequently updated.  The lookup to those files is not protected.
This client has 30-50 clients in fP throughout the day and we are not
getting complaints about errors or "network blips" from other users, just
those using the scanning process at one of three work stations.

Don Coleman