Page 1 of 1

another ERROR Unable to Update Data record

PostPosted: Sat Jul 04, 2015 1:48 pm
by xeddog
I have been running Newsbin Pro for quite a while now with no issues at all, but about a week ago I started getting the subject messages. It's hard to tell how many because when it gets up to just under 4000, the count keeps going up and down some. But there is a lot of them.

I have read that compacting the database might resolve this, so I compacted all of the groups but it didn't help. Then I also read that deleting the group in question and re-downloading all headers would do it. When I look at the messages there is just about every kind of file name from porn to movies to pc software, to music to books to . . . whatever. I have looked up a couple of these on nzb.su and they are in groups that I don't index like a.b.boneless, or a.b.mom. So how do you tell which group(s) are affected?

Thanks,

xeddog

Re: another ERROR Unable to Update Data record

PostPosted: Sat Jul 04, 2015 7:00 pm
by Quade
I have looked up a couple of these on nzb.su and they are in groups that I don't index like a.b.boneless, or a.b.mom. So how do you tell which group(s) are affected?


It's going to be a group you're downloading headers from. So, it's basically one of the ones in your list. Files are crossposted to many group so, even if you're not downloading headers from a particular group you might see posts that a posted BOTH to the groups you do download headers from and ones you don't.

Compact can only fix a very limited number of errors in the DB's. One option is to wait till the import finishes. Then download headers one at a time from your groups till you find one that returns the errors. The other option is to use "Procmon" to see what files Newsbin is accessing at the time.

Re: another ERROR Unable to Update Data record

PostPosted: Mon Jul 06, 2015 2:57 pm
by xeddog
Well, I got the number of error messages down from over 4000 to around 40 by deleting three groups and downloading all headers for them. At least, the download is proceeding now.

I have been trying to find information about "procmon". I have seen you refer to it in a couple of other threads, but I can't find anything about it. Would you point me in the right direction?

Thanks,

xeddog

Re: another ERROR Unable to Update Data record

PostPosted: Mon Jul 06, 2015 4:16 pm
by Quade

Re: another ERROR Unable to Update Data record

PostPosted: Tue Jul 28, 2015 1:54 pm
by Quah
I was seeing this error in RC2, and also build 4163.
In my case it appears to have been caused by the spool_v6 folder (or subfolders) being read only.

The spool_v6 folder only shows one group, and in the groups list, it only shows that same group has any new downloads. The others show no new downloads, but that is very unlikely.

If I compact these groups, it shows 0 size. Each time it gets new group updates, it gets a full days worth, as set in the properties for empty groups.

I believe this is related to the problem I'm having with my download filter no longer working, but I'll need a few more days to confirm that.

Re: another ERROR Unable to Update Data record

PostPosted: Tue Jul 28, 2015 2:40 pm
by Quade
In my case it appears to have been caused by the spool_v6 folder (or subfolders) being read only.


It'll never work properly if this is the case.

Re: another ERROR Unable to Update Data record

PostPosted: Tue Jul 28, 2015 11:36 pm
by Quah
Yes, I misunderstood. The blue block in properties/Attributes/Read Only is misleading and has some other meaning. Still clearing it did stop all the bright red errors in the log. The read only blue block does comes back, but the errors don't. I'll address the other issue I'm having in an appropriate thread if I don't resolve it on my own.

Re: another ERROR Unable to Update Data record

PostPosted: Wed Jul 29, 2015 1:55 am
by Quade
Yes, I misunderstood. The blue block in properties/Attributes/Read Only is misleading and has some other meaning. Still clearing it did stop all the bright red errors in the log. The read only blue block does comes back, but the errors don't. I'll address the other issue I'm having in an appropriate thread if I don't resolve it on my own.


I've seen strange things like that in Windows too.