NzbDrone error on launch

Help & Support
1

It used to work great for the last 2 weeks, but yesterday I restarted my computer (I restarted it alot during that period too) and since then whenever I try to launch NzbDrone.exe it shows this error:

this is the log i found on C:\\ProgramData\zbDrone\\logs:

“13-9-10 02:19:46.5|Info|AppMain|Starting NzbDrone Console. Version 2.0.0.419
13-9-10 02:19:47.0|Info|Router|Application mode: Interactive
13-9-10 02:19:56.3|Info|AppMain|Starting NzbDrone Console. Version 2.0.0.419
13-9-10 02:19:56.6|Info|Router|Application mode: Interactive
13-9-10 02:22:58.6|Info|AppMain|Starting NzbDrone Console. Version 2.0.0.419
13-9-10 02:22:59.5|Info|Router|Application mode: Interactive
13-9-10 02:24:39.4|Info|AppMain|Starting NzbDrone Console. Version 2.0.0.419
13-9-10 02:24:39.7|Info|Router|Application mode: Interactive
13-9-10 02:28:29.2|Info|AppMain|Starting NzbDrone Console. Version 2.0.0.419
13-9-10 02:28:29.5|Info|Router|Application mode: Interactive
13-9-10 02:43:14.1|Info|AppMain|Starting NzbDrone Console. Version 2.0.0.419
13-9-10 02:43:15.0|Info|Router|Application mode: Interactive
13-9-10 02:45:19.9|Info|AppMain|Starting NzbDrone Console. Version 2.0.0.419
13-9-10 02:45:20.2|Info|Router|Application mode: Interactive”

2

Sounds like a corrupt config file, any chance you did a system restore at that time? (someone else had the same issue and they did).

You can delete config.xml from C:\ProgramData\zbDrone and drone will rebuild it on start, you will need to reconfigure your username and password (if set) as well as the default port (if changed).

3

Thank you very much, this worked like a charm.
Any possible explanation to why that happen?

4

No, not sure how/why that would happen. With the other user I suspect the system restore, but I guess its possible that shutting down while NzbDrone is acting on the xml file could cause issues.

We should be displaying a better error message though, so I have added it to Trello: https://trello.com/c/muxChgBX/362-handle-config-xml-corruptions-more-gracefully

5

Thanks for the answer, I think that a shutdown is what caused it, happened a lot recently.