SABnzbd Forums

Hi,

I'm running Sabnzbd & Episode Butler on a Win7 32-bit pc.

Sometimes Episode Butler exports downloads to sabnzbd with the char ":" in them.
then sabnzbd comes with the error for every file:
Disk error on creating file d:\sabnzbd\incomplete\blablabla: blabla 1x01.rar

I'v tryed activing "Replace Illegal Characters in Folder Names" but that doesn't help

Something I'v miseed?

Obviously this is a bug in Episode Butler.
On Windows, filenames cannot contain colons.
Please report this to the EP author too.
Normally SABnzbd filters out these characters, but EP has found a
way to bypass that check.
Since I don't know which method EP uses to send files to SABnzbd,
it's a bit hard to diagnose.

Thx, I'll try that

I'll check the API interface anyway, since that's the most likely point of entry.
It cannot be the "watched folder", since you cannot create disk files with colons in the name.

For newzbin I only send the reportId using the API. All naming info is taken from newzbin by sabnzbd itself.

For nzbs.org I use the URL using the API and also supply an nzbname parameter for a nice name (which will contain a : for certain shows).

For NZBMatrix i'm posting the nzbfile data. I couldn't get it to work with the API (possibly because the httpclient implementation I'm using uses a multipart scheme which isn't supported by sabnzbd) so I used the form on webadmin site itself (addFile instead of api). The file sent to sabnzbd contains a nice filename which may contain a :.



Some extra info. During my mail conversation with dimzen he told me he was using nzbs.org, so its probably the URL in combination with the extra nzbname parameter which is causing the problem.

The nzbname parameter in the API is not checked for illegal characters.
You're not supposed to use these characters.
It would be better if they were filtered by SABnzbd, but currently they're not.
That will be fixed in a later release, so for now, don't send illegal characters.
Sending colon characters isn't useful, since these cannot be stored in filenames anyway
(at least not on Windows).

Just had another error
This one had a "?" in the foldername.

Same issue, same solution.
It's fixed in the source archive now.

shypike wrote: Same issue, same solution.
It's fixed in the source archive now.

Ehmm.. where do I find that?