[Samba] Samba-tool dbcheck shows "incorrect GUID" after update from alpha17 to beta8

[X-Dimension at gmx.net]

-------- Original-Nachricht --------
> Datum: Thu, 4 Oct 2012 12:22:54 +0200
> Von: Michael Wood <esiotrot at gmail.com>
> An: Julian Timm <X-Dimension at gmx.net>
> CC: samba at lists.samba.org
> Betreff: Re: [Samba] Samba-tool dbcheck shows "incorrect GUID" after update from alpha17 to beta8

> On 4 October 2012 09:46, Julian Timm <X-Dimension at gmx.net> wrote:
> >
> > -------- Original-Nachricht --------
> >> Datum: Wed, 3 Oct 2012 16:56:42 +0200
> >> Von: Michael Wood <esiotrot at gmail.com>
> >> An: X-Dimension at gmx.net
> >> CC: samba at lists.samba.org
> >> Betreff: Re: [Samba] Samba-tool dbcheck shows "incorrect GUID" after
> update from alpha17 to beta8
> >
> >> On 3 October 2012 16:26,  <X-Dimension at gmx.net> wrote:
> >> > After updating our Samba4 server from alpha17 to beta8 "samba-tool
> >> dbcheck" shows 24 "incorrect GUID" errors.
> >> > What does it mean and what should i do to fix this?
> >>
> >> Try samba-tool dbcheck --fix.
> >>
> >> Also, why did you not install rc2 instead of beta8?
> >
> > I don't want to compile every Samba version for myself, so i'm using
> > the Zentyal 2.3 PPA. The latest Samba version here is beta8, but rc2
> packages are in testing and should be available soon.
> >
> > After running samba-tool dbcheck --fix the errors still exists, when
> running dbcheck again.
> 
> Try posting the errors to the list and maybe someone will be able to
> say what causes them.
> 
> -- 
> Michael Wood <esiotrot at gmail.com>

Ok, here is an example:

ERROR: incorrect GUID component for member in object CN=Mitarbeiter,OU=Benutzer,DC=test,DC=lan - <GUID=c385ad50-c728-41ba-8b94-22fa07b57b41>;<SID=S-1-5-21-2936403297-3018184044-1011683372-1153>;CN=Max Müller,OU=Benutzer,DC=test,DC=lan
unable to find object for DN CN=Max Müller,OU=Benutzer,DC=test,DC=lan - (No such Base DN: CN=Max Müller,OU=Benutzer,DC=test,DC=lan)
Not removing dangling forward link

All of these database errors affecting users who have german umlauts
in their names like Ä,Ö,Ü. 
These users are also not shown within the Microsoft RSAT AD manager.
When i add a new user now like "Horst Müller" with the management tool, i get the error that the user could not be verified and can't login, but RSAT still creates the user.

Is there a simple way to correct this problem?