none
Auto-start Services Not Running : Windows Server Office 365 Integration Service

    Question

  • Hi to All,

    Yesterday Microsoft Released Update Rollup 1 for Windows Server 2012 Essentials. The update applied without errors as far as Windows Update concerned but upon restarting the server i am getting the error below:

    Auto-start Services Not Running: Windows Server Office 365 Integration Service.

    I am getting this error always in my Health Reports (auto or manually generated) and sometimes in my Dashboard Alerts.

    I repair this error by clicking "Try to repair this error" and it goes away, but my health reports are still showing the error.

    In the afternoon i will check my services status to find out if the service is not starting correctly and post back.

    Any Advice? 

    Wednesday, February 27, 2013 7:33 AM

Answers

  • It appears that the problem here is that a service became marked as disabled during the automatic updates last night and that leads to the "Windows Server Office 365 Integration Service" crashing. To restore correct operation:

    • Check if the "Windows Server Password Synchronization Service" is marked as startup type "Disabled".
    • If so, edit its properties and set startup type to "Automatic" and then start the service.
    • Then start the "Windows Server Office 365 Integration Service" and verify it does not crash. In my case it would always crash within 25 seconds or so.

    So far here so good after about 30 minutes. I'll report back in the morning if everything is still running.

    • Proposed as answer by Susan BradleyMVP Thursday, February 28, 2013 2:47 AM
    • Marked as answer by Wiseman Thursday, February 28, 2013 7:03 AM
    Thursday, February 28, 2013 2:15 AM

