# failed upgrade to SP3 **URL:** \ **Category:** SLES Updates\ **Created:** [January 28, 2015, 9:21pm UTC](https://forums.suse.com/t/failed-upgrade-to-sp3/26612 "2015-01-28T21:21:35Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![System1](https://avatars.discourse-cdn.com/v4/letter/s/51bf81/32.png) [@System1](https://forums.suse.com/u/System1)\ **Post date:** [January 28, 2015, 9:21pm UTC](https://forums.suse.com/t/failed-upgrade-to-sp3/26612/1 "2015-01-28T21:21:35Z")
I had a Sles 11 Sp2 server that I attempted to upgrade to SP3 using the zypper commands because the wagon method failed. Somewhere along the way the server now thinks it’s now sles for vmware instead of sles 11 sp2 so the machine is no longer registered since I don’t have a registration code for sles for vmware, nor do I want one. How do I get it to recognize it for what it is which is Sles 11 SP2? ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [January 28, 2015, 9:40pm UTC](https://forums.suse.com/t/failed-upgrade-to-sp3/26612/2 "2015-01-28T21:40:02Z")
> [@](#): > > On Wed 28 Jan 2015 07:21:35 PM CST, Mike wrote: > > I had a Sles 11 Sp2 server that I attempted to upgrade to SP3 using the > zypper commands because the wagon method failed. Somewhere along the > way the server now thinks it’s now sles for vmware instead of sles 11 > sp2 so the machine is no longer registered since I don’t have a > registration code for sles for vmware, nor do I want one. How do I > get it to recognize it for what it is which is Sles 11 SP2? Hi If you log into SCC and remove the system and then re-registering it with your activation code should sort it out. You might want to also clean out the credentials; ```auto rm /etc/zypp/credentials.d/NCCcredentials ``` – Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.32-33-default If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below… Thanks! ---
**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\ **Post date:** [January 29, 2015, 12:40pm UTC](https://forums.suse.com/t/failed-upgrade-to-sp3/26612/3 "2015-01-29T12:40:47Z")
On 28/01/2015 19:40, malcolmlewis wrote: [color=blue] > If you log into SCC and remove the system and then re-registering it > with your activation code should sort it out. > > You might want to also clean out the credentials; > > ` > rm /etc/zypp/credentials.d/NCCcredentials > `[/color] Since this is SLES11 SP2/SP3 you’ll need to log into Novell Customer Center (as indicated by …/NCCcredentials). ## HTH. Simon SUSE Knowledge Partner * * * ## If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below. Thanks. ---
**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\ **Post date:** [January 29, 2015, 12:51pm UTC](https://forums.suse.com/t/failed-upgrade-to-sp3/26612/4 "2015-01-29T12:51:56Z")
On 28/01/2015 19:21, Mike wrote: [color=blue] > I had a Sles 11 Sp2 server that I attempted to upgrade to SP3 using the > zypper commands because the wagon method failed. Somewhere along the > way the server now thinks it’s now sles for vmware instead of sles 11 > sp2 so the machine is no longer registered since I don’t have a > registration code for sles for vmware, nor do I want one. How do I get > it to recognize it for what it is which is Sles 11 SP2?[/color] How was the server upgraded - what steps did you follow? What do “cat /etc/\*release” and “zypper se -t product” output? If the server thinks it’s SLES for VMware rather than “regular” SLES then removing it from NCC and re-registering it will only achieve the same outcome. Is it possible the server was actually SLES11 SP2 for VMware before the upgrade? ## HTH. Simon SUSE Knowledge Partner * * * ## If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below. Thanks.