NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug.

The Fiji project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Bug 82 - Failure on update of fiji-win32.exe
Failure on update of fiji-win32.exe
Status: RESOLVED FIXED
Product: Fiji
Classification: Unclassified
Component: Other
unspecified
PC Windows
: P2 major
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2009-09-26 14:46 CDT by Richard Fetter
Modified: 2009-11-12 02:04 CST
0 users

See Also:

Description Richard Fetter 2009-09-26 14:46:54 CDT
I've run several update update attemps of Fiji today.  The first time through, all marked files were updated except fiji-win32.exe. Repeated update attempts fail for fiji-win32.exe with following message(I got the same message for it the first time):

Could not update fiji-win32.exe: C:\PROGRA~1\Fiji\Fiji.app\fiji-win32.exe (The process cannot access the file because it is being used by another process)

I have successfully updated fiji-win32.exe in the past, so I know it can be updated.  

Thanks,

Rick
Comment 1 Albert Cardona 2009-09-26 14:49:25 CDT
Hi Rick,

A major problem in windows is that the fiji-win32.exe process doesn't die when closing fiji, sometimes, and holds on to the ij.jar file. Go to the task manager, kill it, and then try again.
If that fails, make sure it's killed and then remove the ij.jar from fiji/ folder manually, and replace with the ij.jar of fiji/update/ij.jar

Please let us know if this fixed the (immediate) problem.
Comment 2 Richard Fetter 2009-09-26 23:41:10 CDT
I tried the suggested fix on my second Windows machine now: kill the fiji-win32.exe process and copy ij.jar from update to main folder.  Closing Fiji did cause the fiji-win32.exe process to terminate.  ij.jar was updated, but the update "Fiji-win32.exe" option in the update list generated by 'Update Fiji' from the Help menu gives the immediate ...cannot update fiji-win32.exe... message from my initial bug report.

So, 2 Windows XP SP2 machines, 2 failure messages to update fiji-win32.exe. 
Comment 3 Johannes Schindelin 2009-09-27 14:35:48 CDT
What _should_ happen is that Fiji tries to rename its executable (which is allowed, at least sometimes, on Windows) and the put the new executable into its place.

But it seems that your process does not have permissions to do so.  Is it possible that you need Administrator privileges to write to the location where Fiji sits?
Comment 4 Jan Eglinger 2009-10-01 23:13:54 CDT
I had the same problem (on WinXP SP3) after updating from an older Fiji version to the new Plzen-rc1 (not downloading the new package, but only updating).

I noticed that there was an older file "fiji-win32.exe.old" already sitting in the Fiji folder. After deleting this file, the updater proceeded without complaining any more and created a new file with this name.
(So I don't know what will happen if the next update of fiji-win32.exe is due: will it be able to overwrite the .old file?)

jan
Comment 5 Johannes Schindelin 2009-11-12 02:04:10 CST
I uploaded a new version of Fiji_Updater.jar which should fix this issue by removing the .old file automatically (please update via Help>Update Fiji).