SABnzbd Forums

I searched the web and this forum and didn't see this or similar posted. The issue started after upgrading from standard release to the 0.6.0 beta/RC and intermittently presents after making changes in SAB's web interface, then restarting SAB, (also via the web interface). Once the SAB process has restarted, I am presented with the initial setup wizard, and all settings are gone.

It appears that, when this issue occurs, SAB shows 'C:\Documents and Settings\NetworkService\Local Settings\Application Data\sabnzbd\sabnzbd.ini' as the default location for the configuration file instead of 'C:\Documents and Settings\USERNAME\Local Settings\Application Data\sabnzbd\sabnzbd.ini'
The ini file in the expected 'USERNAME' directory still contains my settings, while the one in the 'NetworkService' directory is a clean slate, hence the setup wizard upon startup. If I replace the ini file in the 'NetworkService' directory with the one in the 'USERNAME' directory and restart SAB, everything goes back to normal again.

Has anyone else seen this? Is there a permissions issue or similar I may need to look into on my OS that would cause this?

Host OS: Windows XP SP3 x86
SAB Version: 0.6.0RC2

How do you start SABnzbd?

Hi shypike, just with a shortcut in the 'Startup' folder.

Looks like your OS has an identity crisis.
SABnzbd asks the OS what the user's profile folder is and uses what is returned.
There is a way to force the use of an INI file.
Open the properties of the SABnzbd icon (in the Startup folder) and
add this at the end of the "Target" filed, after the last quote character:
-f "c:\documents and settings\USERNAME\Local Settings\Application Data\sabnzbd"

The side effect will be that "Downloads" and some other folders will no longer be
in the normal location. So you will have to change those.

I'm not so sure; I've had SAB installed for quite some time on this particular box, and the issue only started after upgrading to 0.6.0 Beta. It could easily fall on either side of the fence without more details I suppose. Either way, I know how to fix it now and I have a backup of the ini file, so I'll just keep an eye on it.

Try looking at the logging file, next time it fails.
That may give some clues.