Possible reasons for suse_register to return improper code

This document (7014777) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Desktop 11
SUSE Linux Enterprise High Availability Extension 11
SUSE Linux Enterprise Point of Service
SUSE Linux Enterprise Real Time Extension
SUSE Linux Enterprise Server 11
SUSE Linux Enterprise Server 10
SUSE Linux Enterprise Server for VMware
SUSE Manager
SUSE Studio

Situation

This article is aiming at any SUSE Linux Enterprise version using the suse_register command (provided since SLES 10) and will cover possible situations when suse_register returns with:
Execute command result: HTTP Status 400 - An improper code was supplied.

Cause

Possible reasons for this return code are:
  1. There was a typing error in the key. Please verify if the activation code has been entered properly.
     
  2. The key is not active yet. Please check with a support representative.
     
  3. The installed baseproduct gets registered using the wrong code. Each key is assigned to a special baseproduct, activating a SLES with e.g. a key for SLES for VMware or vice versa is not possible. To check which products are installed please run

    zypper pd

    or list the appropriate files in /etc/products.d/ and check if the correct key for the product has been used during the registration.
     
  4. An activation code is missing. This situation is possible if SLES acts as basesystem and add-on products like High Availability Extension or Open Enterprise Server are installed which require an additional activation code. In this case the suse_register command needs to get expanded using an additional "-a regcode-productname <regcode>" statement, e.g.

    OES:
    suse_register -a email=emailaddress -a regcode-sles=regcode -a regcode-oes=oesregcode

    HAE:
    suse_register -a email=emailaddress -a regcode-sles=regcode -a regcode-hae=haeregcode

    The appropriate option names for -a regcode-* can be found out by running suse_register -p which will start a connection with secure-www.novell.com (*) and list the possible options.

(*) NOTE: :
The Novell Customer Center (NCC) and nu.novell.com or secure-www.novell.com is not available anymore. SLE10 and SLE11 Systems still registered to the Novell Customer Center (NCC) can be migrated to the SUSE Customer Center (SCC) as outlined at:
https://www.suse.com/support/kb/doc/?id=000019508

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7014777
  • Creation Date: 21-Mar-2014
  • Modified Date:28-Sep-2022
    • SUSE Linux Enterprise Desktop
    • SUSE Linux Enterprise High Availability Extension
    • SUSE Linux Enterprise Point of Service
    • SUSE Linux Enterprise Server
    • SUSE Studio
    • SUSE Manager
    • SUSE Linux Enterprise Real Time Extension

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center