Page 1 of 1

Error when sending NZB to sabnzbd 1.0.0rc1 from SickRage

Posted: February 19th, 2016, 4:30 am
by sdwhwk
When SickRage cues an NZB, the NZB is added to Sab, but I get the following error on every add:

ERROR 19/02/2016 03:08 [19/Feb/2016:03:08:36] HTTP
Traceback (most recent call last):
File "cherrypy\_cprequest.pyo", line 670, in respond
File "cherrypy\lib\encoding.pyo", line 217, in __call__
File "cherrypy\_cpdispatch.pyo", line 61, in __call__
File "sabnzbd\interface.pyo", line 460, in api
File "sabnzbd\api.pyo", line 105, in api_handler
File "sabnzbd\api.pyo", line 549, in _api_addurl
File "sabnzbd\__init__.pyo", line 519, in add_url
File "sabnzbd\decorators.pyo", line 31, in newFunction
File "sabnzbd\nzbqueue.pyo", line 271, in generate_future
File "sabnzbd\decorators.pyo", line 31, in newFunction
File "sabnzbd\nzbqueue.pyo", line 428, in add
File "sabnzbd\growler.pyo", line 130, in send_notification
File "sabnzbd\growler.pyo", line 544, in send_windows
File "sabnzbd\utils\systrayiconthread.pyo", line 110, in sendnotification
error: (1460, 'Shell_NotifyIcon', 'This operation returned because the timeout period expired.')

And pauses. Windows Notification is enabled.

SickRage throws this:
2016-02-19 03:08:36 ERROR SEARCHQUEUE-BACKLOG-153021 :: [NZBGeek] :: Unknown failure sending NZB to sab. Return text is:

Removing Windows Notification option lets the NZBs go through. Have not tested to see if this does it on the other notification options yet. Will test in the morning.

Re: Error when sending NZB to sabnzbd 1.0.0rc1 from SickRage

Posted: February 19th, 2016, 5:20 am
by safihre
Yes we are aware and it will be fixed in the final release.
You probably run SABnzbd through the scheduler or another service that causes the SABnzbd tray-icon not to load, so it crashes when it tries to send a notification because Windows does not allow notifications without visible tray-icon.