similar to: samba-tool classicupgrade throws uncaught exception

other errors that I have when I try to join BDC with samba 4 is the follow Try the mounting the filesystem with the 'acl' option.") Deleted CN=DANTES,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=eccmg,DC=cupet,DC=cu ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: Your filesystem or build does not

Hi Everybody, I'm stumped. I'm pretty sure I've tried everything to get this to work. I'm trying to join my CentOS 6 server to my Server 2008 AD Domain. I'm using SerNet's samba4 packages: [root at files ~]# samba -V Version 4.1.4-SerNet-RedHat-7.el6 I've done the xattr and acl tests and they all come out just fine. So I don't think it has to do with ACLs

I copied all the database files of samba3 as is mentioned in the wiki - The classicupgrade process <https://wiki.samba.org/index.php/Samba_Classic_Upgrade_(NT4-style_domain_to_AD)#The_classicupgrade_process> But if the winbindd_idmap.tdb file is in the folder, the errors occur. See below: Importing idmap database > ERROR(assert): uncaught exception > File

I used to upgrade samba3 to samba4 with almost successful with one problem, administrator can't access. As administrator, by default it is the only user account that is given full control over the system. My query is how to change the administrator password? we have one account which can join to the samba 4 AD based on the migrated data but the problem can't change the administrator or

You're right, man! Sorry! My mistake! I put that file because I read in somewhere about the persistent and temporary files regarding .tdb files. The winbindd_idamp.tbm was on that list, and I think that's why I left it in the folder. :D Another doubt. For the provisioning starts, I had to comment out the line referring to the ldap backend in the smb.conf of samba3. # passdb backend =

On Fri, 9 Dec 2016 11:11:56 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > From: "Stefan G. Weichinger via samba" <samba at lists.samba.org> > To: samba at lists.samba.org > Subject: Re: [Samba] Samba on Debian 8; NT4 domain, win10 > Date: Fri, 9 Dec 2016 11:11:56 +0100 > Reply-To: "Stefan G. Weichinger"

Ok. I uncomment that line and put: passdb backend = ldapsam:ldap://127.0.0.1 Error message: Provisioning > smbldap_search_domain_info: Searching > for:[(&(objectClass=sambaDomain)(sambaDomainName=EMPRESA))] > smbldap_open_connection: connection opened > failed to bind to server ldap://127.0.0.1 with > dn="cn=Manager,dc=empresa,dc=com" Error: Invalid credentials

Hi All, Attempting to do a classicupgrade and getting this error: *Adding groups* *Importing groups* *Committing 'add groups' transaction to disk* *Adding users* *Importing users* *Adding users to groups* *Committing 'add users to groups' transaction to disk* *ERROR(<type 'exceptions.ValueError'>): uncaught exception - zero length field name in format* * File

> > Is ldap running on the computer you are trying to run the classicupgrade > on? Yes. I need to modify other files too? On Thu, May 21, 2015 at 2:39 PM, Rowland Penny <rowlandpenny at googlemail.com> wrote: > On 21/05/15 18:22, Elias Pereira wrote: > >> Ok. I uncomment that line and put: >> >> passdb backend = ldapsam:ldap://127.0.0.1 >> >

On Fri, Mar 18, 2016 at 4:04 PM, Andrew Bartlett <abartlet at samba.org> wrote: > The upgrade code assumes you run on the same host. I realise now that > folks doing an upgrade use that an an opportunity to upgrade hardware, > and keep old systems as fallbacks, so the assumptions cause trouble. > > Make the new host identical in terms of the data needed to upgrade >

On Sun, 16 Sep 2018 10:51:25 -0400 Bill Baird via samba <samba at lists.samba.org> wrote: > I ran the same thing with 4.8.5 and it work without any issues: > > Adding groups > Importing groups > Committing 'add groups' transaction to disk > Adding users > Importing users > Committing 'add users' transaction to disk > Adding users to groups >

On Sun, 16 Sep 2018 11:28:56 -0400 Bill Baird <Bill.Baird at phoenixmi.com> wrote: > Python is 2.6, but why wouldn't it throw an error during > configure/make? No, the python code isn't compiled. > > I'm using Amazon Linux. Would you like to raise a bug report ? Here: https://bugzilla.samba.org/ Rowland > > On Sun, Sep 16, 2018 at 11:22 AM Rowland Penny

Am 2016-12-09 um 11:11 schrieb Stefan G. Weichinger via samba: > Could not add group name=Domain Admins ((68, "samldb: Account name > (sAMAccountName) 'Domain Admins' already in use!")) I think this is my problem (on the old host/pdc): # net groupmap list Domain Admins (S-1-5-21-2777655458-4002997014-749295002-1006) -> root Domain Guests

I'm trying the classicupgrade, and it is crashing out: ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: Could not add member 'S-1-5-21-305843216-174882882- 1673945419-42545' to group 'S-1-5-21-305843216-174882882-1673945419- 1231' as either group or user record doesn't exist: Unable to find GUID for DN File

On 21/05/15 16:31, Elias Pereira wrote: > I copied all the database files of samba3 as is mentioned in the wiki - The > classicupgrade process > <https://wiki.samba.org/index.php/Samba_Classic_Upgrade_(NT4-style_domain_to_AD)#The_classicupgrade_process> > > But if the winbindd_idmap.tdb file is in the folder, the errors occur. See > below: > > Importing idmap database

> > Then why can the upgrade not contact the ldap server ? I dont know! :( Was ldap running on another computer before ? I installed a temporary openLDAP backend on the new host. Can you post the smb.conf from the old PDC ? the one you are trying to > upgrade from. I sent my smb.conf to your private e-mail. On Thu, May 21, 2015 at 3:08 PM, Rowland Penny <rowlandpenny at

On 21/05/15 17:28, Elias Pereira wrote: > You're right, man! Sorry! My mistake! > > I put that file because I read in somewhere about the persistent and > temporary files regarding .tdb files. The winbindd_idamp.tbm was on that > list, and I think that's why I left it in the folder. :D > > Another doubt. For the provisioning starts, I had to comment out the line >

On Fri, Mar 18, 2016 at 2:39 PM, Andrew Bartlett <abartlet at samba.org> wrote: > Exactly. Think about it a little - how can it determine the group > membership, if the users/groups do not exist locally on the host doing > the migration? To clarify then: Do I need both the users and groups on the new host as they are on the old host, or just the groups? Is there any constraint

Hello, I'm migrating to samba4 (samba 4.0.2 in Debian 6.0.6) After copying .tdb files and smb.conf and migrating ldap server to the new server and configured it. When I run: /usr/loca/samba/bin/samba-tool domain classicpugrade --dbdir=samba --user-xattrs=yes --realm=sadom.espel.com samba/smb.conf I get: Reading smb.conf WARNING: The "idmap backend" option is deprecated WARNING:

On 21/05/15 18:22, Elias Pereira wrote: > Ok. I uncomment that line and put: > > passdb backend = ldapsam:ldap://127.0.0.1 Is ldap running on the computer you are trying to run the classicupgrade on ? It needs to connect to the ldap server, so if the ldap server is running on another computer, you need to use either the FQDN of that computer or its ipaddress. Rowland > >