All replies

  • I get the same thing, and the service is definitely not running. Looking in the event log, I see the following:

    Application: SharedServiceHost.exe

    Framework Version: v4.0.30319

    Description: The process was terminated due to an unhandled exception.

    Exception Info: System.InvalidOperationException

    Stack:

       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ObjectModelBaseExtended`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Invoke(System.Action)

       at Microsoft.WindowsServerSolutions.O365Integration.UpdateO365IntegrationDataTask.CleanUpPasswordSyncData(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.TimerQueue.FireNextTimers()


    Wednesday, February 27, 2013 7:56 AM
  • Same issue here
    Wednesday, February 27, 2013 2:53 PM
  • I, too, am having this problem.  I "repaired" the issue and verified that the service is currently running.  But, I suspect something will stop it shortly.

    Betsy Getreu

    Wednesday, February 27, 2013 3:42 PM
  • It appears the service starts, attempts - Microsoft.WindowsServerSolutions.O365Integration.UpdateO365IntegrationDataTask.CleanUpPasswordSyncData via an ASP.NET v4 operation and then the process terminates due to an unhandled exception.

    A reboot doesn't help, the same problem just continues.

    The service is set to try to restart after the first two failures and then takes no action on the third failure. I changed the service properties to continue to restart the service every 10 minutes so I can see if it ever comes back. 

    Wednesday, February 27, 2013 3:52 PM
  • Hang loose folks while I call out the troups, do you have Office 365 integration hooked up or not?
    Wednesday, February 27, 2013 5:08 PM
  • Yes, I do have Office 365 integration enabled.  However, I did not link my domain.  I tried that and it made a big mess - unfortunately, I can't recall the exact details at the moment.

    Betsy Getreu

    Wednesday, February 27, 2013 5:14 PM
  • Since the start Office 365 is an Internal Part of my Installation.

    So the answer is yes it is integraded with 2 Licenses (P1 Plan)

    Wednesday, February 27, 2013 5:20 PM
  • Can you guys do me a favor?

    1. See if the box was rebooted after installing updates last night (go into control panel, windows updates, view installed updates - see if the essentials rollup is "pending reboot"

    2.  reboot the box and report back if the issue goes away?

    Wednesday, February 27, 2013 6:25 PM
  • Nevermind, first posted said "restarting the server "

    There went that theory.

    Wednesday, February 27, 2013 6:37 PM
  • Yes we are running Office 365 integration. And we have tried multiple reboots without affect.

    We have the service set to try to restart every 5 minutes and continue to get the event id 1026 from the .NET runtime - details above, followed by event id 1000 with these details:

    Faulting application name: SharedServiceHost.exe, version: 6.2.9805.0, time stamp: 0x504a9e6d
    Faulting module name: KERNELBASE.dll, version: 6.2.9200.16451, time stamp: 0x50988aa6
    Exception code: 0xe0434352
    Fault offset: 0x000000000003811c
    Faulting process id: 0xc80
    Faulting application start time: 0x01ce1500c9449c13
    Faulting application path: C:\Program Files\Windows Server\Bin\SharedServiceHost.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: 15859cb3-80f4-11e2-9418-cc52af3e5fc8
    Faulting package full name:
    Faulting package-relative application ID:

    Wednesday, February 27, 2013 6:42 PM
  • Same thing here with E4 licenses.  Have rebooted several times and restarted the service multiple times.  This is on a freshly installed and configured server as of Saturday, February 23rd.
    Wednesday, February 27, 2013 7:02 PM
  • My server rebooted after the rollup was applied and I have rebooted twice to no effect.

    Betsy Getreu

    Wednesday, February 27, 2013 7:05 PM
  • If anyone would like to be a sample dead body that I can open up an
    official support case on - email me at susan-at-msmvps.com (replace the
    -at- with an @) and we can speed up the investigation a bit.
     
    Wednesday, February 27, 2013 7:05 PM
  • Here's some more info. After the two "Error" event ids show above, there are two event ids of 1001 for the windows error reporting. They include:

    Fault bucket , type 0
    Event Name: CLR20r3
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: sharedservicehost.exe
    P2: 6.2.9805.0
    P3: 504a9e6d
    P4: ProviderFrameworkExtended
    P5: 6.2.9805.0
    P6: 504a9e83
    P7: 38
    P8: 12
    P9: System.InvalidOperationException
    P10:

    Attached files:
    C:\Windows\Temp\WER7B95.tmp.appcompat.txt
    C:\Windows\Temp\WER7C71.tmp.WERInternalMetadata.xml
    C:\Windows\Temp\WER7C72.tmp.hdmp
    C:\Windows\Temp\WER8992.tmp.dmp

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_sharedservicehos_414c4b7d56bde9a53965ebc8308956178dc16_cab_175a8aa9

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: b80cfc0a-8111-11e2-9418-cc52af3e5fc8
    Report Status: 4
    Hashed bucket:

    And the second one:

    Fault bucket -899683359, type 5
    Event Name: CLR20r3
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: sharedservicehost.exe
    P2: 6.2.9805.0
    P3: 504a9e6d
    P4: ProviderFrameworkExtended
    P5: 6.2.9805.0
    P6: 504a9e83
    P7: 38
    P8: 12
    P9: System.InvalidOperationException
    P10:

    Attached files:
    C:\Windows\Temp\WER7B95.tmp.appcompat.txt
    C:\Windows\Temp\WER7C71.tmp.WERInternalMetadata.xml
    C:\Windows\Temp\WER7C72.tmp.hdmp
    C:\Windows\Temp\WER8992.tmp.dmp

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_sharedservicehos_414c4b7d56bde9a53965ebc8308956178dc16_0dca91bd

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: b80cfc0a-8111-11e2-9418-cc52af3e5fc8
    Report Status: 0
    Hashed bucket: c858d146f807f7ea92caeb42c09420e4

    • Marked as answer by Wiseman Thursday, February 28, 2013 7:03 AM
    • Unmarked as answer by Wiseman Thursday, February 28, 2013 7:03 AM
    Wednesday, February 27, 2013 7:18 PM
  • It appears that the problem here is that a service became marked as disabled during the automatic updates last night and that leads to the "Windows Server Office 365 Integration Service" crashing. To restore correct operation:

    • Check if the "Windows Server Password Synchronization Service" is marked as startup type "Disabled".
    • If so, edit its properties and set startup type to "Automatic" and then start the service.
    • Then start the "Windows Server Office 365 Integration Service" and verify it does not crash. In my case it would always crash within 25 seconds or so.

    So far here so good after about 30 minutes. I'll report back in the morning if everything is still running.

    • Proposed as answer by Susan BradleyMVP Thursday, February 28, 2013 2:47 AM
    • Marked as answer by Wiseman Thursday, February 28, 2013 7:03 AM
    Thursday, February 28, 2013 2:15 AM
  • That's actually a brand new service that gets installed as part of UR1.  What I don't understand is why it's being installed as disabled.
    Thursday, February 28, 2013 2:47 AM
  • Susan opened a case for me.  MSFT basically did as rhertzler describes after checking some certs and file permissions.  Its kinda hard to know if this service is supposed to run since its not one that I was familiar with.  I failed to install the update on one box and wait, next time I will not roll out so quick.

    I did the same on two other boxes and all is still running just peachy.


    Scott

    Thursday, February 28, 2013 3:00 AM
  • Susan also opened a case for me and the MS tech found exactly what rhertzler describes above.  The Windows Server Password Synchronization Service was disabled.  Once he changed startup to automatic and started this service and the O365 integration service, all was well.  My thanks to Susan.

    Betsy Getreu

    Thursday, February 28, 2013 4:28 AM
  • I believe that this case is know closed. MSFT Support instruct as all with the Solution rhertzler suggested. Therefor All points go to his/her.

    I want to thanks Susan Bradley who was quick as a Lightning to offer her support and access to MSFT Support services. Great Job.

    Keep the Dice rolling....

    Thursday, February 28, 2013 7:09 AM
  • The service is brand new and came in with this update rollup.  The real question as this time is why is it being set to disabled and not to automatic and running.  That I don't know at this time and we will get to the bottom of.

    Thank you for being this week's winners in "let's prove again why we don't like Patch Tuesday " sweepstakes (tongue in cheek sarcasm)

    Thursday, February 28, 2013 7:19 AM
  • Hi Susan et al,

    Thanks for chasing this up - I can't believe the first UR has this problem and will be interested to find out what happened here as it seems to be a fundamental part of testing that has failed.

    I'm building one of these for a client next week and would prefer not to have to start building a list of do's and don'ts so early in the lifecycle!

    Thursday, February 28, 2013 8:25 AM
  • All is still well this morning so indeed I think we have a solution here. But agreed, this certainly helps to make patch tuesday a day to be nervous about. None of us likes spending half a day tracking down solutions to problems we didn't create...
    Thursday, February 28, 2013 1:50 PM
  • Office 365 Integration Service reports not running after install Update Rollup 1 for Windows Server 2012 Essentials (KB2781267) - TechNet Articles - United States (English) - TechNet Wiki:
    http://social.technet.microsoft.com/wiki/contents/articles/16168.office-365-integration-service-reports-not-running-after-install-update-rollup-1-for-windows-server-2012-essentials-kb2781267.aspx

    <sigh> 

    Thursday, February 28, 2013 3:06 PM
  • I'm having this exact issue! I've attempted the above solutions with no success. My O365 service starts but stops shortly after. Eventually when I try to start the service I'm given Error 1067. No amount of googling has solved this problem. 
    Thursday, March 13, 2014 2:14 AM
  • This is an extremely old thread from a year ago that now as a resolution.

    So I'd strongly recommend you post a new post and also include the exact error message you get.


    Unfortunately TechNet subscriptions aren't coming back, sorry folks :-(

    Thursday, March 13, 2014 2:32 AM
  • Also be clear what Essentials version you are running.

    Unfortunately TechNet subscriptions aren't coming back, sorry folks :-(

    Thursday, March 13, 2014 2:33 AM