Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Receiving Error When Attempting to Add User | SBS 2011
Hello All-
On a clients system when I went to create a user, I received two cryptic errors within the SBS console (Unexpected Error & MessageManagement).
When I dug down into the adduser log, I came across this error:
I did some searching online and came across two articles that were not much help as all checked out on this server.
This error does not seem to be affecting anything except the creation of users in the SBS console, when it gets to the creation of the exchange account. Nothing to my knowledge has changed on the server, with the exception of a few group policies and group membership changes.
System is SBS 2011, all up-to-date.
Let me know if you have any further questions.
-Jared
On a clients system when I went to create a user, I received two cryptic errors within the SBS console (Unexpected Error & MessageManagement).
When I dug down into the adduser log, I came across this error:
Connecting to remote server servername failed with the following error message : The WinRM client cannot process the request. The WinRM client tried to use Negotiate authentication mechanism, but the destination computer (SERVERNAME:80) returned an 'access denied' error. Change the configuration to allow Negotiate authentication mechanism to be used or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the local computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic.
I did some searching online and came across two articles that were not much help as all checked out on this server.
This error does not seem to be affecting anything except the creation of users in the SBS console, when it gets to the creation of the exchange account. Nothing to my knowledge has changed on the server, with the exception of a few group policies and group membership changes.
System is SBS 2011, all up-to-date.
Let me know if you have any further questions.
-Jared
Asked:
Who is Participating?
yo_bee-
No problems on that front. It seems to me that it is an issue with the scripts that are running to do a whole slew of things in the SBS console (creating user, adding mail account, etc.)
Let me know if you have any other thoughts?
-Jared
No problems on that front. It seems to me that it is an issue with the scripts that are running to do a whole slew of things in the SBS console (creating user, adding mail account, etc.)
Let me know if you have any other thoughts?
-Jared
What account is being used on the IIS front?
Are you doing it from the Server or from a client machine when you run the Web Console?
Are you doing it from the Server or from a client machine when you run the Web Console?
yo_bee-
SBS plays a bit differently, and does most of this through it's backend.
Also, the SBS console is an application on SBS servers and it is being done on the server itself on the built-in Administrator account.
-Jared
SBS plays a bit differently, and does most of this through it's backend.
Also, the SBS console is an application on SBS servers and it is being done on the server itself on the built-in Administrator account.
-Jared
yo_bee-
The SBS console is it's own application. It has some ties to IIS, but the console itself does not run IIS.
-Jared
The SBS console is it's own application. It has some ties to IIS, but the console itself does not run IIS.
-Jared
Here's what I'd recommend,
Create a user using normal ADUC, attach it to a mailbox using EMC - if this works - then SBS Console is to be blamed.
Second part
Create a user using normal ADUC, attach it to a mailbox using SBS console (Don't have the console handy with me right now) - see if this works, if this works - possibly the AD Account creation in SBS Console is going cranky.
Regards,
Exchange_Geek
Create a user using normal ADUC, attach it to a mailbox using EMC - if this works - then SBS Console is to be blamed.
Second part
Create a user using normal ADUC, attach it to a mailbox using SBS console (Don't have the console handy with me right now) - see if this works, if this works - possibly the AD Account creation in SBS Console is going cranky.
Regards,
Exchange_Geek
Exchange_Geek-
I am certain that it is the SBS console throwing the errors.
I added a normal user in the ADUC and attached a mailbox using EMC and it worked without a problem.
It seems to be the link or connection between the console and exchange that is causing the issue. It runs a whole slew of powershell commands when creating a user, and I am not entirely sure why this all of sudden came up.
Thanks.
-Jared
I am certain that it is the SBS console throwing the errors.
I added a normal user in the ADUC and attached a mailbox using EMC and it worked without a problem.
It seems to be the link or connection between the console and exchange that is causing the issue. It runs a whole slew of powershell commands when creating a user, and I am not entirely sure why this all of sudden came up.
Thanks.
-Jared
Please check for underlaying issues using the BPA.
You need at least version 1.3
http://www.microsoft.com/en-us/download/details.aspx?id=15556
Download and install this first:
http://www.microsoft.com/en-us/download/details.aspx?id=16475
Hope that helps,
Olaf
You need at least version 1.3
http://www.microsoft.com/en-us/download/details.aspx?id=15556
Download and install this first:
http://www.microsoft.com/en-us/download/details.aspx?id=16475
Hope that helps,
Olaf
Olaf-
Both of those were previously installed and ran.
I re-ran the BPA and it came back with no significant issues. Should it be displaying anything more than just the ping information and the version of the server, if there is nothing wrong?
-Jared
Both of those were previously installed and ran.
I re-ran the BPA and it came back with no significant issues. Should it be displaying anything more than just the ping information and the version of the server, if there is nothing wrong?
-Jared
Is OWA working happily?
Are all of your IIS Websites started?
Is your SharePoint site listening on Port 80 and stopping the Default Web Site from starting?
Are all of your IIS Websites started?
Is your SharePoint site listening on Port 80 and stopping the Default Web Site from starting?
Alan-
Yes, OWA and RWW are functioning properly.
All IIS sites are started and sharepoint is on a separate port.
-Jared
Yes, OWA and RWW are functioning properly.
All IIS sites are started and sharepoint is on a separate port.
-Jared
If you only get ping info running the BPA you are running version 1.
You need version 1.3
Download the following and choose repair.
http://www.microsoft.com/en-us/download/details.aspx?id=15556
2nd file: WSSG-KB2699813-X64-ENU.msp
Run BPA again.
Olaf
You need version 1.3
Download the following and choose repair.
http://www.microsoft.com/en-us/download/details.aspx?id=15556
2nd file: WSSG-KB2699813-X64-ENU.msp
Run BPA again.
Olaf
I have just run into this problem as well
Didn't get as far as looking in the log file, just did an iisreset which seemed to sort it
Didn't get as far as looking in the log file, just did an iisreset which seemed to sort it
Alan-
That's exactly what it was. I have removed the KB2506143 (Power Shell 3.0) as that made the most sense re. the powershell scripts that occur when creating an account in the SBS console.
After rolling that back, all is well again.
Thanks for the insight on this.
-Jared
That's exactly what it was. I have removed the KB2506143 (Power Shell 3.0) as that made the most sense re. the powershell scripts that occur when creating an account in the SBS console.
After rolling that back, all is well again.
Thanks for the insight on this.
-Jared
Hi,
I have the same problem on an SBS 2011 Server.
How to uninstall the patch? If I search for KB2506143 there is none. However, there was an update for Windows Server 2008 R2 (KB 2779562) that contained PS 3.0.
When adding users in the SBS Server Console there is an error when it crates the mailbox. It must be done manually.
I have the same problem on an SBS 2011 Server.
How to uninstall the patch? If I search for KB2506143 there is none. However, there was an update for Windows Server 2008 R2 (KB 2779562) that contained PS 3.0.
When adding users in the SBS Server Console there is an error when it crates the mailbox. It must be done manually.
Lorenzo09-
In the 'Control Panel' | 'Programs and Features', on the left tree you will see 'View Installed Updates', from there you can see all the updates that have been applied to this server. From there, you can uninstall the update that seems to be causing this issue.
Because this question is close, I would recommend that you open a new question if my answer above does not resolve your issue.
Hope this helps.
-Jared
In the 'Control Panel' | 'Programs and Features', on the left tree you will see 'View Installed Updates', from there you can see all the updates that have been applied to this server. From there, you can uninstall the update that seems to be causing this issue.
Because this question is close, I would recommend that you open a new question if my answer above does not resolve your issue.
Hope this helps.
-Jared
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month5 days, left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
Check Control Panel for recent installs and if you want, roll them back one at a time and see if that improves the situation.
If it does, you can either re-install it or hold fire for a while and see if a newer version is released.