You are correct. All I got was an improvement. I do get the errors when I launch Comodo. I no longer get them when I exit Comodo and relaunch or when I disable/enable the AV.
Since this thread has been moved, I doubt the developers are watching it any longer and, besides, it may be time for a bug report.
My browser is working properly again, and that’s all I care about. It’s only because of that I got involved in this whole dberr.txt errors thing.
URGENT - WHAT IS COMODO DOING AT 1810 SECOND INTERVALS ? ?
WHY is Comodo causing this error sequence
CatalogDB: 09:27:37 19/09/2009: File #2 at line #1236 encountered error 0x00000057
CatalogDB: 09:57:47 19/09/2009: File #2 at line #1236 encountered error 0x00000057
CatalogDB: 10:27:57 19/09/2009: File #2 at line #1236 encountered error 0x00000057
CatalogDB: 10:58:07 19/09/2009: File #2 at line #1236 encountered error 0x00000057
I have observed the same characteristic in the logs that other people have posted.
There seems to always be a flurry of " File #2 at line #1236" errors at start-up,
after which Comodo seems to go into a 1810 second maintenance cycle.
If Comodo developers think about what is done at 1810 second intervals they may be able to fix it.
I remember many versions ago when at regular interval Comodo would “touch” several hundred GIF / PNG images of red and green arrows used on the Comodo icon to show traffic direction,
and System Restore then added a few hundred more files to the Restore Point - many times a day.
It seems to me the latest problem is another reason for
“If it ain’t broken don’t fix it”
and instead we are suffering from the alternative
“Keep fixing till it breaks” ! ! !
Regards
Alan
I’m also not so sure now about Comodo not being related to the Opera problem. After I took the plunge late yesterday and updated to 3.12, I got the dreaded pop-up again where Opera said it couldn’t save my preferences. I had loaded it numerous times previously and only had the problem again right after the update. Too much of a coincidence to my way of thinking.
And I’m getting many more errors now in the dberr.txt log, more on the order of the other posters.
Alan, good point about the 1810 second intervals being a good place to start, even though I don’t get those.
Someone, please try this. Cmdagent.exe runs as a Windows Service, which I hadn’t noticed previously, and is a Helper Service. Try setting it to Disabled and see if you don’t get errors. I didn’t.
(Helper Services are notorious for causing problems so it was one of the things I was looking at today.)
THAT CAN BE VERY VERY DANGEROUS.
I assume that cfp.exe and Cmdagent.exe have the same responsibilities now as they have had for a long time (way before 3.5, possibly before 3.0).
Cmdagent.exe was in the hardware start-up and was responsible for all protection before and after the user logs on.
Cfp.exe started up AFTER the user logs on, and was responsible for the GUI and pop-ups and any update downloads.
If you remove or delay the start-up of Cfp.exe, you get no pop-ups and no chance to permit.
You still have full protection from Cmdagent which prohibits violations of rules unless permitted.
I am happy to remove Cfp.exe from the main start-up folder, and to replace with my own CMD script that launches various applications in a sequence for an orderly activation - otherwise important things fail to appear in the notification tray. After launching the “urgent” stuff I launch the “GUI” portions of Comodo (and when present the “GUI” portion of ESET NOD32). This allowed the notification tray to get organised before the extreme aggravation/delay of update/signature downloads from the protection servers.
If you remove Cmdagent.exe and retain only Cfp.exe, I am sure from past experience you will be able to download updates and signatures, but it is unlikely that you will have any protection, Cmdagent will not be there to enforce the rules. I think it would allow anything bad to happen - though just possibly it might prohibit anything good or bad, it just would not know right from wrong.
I could be wrong - but it is not a risk I would take whilst electrically connected to the Internet.
Alan.
This was meant to be for diagnostic purposes only to possibly help the developers locate the problem. Like I said before, if anyone cares to try something and feels uncomfortable about an always on connection they can unplug their connection. Someone should only try something in forums if they care to and realize they do so at their own risk. This caution is oft repeated, as I did so in a previous post.
I don’t believe anything in my post inferred that someone should leave it this way. Covering up a problem does not solve it. Besides, they won’t be able to get AV updates it’s off.
I was giving a warning to any-one who might fail to recognise the risks.
I was also warning you because you said cmdagent would not be running without cfp,
and therefore I thought you expect cfp to do all the protection,
and that cmdagent.exe was merely a helper with some unknown bonus features that get in the way.
I agree with you on updates, BUT Windows Automatic Update is always disabled until I have investigated what Security patches may be on offer, and wait a bit to see if any-one reports any problems, and only when I feel comfortable do I nudge the control to Notify and then cautiously choose what to reject and what to download, and then I custom install.
Regards
Alan
Never hurts to provide warnings.
As for cmdagent, a couple of posts ago I said I hadn’t previously realized it was being run as a Windows Service, implying it would be running without cfp loaded. Also, I thought it might give you a clue as to why you are getting those 1810 second errors. My thought was that cmdagent is checking in every 30 minutes and creating an error from that, though I don’t know why it wouldn’t be doing the same on my system.
I know this is not a high priority for the developers, and not really for me either, but I hope they can pull something out of all this.
Have you unchecked Automatically update virus database before scanning in the real-time scanning engine settings?
Because every thirty minutes seems an obvious indication it has to do with the automatic update.
No. It’s checked, and I don’t get the 30 min. errors.
Edit: I was thinking and looking at Scan Memory on Start, which is where I used to get errors when I disabled/enabled it. The one you are referring to is unchecked. Sorry.
OK, it appears that although the automatic DB updating throws errors, the majority of the errors at boot are caused by the scan memory on start function.
If I disabled both scan memory on start and automatically update, I only get a single error added to the log at boot. (Turning on scan memory at this point nets me 42 errors. Now I know Hitchhiker’s Guide to the Galaxy fans will notice this number is the answer to Life, The Universe, And Everything, but I don’t think that’s significant…)
If I enabled automatically update, I still only get a single error at boot.
Not surprisingly, enabling scan memory will net me 40+ errors at boot.
What going on here devs? ???
That was my opinion in my very first post. The Catroot2 rebuild was mostly a distraction, although it did seem to make some little difference in my case.
I left the Automatically Update on, after an exit & relaunch but not a reboot, and haven’t had any errors for a couple of hours. AV has been automatically updating.
Are the developers reviewing these posts, or does someone need to file a bug report?
MRCS
Thank you for starting this thread.
When I first noticed the problem I looked in this user forum and saw no posts.
I thought it required detailed knowledge by Comodo developers of their proprietary code and of Windows,
so I chose to open a support ticket, which did not get me very far. I was told the problem had only been seen in Vista, not XP, and that it was fixed in v3.11 - but it is not.
I tried various specialist technical forums for Catroot2 etc problems, and got nowhere.
I felt very lonely as the only man on the earth with this particular problem.
I returned to this forum and was delighted to find I was not alone.
I now have hope that the developers will now take notice and fix this problem soon.
I keep a close eye on all changes to files and folders, hence I saw dberr.txt continuously growing.
I guess that for every-one of us here who take an interest in such things, there could be 10,000 “normal” users who just play games and use emails etc, and are not aware of impeding doom.
I think raising a bug report linking to this forum is an excellent idea,
but I cannot focus on that myself - the wife is demanding that I take her shopping.
Regards
Alan
Yes, that is wrong on both counts. 
There is definitely a connection between the problems I’ve been having with Opera and Comodo, after all.
I’ve been watching the time stamp when one of my Opera preference files gets revised, which doesn’t happen very often, and when I get a rare non-boot Catroot error. The times have been corresponding. The last ones are:
On the Opera file -
Today, September 22, 2009, 1:41:28 AM
And the dberr.txt -
CatalogDB: 1:41:27 AM 9/22/2009: File #2 at line #1236 encountered error 0x00000057
I’ve given Opera and temporarily various Opera program files full rights to see if I could get Comodo to stop interfering. It hasn’t made any difference.
Whatever is going on with Comodo, it has a strange complex of symptoms.
I’m curious why the devs haven’t had anything to say about this… ???
Like I said in a previous post, “Since this thread has been moved, I doubt the developers are watching it any longer…” Do you know if this is the case? And, do you know if a bug report has been filed?
Well, according to forum lore, the developers follow the forum closely.
I guess a bigger question would be, why was the thread moved? This is obviously a bug, and I’m willing to bet it affects everybody using the software but its evidence is a bit obscure so most people don’t realize it’s happening… 88) Perhaps whoever moved it could move it back?
I haven’t filed a bug report. I don’t see much difference between an “official” report and one posted on the support forum. Does it really need to be official before any action is taken?
It was moved at the same instant I said I thought the Catroot2 rebuild might have been successful for me.
As to whether official action needs to be taken, I thought being a “Comodo Hero” you would know these things. I’ve never actually filed one, anywhere, because the board monitors usually have something to say.
Hah! No, that just means I talk a lot. 
Edit: OK, posted a bug report.
CIS creates numerous errors in CatRoot2 log, dberr.txt daily.