VFP App still shows in Taskmgr after quitting... and the .exe is still held open so can't be updated

[GriffMG]

I have some servers running multiple copies of a VFP app.
There might be twelve copies (individual .exe files in individual folders) on a server - scanning various databases
for requests for reports etc.

To update the .exe files I log on to the server, exit the apps, copy the new .exe files and restart the apps.
Pretty simple, only there is a problem. Sometimes I quit the app, it clearly closes and try to copy the new .exe
and the app is still open, still showing (now as a background task) in taskmgr. The copy fails and I can't update it.

This perhaps happens on a random three out of twelve copies on the same server.

I have found a workaround, open the old version again and then exit it, but does anyone know what the cause is?

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

I'm trying to cut down on the use of shrieks (exclamation marks), I'm told they are !good for you. ​

 

[Chris Miller]

Are you using a new Server? Since Win8 people report problems with file access, also for PACK. And sometimse it's a virus scanner acting on any file activity, including starting or ending executables. Since this is quite often reported I think it's also an OS thing, or it would only happen for people with a specific virus scanner, not sure how common that is.

Chriss

 

[GriffMG]

Hi

It happens on most of the servers from time to time, not, I think, on the remaining 2008 one, but definitely on 2012R2 and 2016 ones.

It's not an anti-virus thing, Taskmgr shows it as a background task after I quit it and it stays there for as long as it seems to fancy, running 1.2-2% of the cpu.

Have you seen it somewhere else? I have only seen it with VFP because I only have VFP apps running on the servers (that need updating).

Some of the apps 'auto-cycle' too, exit and restart after a few hundred iterations - in case there is a memory leak - and they auto-update in the process, and they NEVER
seem to have a problem overwriting the original .exe with a new one. But that could be because they are doing what I do manually, unload, reload, check for update, exit, update and reload again...

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

I'm trying to cut down on the use of shrieks (exclamation marks), I'm told they are !good for you. ​

 

[Chris Miller]

Hi Griff,

no, a process going into background before quitting is unusual. Are there any special DLLs or OCXes involved that need to unload?

Chriss

 

[GriffMG]

You might have something there, I usually only open a dll for a short period and close it explicitly.
But it could be an 'active component' of some sort, that looks like a possibility

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

I'm trying to cut down on the use of shrieks (exclamation marks), I'm told they are !good for you. ​