List u2-users@listserver.u2ug.org
Sent: 05/22/2010 11:57 AM
Subject: Re: [U2] receiving error message XX record corrupt on logto
AH what about refiling each of the F5-Accounts with Restrictions
screens
from /SEC.GROUP.SETUP? Those have checksums as well - and refer to
systems
this out.
Susan Lynch
F. W. Davison Company, Inc.
- Original Message -
From: Boydell, Stuart stuart.boyd...@spotless.com.au
To: U2 Users List u2-users@listserver.u2ug.org
Sent: 05/22/2010 6:34 PM
Subject: Re: [U2] receiving error message XX record corrupt on logto
Susan,
Can you try
Support doesn't run on a standard clock, my friend... My only regret is
that we haven't put this one to bed yet, at least not confirmed.
On Sat, May 22, 2010 at 4:38 PM, Dave Laansma dlaan...@hubbardsupply.comwrote:
What are you people doing 'working' on a Saturday?!
Sincerely,
David
That's interesting, because refiling the group records is usually all it
takes. Did you refile the ROOT record?
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
To recap: you logged in as the SB user, refiled all of the groups, and
you're still getting the XX message corrupt message? XX is a system?
user? group? account?
Just trying to clear my head and understand what SB+ thinks is incorrect.
I wouldn't think this would be much of an issue, but
: Kevin King precisonl...@gmail.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: 05/22/2010 11:38 AM
Subject: Re: [U2] receiving error message XX record corrupt on logto
To recap: you logged in as the SB user, refiled all of the groups, and
you're still getting the XX message corrupt message
AH what about refiling each of the F5-Accounts with Restrictions screens
from /SEC.GROUP.SETUP? Those have checksums as well - and refer to systems.
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Susan Lynch
Sent: Sunday, 23 May 2010 01:48
To: U2 Users List
Subject: Re: [U2] receiving error message XX record corrupt on logto
Kevin, XX is the first system (first menu option) on the account
,
Susan Joslyn
SJ+ Systems Associates, Inc.
PRC - IT Governance for U2/Multivalue.
From: Susan Lynch sly...@fwdco.com
To: U2 Users List u2-users@listserver.u2ug.org
Subject: Re: [U2] receiving error message XX record corrupt on logto
Message-ID: 004b3459d050475daf942cfccd93c...@susanhome
Content
-users@listserver.u2ug.org
Subject: [U2] receiving error message XX record corrupt on logto
I have this happening at a client site and I've been all through the
re-file
everything and it won't quit. It happens *consistently* if I have more
than
one session open, but still happens intermittently when I
...@listserver.u2ug.org] On Behalf Of Susan Joslyn
Sent: Saturday, May 22, 2010 6:37 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] receiving error message XX record corrupt on logto
I have this happening at a client site and I've been all through the
re-file
everything and it won't quit. It happens *consistently
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
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, you said As far as I know, the user did not edit the record, he went
through the screens, so the checksum should be ok. Ah, if only it were
that simple. In some earlier releases of SB+ (and possibly as late as 5.3,
though I thought it was corrected in 5.2) if someone editing something in
List u2-users@listserver.u2ug.org
Sent: 05/21/2010 4:51 PM
Subject: Re: [U2] receiving error message XX record corrupt on logto
Susan, you said As far as I know, the user did not edit the record, he
went
through the screens, so the checksum should be ok. Ah, if only it were
that simple. In some
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
16 matches
Mail list logo
