Q: How do I disable a service?

It is a very odd animal. Others report the Service running, but I never see it. The Office apps will crash if it doesn't exist, but you don't have it at all.

Barney-15E wrote:

 

It is a very odd animal. Others report the Service running, but I never see it. The Office apps will crash if it doesn't exist, but you don't have it at all.

I'll never understand MS, but I use Excel all the time and Outlook (only when I have to connect to Exchange servers) regularly, so I have an interest in ensuring that they work.

I have also installed 14.3.1 and the crash message has stopped.  Office365Service still launches when I open Excel or Word, BUT ONLY IF I'M CONNECTED TO THE INTERNET.  If I turn off Wi-Fi, start Excel, then restart Wi-Fi, Office365Service does not appear to launch.  Don't know what this means...obviously the "utility" is internet related, but not needed to use the main MS applications.

Now it's launching whether Wi-Fi is on or not...I promise I will never use Office 365.

I'm having the same issue.  Office 365 crashing thirteen times per the console log on 5 March because I was on the computer almost all day.  Yesday was only four times since I was gone over 1/2 the day out of the office. Today 7 March already crashed twice in two hours.  Per the Microsoft community, there are instructions on how to disable the service via some terminal commands but it would seem there would be an easier method to uninstall or disable vice having to use terminal commands.

Anybody done this already to disable?

So, did you find reliable instructions on how to disable?

The issue with this particular service is, from what I understand, it doesn't appear in the normal list of services for the Office applications (i.e. it doesn't appear in the .plist files).

If you have a means of disabling the service, please do pass along.

While it's 'harmless' that it crashes, it's still really annoying.

And yes, I am running the latest Mac OS X and latest office patches.

Thanks.

Hi Mark, I have not found a method/process to disable and like you was hoping someone in the forum would have the steps.

Having just updated yesterday to the new 14.3.2 update I am encouraged that Office365Service is no longer running in the background, and I have not had any reports of it crashing either since the update. Looks like they may have fixed the problem at last - certainly the previous update did not fix the problem for me.

My biggest frustration now is that the release notes make no mention of any fixes in this respect - why not mention it and set everyone's mind at rest?

"My biggest frustration now is that the release notes make no mention of any fixes in this respect - why not mention it and set everyone's mind at rest?"

What?! Microsoft do something reasonable, logical and helpful?? MICROSOFT???!!!

I mean, hope springs eternal, but this is Microsoft, after all...

;-)/2

I agree. I updated to 14.3.2 and have not seen the error pop up at all.

That's a good thing. I also concur that the release notes don't mention this issue at all, which I had hoped it would so that we would help re-assure me that Microsoft was at least aware of the issue.

Fingers crossed that this problem doesn't re-appear.

The news is out - new and improved Office 2013. I wonder exactly what Office365Service is communicating. There is no option in the preferences to turn off the office 365 service.

You can quit by going to Activity Monitor and searching for it then clicking 'Quit Process' if that is what you want to do.

That only works for a few minutes, then it re-launches itself again.  I've even noticed that when we're logged off our individual profiles it will launch and literally buzz until we come and click "Deny/Allow"  I am SO FRUSTRATED because it freezes whatever app I'm working in until I click it.  And if I click "Deny" while WORD or EXCEL is open, then the apps freeze and I have to F-Quit.  This is beyond exasperating.  Has anyone found a workaround yet?

You might want to consider starting a new discussion. Since this one is a couple of years old, less people are likely to look at it. A new post would be much more visible. You can link to this one.

Thanks Eric. I actually got an answer from Microsoft (!!) so will post it for others.  Thank you for the coaching.