Bug 11184 - adding new users using RSAT failed with An error occurred: Contact your system administrator
Summary: adding new users using RSAT failed with An error occurred: Contact your syste...
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: 4.2.0
Hardware: All All
: P5 critical (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Samba QA Contact
Depends on:
Reported: 2015-03-30 16:39 UTC by Vladimir
Modified: 2015-05-04 00:09 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir 2015-03-30 16:39:36 UTC
relates to 4.1.17+ (4.2.0 release too)

when trying to create new user from Windows 8.1 or Windows 2012 using RSAT
it fails with the following error:
An error occurred: Contact your system administrator.

also unable to reset users passwords with the same error.

Domain is working no errors anywhere neither eventlogs nor syslog nor samba_logs.
I'm ABLE to create\delete groups and OUs using RSAT though... 

Current Solution hardly googled: 
Remove Windows Updates KB2992611 and KB3000850

after that everything is working as expected! 
Please help!
Comment 1 Louis 2015-04-30 10:34:59 UTC
please read : 
which says : 
The update that this article describes has been replaced by a newer update on December 9th, 2014

Did you install KB3018238 also after KB2992611 and KB3000850
Comment 2 Vladimir 2015-04-30 13:01:27 UTC
oh dear god! Microsoft! 
no i didn't! i had no idea about it, neither it dropped from windows update!
But still i had very intense time googling, caz it was a total malfunction! 
Can we have a FAQ of some kind about it? It's really annoying!
Comment 3 Vladimir 2015-04-30 14:31:16 UTC
I've double checked: KB3018238 is not installed in normal clean system which is using windows update service... instead KB2992611 is installed twice, i guess the old one which were causing the errors and the new one which you referenced as KB3018238. 
Still it can be a major issue for some one.. we need at least to mention this info...
Comment 4 Andrew Bartlett 2015-05-01 02:07:42 UTC
Can you please double-check the 4.2 release for this.  We expect this issue has been addressed with the release of samba 4.2.0, due to fixing bug 11097.

Comment 5 Vladimir 2015-05-01 08:22:16 UTC
Andrew, i'm using SerNet's Samba 4.2 release builds so it was in 4.2 (not sure if it's 4.2.1 havent tested yet)
anyway as i mentioned earlier, if you have windows server clean install and samba 4.2+ you might also have double KB2992611 installation through windows update (as it describes in https://support.microsoft.com/en-us/kb/2992611/en-us) and everything is working... so this may be an issue only for servers which were installed in the past... but still, i thought it's worth mentioning
Comment 6 Andrew Bartlett 2015-05-04 00:09:45 UTC
I'll need network traces and level 10 logs to investigate this further.