# Registration Problem

**URL:** <https://forums.suse.com/t/registration-problem/26970>\
**Category:** SLES for System Z\
**Created:** [April 24, 2015, 11:27pm UTC](https://forums.suse.com/t/registration-problem/26970 "2015-04-24T23:27:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![PaceMainline](https://avatars.discourse-cdn.com/v4/letter/p/6f9a4e/32.png) [@PaceMainline](https://forums.suse.com/u/PaceMainline)\
**Post date:** [April 24, 2015, 11:27pm UTC](https://forums.suse.com/t/registration-problem/26970/1 "2015-04-24T23:27:15Z")

</div>

Trying to register a new system for online updates. When I go through Yast and enter my code I get an error.  
Error  
Registration server error.  
Retry registration later.  
Details: Validation failed: Uuid should be formatted as UUID

Well that doesn’t make a lot of sense.  
So I went and requested a new registration code for Linux Enterprise Server on System z.  
I receive an email saying that my code had been updated. So I copy and paste the new registration code into yast and now I get a new error.

Error  
Registration Failed  
Details: Invalid registration code

Any ideas what I do now?

---

<div class="post-metadata">

**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:** [April 24, 2015, 11:51pm UTC](https://forums.suse.com/t/registration-problem/26970/2 "2015-04-24T23:51:03Z")

</div>

> [@](#):
>
> On Fri 24 Apr 2015 08:34:01 PM CDT, PaceMainline wrote:
> 
> Trying to register a new system for online updates. When I go through  
> Yast and enter my code I get an error.  
> Error  
> Registration server error.  
> Retry registration later.  
> Details: Validation failed: Uuid should be formatted as UUID
> 
> Well that doesn’t make a lot of sense.  
> So I went and requested a new registration code for Linux Enterprise  
> Server on System z.  
> I receive an email saying that my code had been updated. So I copy and  
> paste the new registration code into yast and now I get a new error.
> 
> Error  
> Registration Failed  
> Details: Invalid registration code
> 
> Any ideas what I do now?

Hi  
Is the registration code visible in SCC? [https://scc.suse.com/dashboard](https://scc.suse.com/dashboard)

Sometimes it can take a day or so to filter into the system… Also you  
don’t have multiple accounts, it can be allocated to a different  
entity that does not match the email your using.

If it’s still an issue, I recommend a followup in the SUSE Customer  
Center subforum here which is monitored by the SCC folks.

–  
Cheers Malcolm Â°Â¿Â° LFCS, SUSE Knowledge Partner (Linux Counter #276890)  
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-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!

---

<div class="post-metadata">

**Author:** ![PaceMainline](https://avatars.discourse-cdn.com/v4/letter/p/6f9a4e/32.png) [@PaceMainline](https://forums.suse.com/u/PaceMainline)\
**Post date:** [April 24, 2015, 11:56pm UTC](https://forums.suse.com/t/registration-problem/26970/3 "2015-04-24T23:56:08Z")

</div>

Received this reply from IBM in another forum.

SuSE engineering has determined that the SUSEconnect problem is due to "  
for registration purposes on s390x SUSEConnect requires the uuid to be  
extracted via `read_values -u` SUSEConnect either expects an empty output  
or a properly formatted uuid."

SuSE provided a s390-tools-1.24.1-38.17.8188.1.PTF.919293.s390x.rpm  
containing:

- Wed Mar 04 2015 [puzel@suse.com](mailto:puzel@suse.com)

- update read\_values: print error messages to standard error  
(bnc#919293)

Wonder I find this updated RPM?

---

<div class="post-metadata">

**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:** [April 25, 2015, 12:20am UTC](https://forums.suse.com/t/registration-problem/26970/4 "2015-04-25T00:20:09Z")

</div>

> [@](#):
>
> On Fri 24 Apr 2015 09:04:01 PM CDT, PaceMainline wrote:
> 
> Received this reply from IBM in another forum.
> 
> SuSE engineering has determined that the SUSEconnect problem is due to  
> "  
> for registration purposes on s390x SUSEConnect requires the uuid to be  
> extracted via `read_values -u` SUSEConnect either expects an empty  
> output  
> or a properly formatted uuid."
> 
> SuSE provided a s390-tools-1.24.1-38.17.8188.1.PTF.919293.s390x.rpm  
> containing:
> 
> - Wed Mar 04 2015 [puzel@suse.com](mailto:puzel@suse.com)
> 
> - update read\_values: print error messages to standard error  
> (bnc#919293)
> 
> Wonder I find this updated RPM?

Hi  
You need to contact the SUSE folks;  
[https://www.suse.com/support/kb/doc.php?id=7016361](https://www.suse.com/support/kb/doc.php?id=7016361)

As an aside can you read the bug?  
[https://bugzilla.suse.com/show\_bug.cgi?id=919293](https://bugzilla.suse.com/show_bug.cgi?id=919293)

–  
Cheers Malcolm Â°Â¿Â° LFCS, SUSE Knowledge Partner (Linux Counter #276890)  
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-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!
