Support Forum

I'm currently experiencing the same issue... Version: 0.7.0 OS: Win7 Pro Install-type: Windows Zip Skin (if applicable): N/A (AFAIK) Firewall Software: N/A Are you using IPV6? no Is the issue reproducible? yes EDIT: Also, the suggested workaround of setting the download to "stop" doesn't w...

The default paths: C:\Users\steve\AppData\Local\sabnzbd\admin\ A couple nights ago on IRC didn't we move your cache (where history1.db lives) to something like C:\cache ? Did that help, or did it do the same thing as before: work for awhile and then stop working? Yea, correct, it worked for a while...

Which exact paths are you using? The database file will be in the sub-folder "admin" of the folder where the sabnzbd.ini file is. Can you use any tools (e.g. sysinternals collection) to see if another program might be accessing the history1.db file? The default paths: C:\Users\steve\AppDa...

This could be the problem, the server is running ESET Smart Security. I've completely disabled it at the moment and I'll try to reproduce my errors. You'll find many more ESET related complaints in this forum :( On a personal note: my opinion is that all these security programs cause more problems ...

Did you complain about this on the IRC channel before? One team member and one Beta tester tested on Server2008R2 but could not find any issue. Yea that was me, Do you think it matters that it was 64-bit? The only thing I can think of is that the OS doesn't allow you to open the db file. Access rig...

The error: 2010-01-19 03:53:56,917 ERROR: SQL Command Failed, see log See bottom of post for LINK to error logs and history1.db Version: (Ex: 0.5.0 beta 4) OS: MS Server 2008 R2 Install-type: Windows Installer Skin (if applicable): n/a Firewall Software: None Are you using IPV6? on Is the issue repr...