Red Hat Bugzilla – Bug 235004
Problem registering system:Error Class Code: 70
Last modified: 2007-11-30 17:07:10 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Description of problem:
I cannnot registering my system.
Whenever I try to run it I put in all the info they ask me for,
but by the end of the process (Sending my profile information to Red Hat
Network) I get an error message saying -
"Problem registering system:
Error Class Code: 70...."
Steps to Reproduce:
2.Enter all relevant data and keep pressing Next 'till you get to the
last part where it says:
3. Press "Next"
Actual Results: I get an error message saying "Problem registering
Expected Results: Registration status: success?
It never worked before, so I don't know...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.Enter all relevant data and click Next.
The following message appears.
Problem registering system:
Error Class Code: 70
Error Class Info:
All available subscriptions for the requested channel have been exhausted.
Please contact a Red Hat Network Sales associate.
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.
My system is NOT registered in RedHat Network website.
And I cannot check errata.
% rpm -q up2date
User email@example.com's account has been closed
I get a similar result, I think it's because I/we had a paid for subscription
and although I think it should still be possible to get software updates
through up2date? ("the Redhat Network is a free service") it doesn't work.
Maybe I need to change to server? All information gratefully received!
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.