Colin,
As far as I know, the user did not edit the record, he went through the
screens, so the checksum should be ok.
I did verify that the account names are all upper-case - that was one of the
tech tips on the U2 Knowledge Base, although it said that that was
introduced in 5.3.4 when correcting a different issue in 5.3.3 (which was
why I was asking for memories of what was wrong on 5.3.3 - the release notes
don't specify!)
Thanks for the encouragement on old releases - I do my best to keep our
customers on current releases, but sometimes institutional inertia prevents
them from making changes.
Susan Lynch
F. W. Davison & Company, Inc.
----- Original Message -----
From: "Colin Alfke" <alfke...@hotmail.com>
To: "'U2 Users List'" <u2-users@listserver.u2ug.org>
Sent: 05/21/2010 11:42 AM
Subject: Re: [U2] receiving error message XX record corrupt on logto
It's not that old Susan - most of our clients are still running 5.2.4 with
some still on 4.5.4 :)
- make sure the DMACCOUNTS record key is all uppercase
- try saving the top of the tree in group security when logged in as root.
What was changed and how? You can't change most things manually without
causing this type of error because of the checksum it keeps. You may be
able
to change it back though....
Hth
Colin Alfke
Calgary, Canada
-----Original Message-----
From: Susan Lynch
I am hoping that someone has a good memory - the company I am working with
is running SBPlus 5.3.3, which is past the End of Service date. I have
checked the U2 Knowledge Base for this problem, and have checked
everything
that they listed, and none of those possible causes are the reason for
this
account.
My user says that he changed SB security for this account, and now HE
can't
log to the account without getting this message, and neither can I - and I
am in the ROOT group, and the account is in the ROOT group's list of
accounts without restrictions.
If all else fails, I can try copying over all the XX files from an account
where we are not getting this message, but I am not convinced that it will
solve the problem, since it arose immediately after he changed something
in
the security settings for the account.
Any ideas?
Thanks!
Susan Lynch
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
