Page 1 of 1

error when try to fetch episode list

Posted: 13 Dec 2011, 21:11
by ztoner
hi there!
this seems to be a really nice program, but I run into some trouble, I cant fetch episode lists from any sources?

with an error like:

***Richard***

Re: error when try to fetch episode list

Posted: 14 Dec 2011, 00:50
by rednoah
Haven't seen that before. Can u run "filebot" from cmdline? There should be more output there.

Re: imdb id lookup problem?

Posted: 14 Dec 2011, 02:11
by rednoah
Is there nfo files with imdb ids in that folder? Might be that the datasource I use to lookup imdbids was down when u tried... i'll switch that to the thetvdb interface and gracefully ignore errors. nfo/id lookup is just an extra anyway. Updated the v2.3 release packages to r765.

Re: error when try to fetch episode list

Posted: 15 Dec 2011, 15:26
by ztoner
thanks for answer.

nope no nfo files, im on xp-sp3.. hmm havent really figured out the cmd-stuff jet, how do I runnit, where do I place the "bat-file"?

Re: error when try to fetch episode list

Posted: 15 Dec 2011, 15:35
by rednoah
There's filebot.cmd in INSTALL_DIR. That should also be in the PATH if installed via MSI. So just opening a cmd shell and then running "filebot" will run the app and also show u all the stacktraces in the console.

Re: error when try to fetch episode list

Posted: 15 Dec 2011, 15:42
by rednoah
btw are u using FileBot via WebStart, installed via MSI or directly running the jar?

Re: error when try to fetch episode list

Posted: 15 Dec 2011, 15:44
by ztoner
running the jar, with cmd looks like this.

Re: error when try to fetch episode list

Posted: 15 Dec 2011, 15:46
by ztoner
I'll try to re install it...

Re: error when try to fetch episode list

Posted: 15 Dec 2011, 15:50
by rednoah
This is wierd, there might be a caching inconsistency... try running "filebot -clear"

Re: error when try to fetch episode list

Posted: 15 Dec 2011, 16:11
by ztoner
that worked =)

Re: error when try to fetch episode list

Posted: 15 Dec 2011, 16:40
by rednoah
still a bit perplexed about that problem... but i think it would have fixed itself a few hours from now 'cause that cache element has a 48h timeout. :D