The Samba-Bugzilla – Bug 11184
adding new users using RSAT failed with An error occurred: Contact your system administrator
Last modified: 2015-05-04 00:09:45 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 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
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!
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...
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.
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
I'll need network traces and level 10 logs to investigate this further.