Possible reasons for suse_register to return improper code

Execute command result: HTTP Status 400 - An improper code was supplied.

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.