Thanks for your response, Ted. My answers are embedded in your answers.
From: Ted Roche tedroche@gmail.com To: "profox@leafe.com" profox@leafe.com Sent: Friday, June 2, 2017 10:32 AM Subject: Re: "Record is not available" error in FPW 2.6
On Fri, Jun 2, 2017 at 6:26 AM, Michael Madigan mmadi10699@yahoo.com wrote:
For the first time in 24 years some users are getting the scrolling "Record is not available" in FPW 2.5. This error is extremely annoying because it can't be trapped by an error handler, and it has no error number.
That's because you're in a RETRY loop, and your REPROCESS settings aren't allowing it to fail and fall into the error handler.
From what I've read on the internet, this error never gets trapped, regardless. What would you recommend the reprocess be set to? There are 4 terminal services servers, 1 file server, and approximately 40 users. I have been told this happens on 2 unrelated programs each hosted on the same server, although this is not verified. This makes me think this may not be a software issue, hut instead a hardware issue.
With the same information, my first thought that this was a network/OS locking configuration problem.
This started when 5 new employees started.
Well, that's interesting! Are they using new machines? Are they configured the same way as the existing machines? Are they patched up-to-date? Are they running the same AV as the others? Same exclusions? That's where I'd look first -- the thing that last changed. They are using terminal services with the same setup profile as the other machines.
You're running 16-bit FPW 2.5? How do you install it for the new employees? How do you patch it? Are the runtime libraries the same? How about the CONFIG.FPW? CONFIG.NT? What's the networking protocol? Are you running SMB 1, 2, or 3? How about oplocks? The hardware guy insists that he's installed many servers with legacy foxpro programs and he doesn't want to change his oplocks settings The users are using the same shared exe. I know that's not optimal, but there wasn't an issue until today.
my config.fpw exclusive=offdeleted=onKEYCOMP = WINDOWSescape=onautosave=oncentury=onresource=offMEMLIMIT=60,4096,8192refresh = 1,1tablevalidate=0 Should I have autosave on and are the refresh settings correct?
It only happens for a few minutes then clears itself. It happens maybe 2 times a day for 5-10 minutes and everyone has to wait.
Sounds like a stale lock isn't getting cleared immediately. Hardware errors that clear up are more rare, though not impossible. Yes, as someone else has suggested, I should do an unlock immediately after the write. That may be part of my problem. I have also heard that locks on memo fields behave differently than other fields. I'm not sure if that's the case or not.
I think this is a hardware issue, where some rogue task is taking down the file server's or terminal server's performance.
I still don't get how this is "hardware." I shouldn't say "hardware", I should say, "not my software" issue or "system" In other words, an antivirus, backup, or other program. Coincidentally we had one server that had a gazillion errors in the system log that had a Citrix receiver program not loading and retrying and retrying. The guy fixed that and I thought the problem was gone, then two days later it happened again.
Well, yeah.
even though 2 separate, distinct programs are having issues and they don't have any interaction between them.
Don't they run the same runtimes, on the same OS, using the same network protocols, to talk to the same servers? Right but program one has like 5 users and the other has like 40, so the load is way less, and this program didn't receive the new users.