This content has been marked as final. Show 6 replies
it means the server definition you included in your install set is NOT the one the server is using (did you create multiple server entries, or did you delete and recreate a server entry?)
the temporary solution is to set authentication=no in sdmcfg.ini on the client.
the proper solution is to work out why your server/client keys are mismatched and fix that.
I use the same installation set as every other computer and they all work fine. We get this error from time to time, not very often though.
We have upgraded the server side to 5.1.7 but apart from that there's nothing else changed. We have a lot of computers that are still getting the old installation set and works ok, even after the upgrade.
We have two server entries that points to the same server at the moment. (the server was planned to be replicated and used as backup but that never happended.)
I have not deleted or recreated any server entries at all.
From what I can see in the sdmcfg.ini file it looks ok.
ah, if it's intermittent, then that's a know issue with that build. Resolved in 5500 etc.
you can upgrade (I'd wait for 5503 which should be due any week now) or turn auth off to resolve.
Okey, that's good to know.
5503 in a week or so, now that's even better news. Been trying to get that info from a McAfee Tier III Support Engineer today actually :)
"any week now" is very different from "in a week or so" wink
Right you are grin Of course it's different, my mind just interpreted it to my advantage.
It's good news none the less.