Page 1 of 1
Fatal error help!
Posted: March 26th, 2014, 1:49 pm
by mfitt
Had this come up today, on .16 and .17 and now nothing will download! Any ideas?
SABnzbd detected a fatal error:
"C:\Users\User\AppData\Local\sabnzbd\sabnzbd.ini" is not a valid configuration file
Error message: Invalid line at line "1".
Specify a correct file or delete this file.
Program did not start!
---------------------------------------------
I don't actually have the specified folder. I have uninstalled sab and put it back on, and also tried both versions with the same result.
Re: Fatal error help!
Posted: March 26th, 2014, 2:03 pm
by shypike
Your sabnzbd.ini file has become corrupt.
Inspect it with Notepad (or something similar).
Location:
http://wiki.sabnzbd.org/configure-0-7
In the worst case you need to remove that file and reconfigure SABnzbd.
Re: Fatal error help!
Posted: March 26th, 2014, 2:29 pm
by mfitt
Thanks for the reply. I can't even get sab to open to try and re-configure it. I don't have the folder where the error is. Never had this problem before with any version. Is there anyway to install this missing folder by itself?
Re: Fatal error help!
Posted: March 26th, 2014, 4:13 pm
by shypike
It's not a missing folder, but a corrupt INI file.
The file is located where the Wiki page says it is, although the folder might be hidden.
Without removing that file (sabnzbd.ini) SABnzbd will not start.
Re: Fatal error help!
Posted: March 27th, 2014, 12:26 am
by mfitt
Got there in the end. I had to do a search for "sabnzbd.ini" on my whole C drive, but there were 2 ini files hidden that I deleted, and it all works lovely again. Thanks for the help shypike.
Re: Fatal error help!
Posted: March 27th, 2014, 4:38 am
by shypike
Where were those files located?
Re: Fatal error help!
Posted: March 27th, 2014, 6:36 am
by mfitt
I'm using Windows 8, so they were in c/users/user/sabnzbd but I couldn't find them until I did a search of C drive. It may have just been me looking in the wrong place or they were hidden. It looks like it was a program at 0620 yesterday morning that didn't d/l correctly that caused the error.