From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922
Description of problem:
I used the up2date --register command and it will not register my
system. I currenty have 2 update entitlements and it simply will not
register the system.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Check RHN that I actually have the entitlements available
2.Tried the command again, and it failed again.
Actual Results: This is the error message I get when I run up2date
Problem registering system:
Registration failed: RHN Software Management service entitlements
Error Class Code: 91
Error Class Info: Registration token unable to entitle system: maximum
An error has occurred while processing your request. If this problem
persists please enter a bug report at bugzilla.redhat.com.
If you choose to submit the bug report, please be sure to include
details of what you were trying to do when this error occurred and
details on how to reproduce this problem.
By 'available', do you mean that they exist, or that they are actually
not being used?
By 'available' I mean I have 3 entitlements, and 2 were available.
I've since corrected the problem. (I still can't see why it didn't
work the first time around). But after alot of stuffing around, I must
have setup an activation key, somewhere along the line. I ended up
removing it, and the RH9 system I had activated a while back. And now
it's working. And I was then able to reactivate the RH9 system again,
and all is well. So now the RHN system states that I have 3
entitlements, and 1 available.
Huh. OK. So this has therefore been resolved?
I have the same problem wiht a RHES 3. simply i have disable
the "Activation Keys" in the rhn account and so i can register the
*** Bug 118918 has been marked as a duplicate of this bug. ***
*** Bug 177775 has been marked as a duplicate of this bug. ***
*** Bug 200884 has been marked as a duplicate of this bug. ***
*** Bug 172568 has been marked as a duplicate of this bug. ***
*** Bug 234328 has been marked as a duplicate of this bug. ***