Snap Ins Not Reporting Complete

[UWPVIOLATOR]

FOG 1.4.4
Ubuntu 16.04

This has been an issue for awhile. After a snapin deploys and installs as part of the imaging process. You can see in the logs as the snapin finishes then it reboots. After the reboot it then tries to do the snapin all over again. It does appear to only be this 1 snapin. Zenworks Agent. It worked just fine for us for a long time but seems like 1.4.4 did something to it. Suggestions?

 2/12/2018 11:46 AM SnapinClient C:\Program Files (x86)\FOG\tmp\ZenAgent.64.Complete.11.4.3.exe
 2/12/2018 11:46 AM Bus Emmiting message on channel: Notification
 2/12/2018 11:46 AM SnapinClient Starting snapin
 2/12/2018 11:47 AM SnapinClient Snapin finished
 2/12/2018 11:47 AM SnapinClient Return Code: 0
 2/12/2018 11:47 AM Bus Emmiting message on channel: Notification
 2/12/2018 11:47 AM Service ERROR: Unable to run module
 2/12/2018 11:47 AM Service ERROR: The process cannot access the file 'C:\Program Files (x86)\FOG\tmp\ZenAgent.64.Complete.11.4.3.exe' because it is being used by another process.

After Reboot tries to install again

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 2/12/2018 11:51 AM Client-Info Client Version: 0.11.12
 2/12/2018 11:51 AM Client-Info Client OS:      Windows
 2/12/2018 11:51 AM Client-Info Server Version: 1.4.4
 2/12/2018 11:51 AM Middleware::Response Success
 2/12/2018 11:51 AM SnapinClient Running snapin ZenAgent 11.4.3 x64
 2/12/2018 11:51 AM Middleware::Communication Download: http://fogserver/fog/service/snapins.file.php?mac=10:60:4B:75:37:98&taskid=151804
 2/12/2018 11:52 AM SnapinClient C:\Program Files (x86)\FOG\tmp\ZenAgent.64.Complete.11.4.3.exe
 2/12/2018 11:52 AM Bus Emmiting message on channel: Notification
 2/12/2018 11:52 AM SnapinClient Starting snapin
 2/12/2018 11:53 AM SnapinClient Snapin finished
 2/12/2018 11:53 AM SnapinClient Return Code: 0
 2/12/2018 11:53 AM Bus Emmiting message on channel: Notification
 2/12/2018 11:53 AM Service ERROR: Unable to run module
 2/12/2018 11:53 AM Service ERROR: The process cannot access the file 'C:\Program Files (x86)\FOG\tmp\ZenAgent.64.Complete.11.4.3.exe' because it is being used by another process.

[Joe Schmitt]

@UWPVIOLATOR This has been fixed in v0.11.14, which will be released with the next server RC. I’d still recommend using process-explorer to find out why the file is locked though.

To get v0.11.14 you can either wait for the next server release, or download it from here: https://github.com/FOGProject/fog-client/releases/tag/0.11.14

[Sebastian Roth]

@UWPVIOLATOR said:

… The process cannot access the file …

Maybe access rights on that directory being too restrictive? Are you able to deploy other snapins?

[UWPVIOLATOR]

@sebastian-roth Yes everything else works and this snapin did install but it never tells FOG so the task never clears and then the next time the client does a check in it will try to install all over again.

[Joe Schmitt]

@UWPVIOLATOR can you check the file for locks? (That is, find what processes are still using that file)

Ultimately you are right that this is a bug, and something that should be addressed. However finding what is locking the file should at least give you a work around until I can patch it.

[UWPVIOLATOR]

@joe-schmitt How can I check? Are you saying that after the snapin runs (which takes a few min) that FOG is trying to delete the snapin but cant because its still in use?

[Joe Schmitt]

@UWPVIOLATOR correct, once the client finishes running the snapin another process seems to still be using it (according to the log). You can use a utility called Process Explorer (https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer) to check. Please check for the lock right after/when the client produces that error message (or as soon as possible after it occurs).

For more info on using that tool: https://www.techsupportalert.com/content/how-find-out-which-windows-process-using-file.htm

[Joe Schmitt]

@UWPVIOLATOR This has been fixed in v0.11.14, which will be released with the next server RC. I’d still recommend using process-explorer to find out why the file is locked though.

To get v0.11.14 you can either wait for the next server release, or download it from here: https://github.com/FOGProject/fog-client/releases/tag/0.11.14