This content has been marked as final. Show 11 replies
sounds like the exact problem that 5.1.9 has, so I would go down the easy route and exchange the sbfiledb.dll for the 5.1.8 version, or upgrade to the current version first.
it's not "upgrade" which causes this issue, it's that version of that dll.
Ok, I will try that, but isn't it strange that it only affects one device group in stead of all the groups? The other cases over here always reported this on the complete database.
Ok, I've replaced the DLL and it fixed the error.
I've had this problem now, do I have to download the whole Endpoint_Encryption_Suite_B5600.zip just to get the old sbfiledb.dll that makes the problem go away?
no, download the LATEST version, and use that in its entirety.
ok I installed everything from Endpoint_Encryption_Suite_B5701 as that was all that was available. Now I see there is McAfee_EEPC_520.zip & McAfee_EEM_520.zip on my grant number login.
rather than upgrading properly I just want to get this machine back using the temp dll fix
what is the quickest way?
The temp dll fix (replacing sbfiledb.dll with 5.18/5.2x) is for a totally different problem than the one you (ZN) have. You need to either do a disable/enable on the affected machines, or eBoot them. There's no way to fix the corruption AFAIK.
In the eem when I double click the device it popsup
error 0xdb000013 - file not found
so I say OK on the error message then a properties window opens saying "no properties are available"
the client refuses to sync because error db000013 file not found
I thought having seen a couple of threads that this was a bad dll not reading the db correctly but you are saying the db is corrupted?!?
I'm really worried if this is the case when I'm still testing on our trial with less that 20 users/devices
you need to confirm what problem you have - if it's in EEM, the DLL switch will fix it, if it's on the client itself, then it's something different.