[PROBLEM] 4.7.2 worked fine. Upgraded to 4.7.5 and can't rename files

All your suggestions, requests and ideas for future development
Post Reply
horseflesh
Posts: 4
Joined: 26 Nov 2016, 04:02

[PROBLEM] 4.7.2 worked fine. Upgraded to 4.7.5 and can't rename files

Post by horseflesh »

I started Filebot 4.7.2 x64 today and got a prompt to upgrade to 4.7.5. I did so but then found a problem: I was unable to rename files. Clicking Rename just did nothing at all.

I also found that when I looked up a file which required me to clarify the actual show name, the show selection dialog popped up twice in a row--thereafter, the Rename button failed to do anything.

I reinstalled Java, no change. I reinstalled 4.7.5 x64, no change.

I uninstalled, deleted Filebot's folder in Appdata, manually installed 4.7.2 x64 and all is well again. I reinstalled 4.7.5, and the problem returned. Reverted, all was well.

Here's the data from the broken 4.7.5 install. I am sure this error is the source of the trouble because under 4.7.2 my error log is empty. It's strange that 4.7.2 worked perfectly and 4.7.5 failed in the same environment:

WARNING: Could not find JNA native support

My OS is Win7 64 bit and I installed 64 bit Java, though the "HotSpot VM" shows 32 bit, which is confusing.

Filebot console output

Code: Select all

C:\Users\matt>"C:\Program Files\FileBot\filebot.exe"
Could not find JNA native support
java.lang.UnsatisfiedLinkError: Could not find JNA native support
        at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java
:844)
        at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:826)
        at com.sun.jna.Native.<clinit>(Native.java:140)
        at net.filebot.win.Shell32.<clinit>(Shell32.java:12)
        at net.filebot.win.WinAppUtilities.setAppUserModelID(WinAppUtilities.jav
a:15)
        at net.filebot.Main.startUserInterface(Main.java:244)
        at net.filebot.Main.lambda$main$1(Main.java:133)

filebot -script fn:sysinfo output


C:\Users\matt>"C:\Program Files\FileBot\filebot.exe" -script fn:sysinfo

Code: Select all

FileBot 4.7.5 (r4600)
JNA Native: java.lang.UnsatisfiedLinkError: Could not find JNA native support
MediaInfo: net.filebot.mediainfo.MediaInfoException: Unable to load x86 (32-bit)
 native library MediaInfo.dll: Could not initialize class com.sun.jna.Native
7-Zip-JBinding: net.sf.sevenzipjbinding.SevenZipNativeInitializationException: F
ailed to load 7z-JBinding: C:\Program Files\FileBot\7-Zip-JBinding.dll: Can't lo
ad AMD 64-bit .dll on a IA 32-bit platform
Chromaprint: 1.1.0
Extended Attributes: OK
Script Bundle: 2016-11-26 (r465)
Groovy: 2.4.7
JRE: Java(TM) SE Runtime Environment 1.8.0_111
JVM: 32-bit Java HotSpot(TM) Client VM
CPU/MEM: 4 Core / 247 MB Max Memory / 20 MB Used Memory
OS: Windows 7 (x86)
Package: MSI
Data: C:\Users\matt\AppData\Roaming\FileBot
Done ?(?????)?
Filebot error log contains only

Code: Select all

Nov 25, 2016 7:58:06 PM net.filebot.win.WinAppUtilities setAppUserModelID
WARNING: Could not find JNA native support
java.lang.UnsatisfiedLinkError: Could not find JNA native support
	at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:844)
	at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:826)
	at com.sun.jna.Native.<clinit>(Native.java:140)
	at net.filebot.win.Shell32.<clinit>(Shell32.java:12)
	at net.filebot.win.WinAppUtilities.setAppUserModelID(WinAppUtilities.java:15)
	at net.filebot.Main.startUserInterface(Main.java:244)
	at net.filebot.Main.lambda$main$1(Main.java:133)
User avatar
rednoah
The Source
Posts: 22995
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: [PROBLEM] 4.7.2 worked fine. Upgraded to 4.7.5 and can't rename files

Post by rednoah »

I recommend getting FileBot from the Windows Store if you have trouble setting up 64-bit Java on your 64-bit machine. You're using 32-bit Java which makes little to no sense in this day and age. :lol:
FAQ wrote:Q: Why is MediaInfo not working? Why is 7zip not working?
If you are using 64-bit Java you must install 64-bit FileBot. If you are using 32-bit Java you must install 32-bit FileBot. If you have installed 64-bit Windows and 64-bit FileBot and 32-bit Java, the java process will be in 32-bit compatibility mode and the native libraries won't work. So uninstall 32-bit Java and then only install the latest 64-bit Java and latest 64-bit FileBot.
:idea: Please read the FAQ and How to Request Help.
horseflesh
Posts: 4
Joined: 26 Nov 2016, 04:02

