When I clicked on the “View Warning Details” I got some more details.

There was an error that read “unexpected error” with a yellow sign beside it as well as a “messaging management” error with a red X beside it.

I closed out of the user account setup wizard. The user account was created but the email address wouldn’t be. If you are receiving this error, here is the fix I found.

Step One: Go to Control Panel > Programs > View Installed Updates . Search for update, KB2506143. If it is installed, uninstall the update. You will need to restart the server once the uninstall is complete.

Step Two: After you restart the server, open the SBS console again and try creating a user account. The setup wizard should complete successfully this time.

After I restarted the server, I opened the Windows Small Business Server Console 2011 and tried adding a user account. I was able to add the user account and email address without a problem!

Conclusion: After Update KB2506143 (Power Shell 3.0) the functionality to add a new user account with an email address was broken with servers running Exchange 2010. After the uninstall of that update, everything worked again. Here is another article you can refer to about this issue.  Feel free to post in the comments if you have another suggestion or if a fix has been issued. Thanks

This was posted by techspeeder.

Hat Tip: jaredr80

I decided to install Acronis on the Small Business Server 2011 to see if that would fix my issues. I tried kicking off a couple backups with Acronis and I ran into a similar issue. I was getting quite frustrated with this problem. Here are the steps I used to get my SBS 2011 to backup successfully.

Step One: Start a backup. Go into  Event Viewer and see if there are any VSS error logs. In my situation there were hundreds of them. This is what my VSS error log said.

Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class CLSID { 423bbc78-9b20-4bbe-a967-b63ec43bc7f3} [0x80040154, Class not registered].

Operation: Creating instance of hardware provider, Obtain a callable interface for this provider, List interface for all providers supporting this context, Get Show Copy Properties . . . 

Step Two: Open a CMD prompt as an administrator. Run this command:  vssadmin list writers . Check your results. If all of your VSS writers say Stable – No error, then your VSS writers are fine. If your VSS writers are failing or corrupting you may need to reboot the server. In my case, the VSS writers were fine.

Type this command: vssadmin list providers . This will show the VSS writers capable of taking a system snapshot when backing up your sbs 2011. Take note of how many VSS providers you have.

Next type: diskshadow  . Once that comes up type:  list providers .  You will now see the Provider ID for each VSS writer that you have. 

Step Three: Take note of what your VSS error said in your event log. For mine I noticed that a VSS writer with the ID of { 423bbc78-9b20-4bbe-a967-b63ec43bc7f3} was giving me lots of errors. I matched up the ID number of the event log to the ID number of command prompt output. I noticed that the VSS Lifeline HW Provider was the writer that was giving me all my grief.

Step Four: Since I didn’t need that VSS writer, I decided to remove that writer. Here is how to remove your troublesome VSS writer.  Please be advised that you do this at your own risk! Incorrect use of the Windows Registry could cause your operating system to crash. Be sure to back up your Registry before deleting these keys.

• Open the Registry Editor (Start -> Run -> enter “regedit”, hit enter)

• Navigate to the this registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Providers
• Delete the registry tree with the GUID referenced in the event log and CMD prompt that was giving you issues.

Go back to command prompt and type in diskshadow and then list providers. The VSS writer that was faulty should now be gone. Type exit in command prompt to close diskshadow.

• {optional but recommended} Reboot the server.

Step Five: I tried starting a backup with Acronis and  it worked!! After a couple successful backups with Acronis I decided to try Windows Server Backup.  I started a backup and to my amazement the backup went through successfully! I have run numerous backups since and they have gone through without a hitch!

I hope this helps you out. Please post in the comments if this worked for you. Like us on Facebook and follow me on Twitter!

This was posted by techspeeder.

Thanks to this post for pointing me in the right direction.