Results 1 to 3 of 3

Thread: Registering against SMT server Subscription expired messages

  1. #1

    Registering against SMT server Subscription expired messages

    Hi,
    Just did an upgrade of our GMS server - SLES11SP2> SP3, then GWM2.0>2.1
    I have all the appropriate repos mirrored on our SMT server and our subscription for SLES and GroupWise are current and the SMT server is syncing every night.
    I ran the SLES upgrade using Yast2 wagon, it added the new repos and upgraded successfully, however the registration failed with the following error:
    Product: SUSE Linux Enterprise Server 11 SP3 (x86_64, )
    Subscription: expired (full version)
    Message: Subscription is expired.
    Expiry: 2008-05-01 01:00:00
    Product: GroupWise Mobility Service (, )
    Subscription: expired (full version)
    Message: Subscription is expired.
    Expiry: 2008-05-01 01:00:00
    A zypper lr showed the SLES11SP3 & GMS repos were actually added and active.

    Then I did the GMS update and had the same errors. Here's what zypper lr gives:
    # | Alias | Name | Enabled | Refresh
    ---+-------------------------------------------------------------+---------------------------------------------------------+---------+--------
    1 | GroupWise-Mobility-Service_2.0-1.3 | GroupWise-Mobility-Service 2.0-1.3 | No | No
    2 | GroupWise_Mobility_Service_2.1 | GroupWise Mobility Service 2.1 | Yes | No
    3 | Mobility_Pack_1.2.2 | Mobility Pack 1.2.2 | No | No
    4 | Novell-data-synchronizer-mobility-pack-x86_64-966_1.2.4 | Novell-data-synchronizer-mobility-pack-x86_64-966 1.2.4 | No | No
    5 | Novell_Data_Synchronizer_Mobility_Pack_1.2.4_x64 | Novell Data Synchronizer Mobility Pack | No | No
    6 | Novell_Data_Synchronizer_Mobility_Pack_1.2.5 | Novell Data Synchronizer Mobility Pack 1.2.5 | No | No
    7 | Novell_Mobility_Data_Synchroniser | Novell Data Synchronizer Mobility Pack | No | No
    8 | SMT-http_hamstall02v_hamcoll_sa_edu_au:Mobility-2.1-Updates | Mobility-2.1-Updates | Yes | Yes
    9 | SMT-http_hamstall02v_hamcoll_sa_edu_au:SLES11-SP1-Updates | SLES11-SP1-Updates | No | No
    10 | SMT-http_hamstall02v_hamcoll_sa_edu_au:SLES11-SP2-Core | SLES11-SP2-Core | No | No
    11 | SMT-http_hamstall02v_hamcoll_sa_edu_au:SLES11-SP2-Updates | SLES11-SP2-Updates | No | No
    12 | SMT-http_hamstall02v_hamcoll_sa_edu_au:SLES11-SP3-Pool | SLES11-SP3-Pool | Yes | Yes
    13 | SMT-http_hamstall02v_hamcoll_sa_edu_au:SLES11-SP3-Updates | SLES11-SP3-Updates | Yes | Yes
    14 | SUSE-Linux-Enterprise-Server-11-SP2_11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | No | No
    15 | novell-groupwise-mobility-service-2.0.1 | novell-groupwise-mobility-service-2.0.1 | Yes | Yes
    I've highlighted the active repos in blue (haven't cleaned up the old ones yet).
    When I look at the SMT Subscription Report, it's listing a number of expired subscriptions, including SLES expired 2008 and GMS expired in April 2015. Both products were renewed this year and the Subscription report shows this in the Active subscription section.
    It looks like the problem is the Activation codes on the existing GMS server haven't changed, so they have now expired. Looking at the report, there are 10 other servers in the same situation. Is there some way to change the activation code to the current one?

    Cheers,
    Ian

  2. Re: Registering against SMT server Subscription expired mess

    Hi Ian,

    > Is there some way to change the activation code to the current one

    have you tried to re-register the machines with the new activation code? From "suse_register --help":
    Code:
    Example:
                                                                                                                                                                                                                                                                                   
     suse_register.pl -n -a email=company@example.com -a regcode-sles=03474hdkndg3934957340
    A different way I used with NCC (have not yet tried with SCC) was to move machines to the new subscription NCC(web)-wise.

    Regards,
    Jens
    From the times when today's "old school" was "new school"

    If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...

  3. #3

    Re: Registering against SMT server Subscription expired mess

    Attempting to re-register with the current activation codes just gave the same message about the expired subscriptions. Reading the suse_register help, I noticed the -E option to erase the current subscription. Running that and then re-registering with the current activation codes seems to have successfully updated the codes. Oh, and contrary to what the help info says, the command is suse_register without the .pl!

    Thanks for your help.

    Cheers,
    Ian

    Quote Originally Posted by jmozdzen View Post
    Hi Ian,

    > Is there some way to change the activation code to the current one

    have you tried to re-register the machines with the new activation code? From "suse_register --help":
    Code:
    Example:
                                                                                                                                                                                                                                                                                   
     suse_register.pl -n -a email=company@example.com -a regcode-sles=03474hdkndg3934957340
    A different way I used with NCC (have not yet tried with SCC) was to move machines to the new subscription NCC(web)-wise.

    Regards,
    Jens
    Last edited by imoore; 14-Jul-2015 at 03:32.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •