THE OFFICIAL BLOG OF THE SBS "DIVA"

Well I hit a bump.  The user role wizard is not liking something here...

The cryptic error of MessagingManagement Unexpected error occurred.  And the help box goes ot a "you have encountered a user role error, for more information see "Troubleshooting Windows Small Business Server 2008" in the Windows Small Business Server Technical Library (http://go.microsoft.com/fwlink/?LinkID=111318

Hmm...but not seeing anything on point -- http://technet.microsoft.com/en-us/library/cc527572(WS.10).aspx

And they should be pointing me to the best helpful place that of the log files. http://blogs.technet.com/sbs/archive/2008/10/01/key-small-business-server-2008-log-files.aspx

Which is the ChangeUsersRole.log

In it is this error...

[8748] 091113.195720.3589: Messaging: MessagingTaskException: Failure during monad command execution: set-mailbox -- Error# (800001)
[8748] 091113.195720.3589: Messaging: Inner exception: An Exchange 2007 server on which an address list service is active cannot be found.
[8748] 091113.195720.3589: Messaging: Stack Trace:
[8748] 091113.195720.3589: Messaging:    at Microsoft.Exchange.Configuration.Tasks.Task.ThrowTerminatingError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.ApplyRusPolicy(RecipientUpdateService rus, ADRecipientSession recipientSession, ADRecipient recipient, TaskVerboseLoggingDelegate logHandler, TaskErrorLoggingDelegate writeError, TaskErrorLoggingDelegate throwTerminatingError, TaskWarningLoggingDelegate writeWarning)
   at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalProcessRecord()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
   at System.Management.Automation.Cmdlet.DoProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
[3264] 091113.195720.3745: AdminTME: Committer: Completed called

Now to be fair I'm doing this setup funky.  I have a RWW access url that is not remote.domain.com ... rather it's domainpc.com   That's it.  But my email address is domain.com.  So earlier I went into Exchange and did a change domain and renamed the mailboxes.

But I certainly have moved my mailboxes and they are no longer legacy ones.

I may have shot myself in the foot there.  So I got to redo the mailbox policy...but hang on when I go to edit it back to what it was I get:

Huh?  This is ON the SBS 2008 box...how can it not find an Exchange Server 2007?

And this is where I shot myself in the foot another way.  I didn't patch.  But I have rebooted.  And I hadn't yet set up alerts that would have told me that a key Exchange service wasn't running like it was supposed to be.

 And what nailed me is that this is an Exchange 2007 sp1 box that I have not installed Update rollup (now 9) but what we're looking for is rollup 5 OR LATER.  Up until then Exchange has this lovely habit of forgetting to start services.. one of which is important for this wizard to run.  You need the MS Exchange System Attendant running and it was not.

http://social.technet.microsoft.com/Forums/en/exchangesvradmin/thread/bc1cef27-78ee-49d4-87eb-21f6f2e09079

What I SHOULD HAVE DONE right after I built the new server is to take a solid/good backup and patch the server.

You want Windows 2008 sp2 on there asap.  (Hopefully the SP2 media is more in the channel soon I'm having trouble finding it as a Open Value Software Assurance Customer).  Then you need to get that Exchange rollup on there.  But MAKE SURE you have a backup before applying patches.  I did this to myself because I was lazy and didn't want to patch right after installing the server and I certainly did not want to patch/install patches DURING the install... which wouldn't install the Exchange patches anyway during the initial setup so it would not have prevented this anyway.

Bingo...that fixed it right up....