This bug still persists in version 7.6. I included a full set of tests of a minimum viable setup to reproduce the bug months ago as well as details on the last version that permitted launching from a 3rd party file manager, menu, or any other process. As it has been 20 months, it seems unlikely this bug will be fixed.Attempting to run FreeFileSync.exe from another process on Windows yields the following error:
---------------------------
FreeFileSync - An exception occurred
---------------------------
Cannot open file "GlobalSettings.xml".
Error Code 32: The process cannot access the file because it is being used by another process. (CreateFile)
This does not occur from a batch file but does occur when run from another EXE. I found the issue while packaging the PortableApps.com Format package of the app and thought it may be due to an interaction with our launcher, but created a simplified NSIS-based EXE that only does one thing (ExecWait '$EXEDIR\FreeFileSync.exe') and it yields the above error as well. We may be able to code around it in our package, but I'd wager this will cause issue when run from some other scheduling software and alternate Windows Start menus.critternyc
BUG: Starting FreeFileSync.exe from another process yields Error Code 32
-
- Posts: 27
- Joined: 11 Dec 2004
-
- Posts: 27
- Joined: 11 Dec 2004
This bug still persists in 7.6. I have complete details to reproduce in the report from 9 months ago: viewtopic.php?t=1716&p=6995#p6995
This bug is now 20 months old and still doesn't allow FreeFileSync to be launched from 3rd party file managers, menus, and other processes.
This bug is now 20 months old and still doesn't allow FreeFileSync to be launched from 3rd party file managers, menus, and other processes.
-
- Posts: 27
- Joined: 11 Dec 2004
This bug still persists in FreeFileSync 7.8. The bug is now 22 months old. Complete details on how to reproduce it along with source code and a stub launcher to do so were provided 11 months ago.
If you'd like to use FreeFileSync with a start menu of your choice, a file manager of your choice, or any other software, you can obtain version 6.2, the last properly working version, from here: http://portableapps.com/apps/utilities/freefilesync-portable
If you'd like to use FreeFileSync with a start menu of your choice, a file manager of your choice, or any other software, you can obtain version 6.2, the last properly working version, from here: http://portableapps.com/apps/utilities/freefilesync-portable
- Posts: 3
- Joined: 1 Apr 2012
I'm sorry I made a new thread about this, I didn't assume this would be a persistent issue since it never happened to me before, and I've been updating FFS promptly every month.
I'm baffled as to why this particular issue hasn't been tracked down and addressed yet. I mirror the same experience others have posted here. That said, I have not met this error today (I run and closed FFS over 10 times, no issues), and as I mentioned in the thread I created, this only happened yesterday in one of my PCs after having used FFS several times in the last few days since the 7.8 update, and I haven't had any issues with FFS on the other PCs with very similar software setups. It's funny how it seemingly manifested at random only yesterday, intermittently too.
Other than restarting my system (or rather, turned it off yesterday to turn it on today), no changes were made that could possibly interfere with the software's behavior, after or before I'd say. I might as well add that this didn't ruin my day or anything, and I will continue to use this amazing utility as long as this bug doesn't become crippling for daily use.
I'm baffled as to why this particular issue hasn't been tracked down and addressed yet. I mirror the same experience others have posted here. That said, I have not met this error today (I run and closed FFS over 10 times, no issues), and as I mentioned in the thread I created, this only happened yesterday in one of my PCs after having used FFS several times in the last few days since the 7.8 update, and I haven't had any issues with FFS on the other PCs with very similar software setups. It's funny how it seemingly manifested at random only yesterday, intermittently too.
Other than restarting my system (or rather, turned it off yesterday to turn it on today), no changes were made that could possibly interfere with the software's behavior, after or before I'd say. I might as well add that this didn't ruin my day or anything, and I will continue to use this amazing utility as long as this bug doesn't become crippling for daily use.
- Posts: 1
- Joined: 7 Feb 2016
Hello!
I beg pardon for my English. I use Google Translator ...
This problem, error code 32, came to me too.
I take LiberKey ...
And, wrote FreeFileSync Portable small launcher for windows.
The utility needs wider testing.
Distributed freely without any conditions.
Download FreeFileSyncLaunch
Hash List
MD5 ab5d8cc39b53f6a45f401c0f0cfaabc1
SHA1 0b1e5d8d19bf0588d2374a293046062cbb3a8ef0
SHA256 25406109179ada87d5c74680399edba91ab0918f12a04972929e15ed1b7419d7
I would appreciate your feedback.
I beg pardon for my English. I use Google Translator ...
This problem, error code 32, came to me too.
I take LiberKey ...
And, wrote FreeFileSync Portable small launcher for windows.
The utility needs wider testing.
Distributed freely without any conditions.
Download FreeFileSyncLaunch
Hash List
MD5 ab5d8cc39b53f6a45f401c0f0cfaabc1
SHA1 0b1e5d8d19bf0588d2374a293046062cbb3a8ef0
SHA256 25406109179ada87d5c74680399edba91ab0918f12a04972929e15ed1b7419d7
I would appreciate your feedback.
-
- Posts: 27
- Joined: 11 Dec 2004
FreeFileSync 7.9 is still affected by this bug. The location of this bug report is now directly linked from the app pages for FreeFileSync on PortableApps.com and PortableFreeware.com.
- Posts: 2
- Joined: 22 Feb 2016
A couple of possible workarounds:
Symenu - freeware that is a great portable menu launcher and a Start Menu replacer to organize your applications quickly and easily.
Web address is http://www.ugmfree.it/
Here is what the author of Symenu gave me as possible fixes and they worked for me.
First method:
-Create a batch file and name it: SyMenuStartFreeFileSync.bat
-Place the following code inside the batch file: start "" "FreeFileSync.exe"
-Save the batch file to the FreeFileSync root folder
-Launch the new batch file instead of the normal FreeFileSync.exe file
Second method: If using Symenu app launcher
- Go to SyMenu configuration form
- Add a new Windows command element
- Give it a clear name such as FreeFileSync CMD
- In the command box put the command
start "" plus the full path or your FFS executable replacing the drive
unit letter with the SyMenu universal unit identifier (d: becomes #:)
In my PC the command box contains this string
start "" #:SyMenuProgramFilesSPSSuiteSyMenuSuiteFreeFileSync_spsFreeFileSync.exe
Here is an example batch file to download:
Symenu - freeware that is a great portable menu launcher and a Start Menu replacer to organize your applications quickly and easily.
Web address is http://www.ugmfree.it/
Here is what the author of Symenu gave me as possible fixes and they worked for me.
First method:
-Create a batch file and name it: SyMenuStartFreeFileSync.bat
-Place the following code inside the batch file: start "" "FreeFileSync.exe"
-Save the batch file to the FreeFileSync root folder
-Launch the new batch file instead of the normal FreeFileSync.exe file
Second method: If using Symenu app launcher
- Go to SyMenu configuration form
- Add a new Windows command element
- Give it a clear name such as FreeFileSync CMD
- In the command box put the command
start "" plus the full path or your FFS executable replacing the drive
unit letter with the SyMenu universal unit identifier (d: becomes #:)
In my PC the command box contains this string
start "" #:SyMenuProgramFilesSPSSuiteSyMenuSuiteFreeFileSync_spsFreeFileSync.exe
Here is an example batch file to download:
- Posts: 2
- Joined: 22 Feb 2016
Here are a couple of corrections to this post:A couple of possible workarounds:
Symenu - freeware that is a great portable menu launcher and a Start Menu replacer to organize your applications quickly and easily.
Web address is http://www.ugmfree.it/
Here is what the author of Symenu gave me as possible fixes and they worked for me.
First method:
-Create a batch file and name it: SyMenuStartFreeFileSync.bat
-Place the following code inside the batch file: start "" "FreeFileSync.exe"
-Save the batch file to the FreeFileSync root folder
-Launch the new batch file instead of the normal FreeFileSync.exe file
Second method: If using Symenu app launcher
- Go to SyMenu configuration form
- Add a new Windows command element
- Give it a clear name such as FreeFileSync CMD
- In the command box put the command
start "" plus the full path or your FFS executable replacing the drive
unit letter with the SyMenu universal unit identifier (d: becomes #:)
In my PC the command box contains this string
start "" #:SyMenuProgramFilesSPSSuiteSyMenuSuiteFreeFileSync_spsFreeFileSync.exe
Here is an example batch file to download: Wylie
The line
start "" #:SyMenuProgramFilesSPSSuiteSyMenuSuiteFreeFileSync_spsFreeFileSync.exe
should be
start "" #:\SyMenu\ProgramFiles\SPSSuite\SyMenuSuite\FreeFileSync_sps\FreeFileSync.exe
A link to the batch file...
Here is an example batch file to download:
http://www.ugmfree.it/public/SyMenuWorkaround/SyMenuStartFreeFileSync.zip
-
- Posts: 27
- Joined: 11 Dec 2004
Wylie: We tried that method at PortableApps.com soon after the bug presented 2 years ago. The standard ways to break out of process are either `start "" "FreeFileSync.exe"` or `cmd /c start "" "FreeFileSync.exe"`. We've found this technique to be only partially effective in neutralizing the bug. On some affected machines, it will work every time. On some it will work about 1/2 the time. And there doesn't seem to be a specific trigger on it either way other than whether the parent or grandparent process is still running as demonstrated with the example code I gave the publisher about a year ago in the thread. So, it's not a complete solution, even just for one proprietary menu.
-
- Posts: 27
- Joined: 11 Dec 2004
In additional testing, it seems that it is indeed the FreeFileSync.exe and FreeFileSync_x86/x64.exe processes that are stepping on each other with locking the options file. This continues to happen when launched from a parent process that remains running (portable menu, portable file manager, 3rd party scheduling utility). This may be related to changes in the way file_handling.cpp lock checks are made between 6.2 and 6.3. It also may be related to the update checker which is buggy when run portably: viewtopic.php?f=2&t=2308
If anyone needs FFS 6.2 and 6.3 to compare, they're available from PortableApps.com here: https://sourceforge.net/projects/portableapps/files/Source/FreeFileSync/
If anyone needs FFS 6.2 and 6.3 to compare, they're available from PortableApps.com here: https://sourceforge.net/projects/portableapps/files/Source/FreeFileSync/
- Posts: 1
- Joined: 23 Feb 2016
This works for me. Bug solved.start "" "FreeFileSync.exe"Wylie
Thank you Wylie.
-
- Posts: 2
- Joined: 24 Feb 2016
Hi guys,
Upgrading to v7.9, this bug suddenly hit me to.
Before I found this thread, I made some research on my own, and found that I was affected only when I have my Windows scheduled FFS operations enabled. As soon as I disable the scheduled operations, the SyMenu launcher works flawless again.
Gianluca's workaround works fine, while waiting for the "real thing". ;)
Upgrading to v7.9, this bug suddenly hit me to.
Before I found this thread, I made some research on my own, and found that I was affected only when I have my Windows scheduled FFS operations enabled. As soon as I disable the scheduled operations, the SyMenu launcher works flawless again.
Gianluca's workaround works fine, while waiting for the "real thing". ;)
-
- Posts: 27
- Joined: 11 Dec 2004
For completeness, it should be called volpoca's solution since he posted it here in January 2015: http://portableapps.com/comment/220608#comment-220608
Not sure why others are taking credit for the approach.
Not sure why others are taking credit for the approach.
-
- Posts: 2
- Joined: 24 Feb 2016
Well, I was talking about this workaround, and that has very little, or nothing to do with PortableApps.For completeness, it should be called volpoca's solution since he posted it here in January 2015: http://portableapps.com/comment/220608#comment-220608
Not sure why others are taking credit for the approach.critternyc
-
- Posts: 27
- Joined: 11 Dec 2004
It's a simple trick volpoca posted to the PortableApps.com forums back in January 2015. And that pudah already posted within this thread in April of 2015. It's an old approach that doesn't help for every app you'd want to launch it from, especially scheduling utilities. It's now referenced right in the main topic of this thread for those that it might work for. It's just odd that it's being posted about by a couple people a year later as if it's something new created by someone recently.Well, I was talking about this workaround, and that has very little, or nothing to do with PortableApps.eson
- Posts: 1
- Joined: 2 Mar 2016
Hello.
I have the same problem. In my system (Windows 7 x64) I solve this by right click on file "FreeFileSync.exe" (need to mention, that it is installed as the portable application on the removeable USB HDD and I run it from this HDD), choose "Properties", then tab - "Compatibility". In this tab "Privilege level" - check mark "Run this program as administrator". After that the batch job task runs normally without Error Code 32.
Hope this helps somebody.
I have the same problem. In my system (Windows 7 x64) I solve this by right click on file "FreeFileSync.exe" (need to mention, that it is installed as the portable application on the removeable USB HDD and I run it from this HDD), choose "Properties", then tab - "Compatibility". In this tab "Privilege level" - check mark "Run this program as administrator". After that the batch job task runs normally without Error Code 32.
Hope this helps somebody.
- Posts: 3
- Joined: 1 Dec 2016
Hello, I found a solution to the error code 32.
A permanent and 100% working solution. It's a workaround but works great.
I have 5 sync jobs that I run using a Scheduled Batch file.
Here is the batch file
========================
FreeFileSync.exe Job1.ffs_batch
FreeFileSync.exe Job2.ffs_batch
etc
=========================
Instead of using a .bat to .exe file converter, I wrote this AutoHotKey Script
========================================================
; Launch the Batch File
SetWorkingDir, C:\Software\FreeFileSync
Run, "C:\Software\FreeFileSync\ALLSyncJobs.bat"
========================================================
I then converted the AHK script using a AHK to EXE converter.
Don't ask me why, but it works each time.
Best
A permanent and 100% working solution. It's a workaround but works great.
I have 5 sync jobs that I run using a Scheduled Batch file.
Here is the batch file
========================
FreeFileSync.exe Job1.ffs_batch
FreeFileSync.exe Job2.ffs_batch
etc
=========================
Instead of using a .bat to .exe file converter, I wrote this AutoHotKey Script
========================================================
; Launch the Batch File
SetWorkingDir, C:\Software\FreeFileSync
Run, "C:\Software\FreeFileSync\ALLSyncJobs.bat"
========================================================
I then converted the AHK script using a AHK to EXE converter.
Don't ask me why, but it works each time.
Best
