• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1475
  • Last Modified:

Windows Server Essentials E-Mail Service Failing

After recently completing a migration from SBS 2003 to Server Essentials 2012 R2, moments after decomissioning the old domain controller, the essentials e-mail service which is responsible for handling the cloud sync to azure and office 365 will not start.

Microsoft are stumped by this too so I wondered if there was anyone else out there that had similar issues with 2012 essentials r2 since installing windows updates.?
1
tegenius
Asked:
tegenius
  • 6
  • 3
1 Solution
 
Cliff GaliherCommented:
Can you be more specific? The o365 integration wizard will not run while the SBS 2003 server is still ON the network, and yet your question implies that it had been run and was working. This is contrary to how the system behaves. Please be specific about the environment, what has been done, and what errors you are getting.

Just to be VERY clear, essentials does not have an email service. It has an integration service that makes it easier to create o365 accounts easier (seamless actually) when creating users through the essentials dashboard. No email service runs locally and no syncing of data occurs.
0
 
tegeniusAuthor Commented:
Apologies for the lack of specifics.

The FSMO roles have been transferred, exchange decommissioned (by deleting the server object out of ADSI) and the old server removed from the network.

We then began with the Office 365 integration wizard and began assigning pre-existing Microsoft Online accounts to our users so passwords would sync to the cloud. It worked for about an hour and then all of a sudden, the microsoft online status for all accounts was "unknown", the details from the office 365 tab became "unknown" also.

The only changes that occurred during this period was adding the DHCP role and decommissioning all the old small business server group policies and... windows update which included the latest rollup.

The only link to this "unknown" status is the fact that this e-mail integration service has stopped.

I'm struggling to understand what is stopping this from running. The actual event log is confusing.

Application: SharedServiceHost.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.DirectoryServices.DirectoryServicesCOMException
Stack:
   at System.DirectoryServices.DirectoryEntry.CommitChanges()
   at Microsoft.WindowsServerSolutions.MailService.ActiveDirectoryHelper.SetLocalUserPrincipleName(System.String, System.String)
   at Microsoft.WindowsServerSolutions.O365Integration.UpdateO365IntegrationDataTask.CleanUpMappingData(Microsoft.WindowsServerSolutions.O365Integration.O365User[])
   at Microsoft.WindowsServerSolutions.O365Integration.UpdateO365IntegrationDataTask.Run()
   at Microsoft.WindowsServerSolutions.O365Integration.BackgroundTask.TimerCallback(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.TimerQueueTimer.CallCallback()
   at System.Threading.TimerQueueTimer.Fire()
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Open in new window


Faulting application name: SharedServiceHost.exe, version: 6.3.9600.16384, time stamp: 0x5215ca62
Faulting module name: KERNELBASE.dll, version: 6.3.9600.16496, time stamp: 0x52b3f283
Exception code: 0xe0434352
Fault offset: 0x0000000000005a88
Faulting process id: 0x253c
Faulting application start time: 0x01cf429464892f22
Faulting application path: C:\Windows\System32\Essentials\SharedServiceHost.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: a63a17ba-ae87-11e3-80bf-9c8e995696bc
Faulting package full name: 
Faulting package-relative application ID: 

Open in new window

0
 
tegeniusAuthor Commented:
Here's some screenshots:

Unknown account status.
Office 365 status unknown.
0
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
Cliff GaliherCommented:
Make sure your clock and time zone are both still correct. Open the services control panel and verify all automatic services are in a running state.
0
 
Cliff GaliherCommented:
And again, for clarification, you say this is 2012 R2?? You also say updates included a rollup. Essentials 2012 R2 does not *have* any rollups, so as before, some inconsistency exists in your description.
0
 
tegeniusAuthor Commented:
I lost access to this account so apologies for the late response.

This issue was resolved by the Microsoft dev team. It was caused by the same microsoft online account being added to 2 AD users via the dashboard. This was caused by the fact the dashboard did not refresh with the up to date information once the first account had been added.

To resolve this, one of the duplicate AD accounts had to be deleted and recreated from scratch, The service then started up again.
0
 
tegeniusAuthor Commented:
Microsoft support resolved the issue after a lengthy debugging process.
0
 
Pgh_HabitatCommented:
I am having the exact same issue.  The dashboard shows "unknown" for all Microsoft Online Accounts, and no information in the Office 365 integration tab.   Windows Server Essentials Email Service is stopped.   If I manually restart the service, all is good.   Checked AD and no issues with duplicate accounts being assigned (as tegenius noted).   Any help on this?
0
 
tegeniusAuthor Commented:
It was caused by 2 accounts having the same e-mail address in the local directory. One had successfully synced to the cloud but the other hadn't and was causing the whole synchronisation to fail. Best using powershell to export your AD to csv and checking all your accounts over.
0
 
tegeniusAuthor Commented:
As for your exact issues, not sure :( Microsoft support may be able to help, even the Azure AD team on 365 :)
0

Featured Post

Problems using Powershell and Active Directory?

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

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now