Quade wrote:I'd guess one or more groups has become corrupt. I'd pick one bad group. First I'd try compacting it (Post Storage/Compact Database) if that doesn't work, I'd probably purge the group and re-download headers. See if that fixes it.
OK, I'll try that... But WHERE is this "Post Storage/Compact Database" I don't see anything like this under any of the main menu items, and it isn't under Options / Options or any of the other choices under Options. I tried looking FOR the help files, but 6.5 help just says to see 6.0 help and 6.0 help does not appear to be searchable in any way. I tried the page that is supposed to have a detailed explanation of all the menu items, but I couldn't find anything about post storage or compact database.
Quade wrote:6.56 is identical to 6.55 except for the SSL changes. The code for storing and accessing the groups is 100% identical.
I'm not sure exactly what version I was running before, but I doubt it was 6.55 because I don't generally upgrade with every new release.
Quade wrote:It does make me wonder if your security software is stepping on the data. I've not seen any real sign of it though.
Anything might be possible but the security software is Symantec Endpoint Protection which has been running here for a long time with just the regular updates and I don't think I've ever seen this before.
I'm not too worried because NewsBinPro still works despite the error messages -- 6.56 took a longer than expected to download the headers the first time but seems to be ok now - although it still gives hundreds of this particular error.
One other odd thing is the way it counts the log entries. The first few log entries get counted normally, but once the Unable to Update Data record errors start, they arrive in massive batches and the log counter acts weirdly. Right now it says "Logging:(3911)" but if I wait for the next batch of this error to show up the count will change but it may go up or down as entries from earlier in the log disappear. OK, it just logged another bunch of this same error and now the count is "Logging:(3833)"