Trend CSM and .notaccount. errors in server security logs - 529 and 681
I first blogged about this back in February when I spotted the issue on my networks, but back then I was not able to find the cause of the issue.
Susan has now blogged about a possible fix for the 529 and 681 errors involving .notaccount. The fix, which comes straight from a Trend knowledge base article is to simply turn off all but one option for the Trend Vulnerability Scanner. Of course, the Settings window itself recommends the exact opposite, but there you go.
I recommend if you are affected by the 529/681 .notaccount. issue that you consider very carefully the implications of turning off Vulnerability Scanning for all but OfficeScan Corporate Edition. Personally, I would not turn off Vulnerability Scanning for products that are in use on your networks. Let's be honest, the 529 and 681 errors, irritating as they are, as not so disruptive or damaging that the steps recommended by Trend are truly justified. I'd much prefer that Trend fix the problem, which has been around long enough to justify a knowledgebase article being published in June 2006! The article refers to CSM 3.0, and the problem continues in CSM 3.5 on one of my servers - I'm not seeing any sign of it on the server that is still running CSM 2.0. I can only hope the issue is finally fixed in the next version.
For the time being I'm going to disable only those options which are not relevant to my networks, and monitor the situation. If that doesn't work, well, I'll just have to start kicking up a bit more of a stink - I have email addresses
Oh, and by the way, I sincerely hope that you are not running Trend and/or McAfee and/or Norton on your network. Do *not* mix 'n' match antivirus protection - it will end in tears, I promise.
Trend recommends that all Product Query options except for OfficeScan Corporate Edition be disabled to stop the 529 and 681 errors involving .notaccount.