This content has been marked as final. Show 15 replies
are you sure this is a database problem, and not a problem with the local client store on one machine?
Normally this error refers to a local problem on one machine (resolved in the current release).
no we have the same error on multiple machines, if it was 1 machine I would remove and re encrypt, but it seems to be on all machines in this group
Our database is plagued with problems like this and McAfee has been unable to figure out why object corruption continues to occur.
Their answer has always been either "Upgrade to the newest version (even if we were on the latest version)" or "Redesign your database - you should only have 500 objects or less per User or Machine Group".
We have been able to get rid of these "dead" objects in the database, which MIGHT be why you're seeing these sync errors, by using the sbadmcl tool in conjunction with the cleanupmachinegroup and cleanupusergroup options.
SBADMCL -Command:CleanupMachineGroup -Adminuser:***** -Adminpwd:***** -Group:”*****” -Database:"*****"
SBADMCL -Command:CleanupUserGroup -Adminuser:***** -Adminpwd:***** -Group:”*****” -Database:"*****"
It'll tell you at the end after running against each group if it found and removed any corrupt objects in the DB.
(I'd also use Group Scan to check for orphaned objects - from the MEE Admin Console)
Hope this helps
Thanks for the info I will have a bash
OK found the tool, assume it opens in command prompt, is there any docs on where to run it,
In the Documentation folder you should have some reference to what commands are available.
"Endpoint Encryption Scripting Tool User Guide" is the name of the PDF.
The command scructure is in XML, which I don't quite follow, but if you use the same params as listed in the document with the dash and dash & colon you get the same results.
your problem is not related to anything in the database - it's a problem with the client itself.
it would be unwise to tinker with the database when there's nothing to indicate its broken.
McAfee Gold and Platinum support recommended to me that I "tinker" with our database using these commands on a regular basis (monthly). They state it is a maintenance task.
Do you believe that the cleanupmachinegroup and/or cleanupusergroup can or will have adverse effects on a database?
I ask because of our ongoing issues like this error he was having, on multiple machines (2 or 3 a week) that are healthy good hard drives per thorough diagnostics, that appear to "corrupt" the database objects.
The problem I think is more the old version (5.1.8) of the client than anything else - it's more sensitive to slow/unreliable db links than the newer version (5.2). If you do have big groups, you simply need an adequate server to deliver them. If you have big groups and a hand-me-down server, you're asking for trouble.
The cleanup commands won't do anything they are not meant to do, but they have to be used correctly - you should make sure your db is offline before running them for sure. Any open objects will get treated as corrupt by these commands and will get removed from groups.
Mostly people forget this and are astounded when the command orphans out a whole bunch of busy machines. .