Re: [PROBLEM] 4.7.2 worked fine. Upgraded to 4.7.5 and can't rename files

Post by horseflesh »

Thank you for confirming the issue. This is what I suspected, but things didn't seem to add up. The previous version of Filebot worked, and going through the Java install process anew didn't install the 64 bit version, which seems crazy. But I just did it again--uninstalled, started at java.com via Chrome, and reinstalled based off the biggest, flashiest prompts on the site. I assumed the path of least resistance on java.com would install 64 bit Java on a 64 bit OS -- and it does not! You really have to dig for it.

BTW, if you start Filebot without any Java installed at all, it takes you to the download page -- but it's the download for the big fat SDK, not the JRE. Can users just install the smaller JRE?

Edit: just the JRE works, as I'd expect. Maybe update the link for when a user starts Filebot without a JRE?

Thanks for Filebot!
Last edited by horseflesh on 26 Nov 2016, 05:26, edited 1 time in total.
User avatar
rednoah
The Source
Posts: 22995
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: [PROBLEM] 4.7.2 worked fine. Upgraded to 4.7.5 and can't rename files

Post by rednoah »

I recommend the JDK because it includes the JDK & JRE but none of the consumer bullshit (advertising, ask toolbar, browser plugin, etc) that give Java a bad name.

That being said, the Window Store version includes it's own private 64-bit JRE, so you won't need to worry about Java at all if you get it via the Windows Store.
:idea: Please read the FAQ and How to Request Help.
horseflesh
Posts: 4
Joined: 26 Nov 2016, 04:02

Re: [PROBLEM] 4.7.2 worked fine. Upgraded to 4.7.5 and can't rename files

Post by horseflesh »

rednoah wrote:I recommend the JDK because it includes the JDK & JRE but none of the consumer bullshit ...
Cool, I did not know that! Makes sense.

All is well now on my install. Thanks again.
kevin2016
Posts: 4
Joined: 28 Nov 2016, 04:19

Re: [PROBLEM] 4.7.2 worked fine. Upgraded to 4.7.5 and can't rename files

Post by kevin2016 »

Thanks for the great support! I had this problem, not renaming after upgrading to 4.7.5, checked and found Java (32 bit) in the Control Panel. I uninstalled, and followed the Oracle prompts to install online and installed.... Java (32 bit) again. I uninstalled again, and installed the 64 bit version following the offline prompts and everything's working fine now.
horseflesh
Posts: 4
Joined: 26 Nov 2016, 04:02

Re: [PROBLEM] 4.7.2 worked fine. Upgraded to 4.7.5 and can't rename files

Post by horseflesh »

I'm glad I wasn't the only one!
olivio
Posts: 1
Joined: 29 Nov 2016, 21:18

Re: [PROBLEM] 4.7.2 worked fine. Upgraded to 4.7.5 and can't rename files

Post by olivio »

horseflesh wrote:I'm glad I wasn't the only one!
same here, same problem with windows 2012 server
JazJon
Posts: 9
Joined: 20 Apr 2012, 22:04

Re: [PROBLEM] 4.7.2 worked fine. Upgraded to 4.7.5 and can't rename files

Post by JazJon »

I upgraded from 4.72 to 4.75 (Used the Free Edition to test first) but I couldn't rename any files as well. I just ran across this thread and now realize I needed to update to 64bit Java. (Done)

I was happy to pay $9.99 yesterday but after my test failed I rolled back to 4.72. Now that I know how to get 4.75 working, I'm happy to go through the windows store but the price went up to $19.99 Any way to get discount coupon to pay the original Cyber Monday $9.99 Deal? If so please send a PM :)

Proof I was ready:

Image
User avatar
rednoah
The Source
Posts: 22995
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: [PROBLEM] 4.7.2 worked fine. Upgraded to 4.7.5 and can't rename files

Post by rednoah »

1.
The Windows Store version can't have this problem, because the package includes it's own private 64-bit JRE and doesn't use or care about whatever Java you may or may not have installed on your system.

2.
There should be a new sale for all of December. Please try again tomorrow.
:idea: Please read the FAQ and How to Request Help.
Post Reply