Hi -- 

I constantly have to remove the Microsoft Database Daemon from my Login Items but it keeps coming back. I have locked the Login Options page in my Accounts -- and I'm the Administer for all of my Macs -- but still that darn "feature" keeps reappearing. It causes me extra work with my backup program since I need to remove it and then restart in order to synchronize 5 different Macs and I cannot do that if the Database Daemon is already running. I've tried to remember to remove it from the Login Items when I shut down each machine, but sometime I forget to remove it. It then causes me issues again the next time I start that computer up again.

Is there any setting I can make that will prevent the Database Daemon from being added automatically to my Login Items?

Thank you

Using Mountain Lion and Office 2011. Went away over Christmas over which time my MacBook Pro had gone into hibernation as the battery level had dropped and I'd left the original power supply in the office. Go a new one today and powered up. Tried to go into Outlook which downloaded the outstanding mail and the posted an error that the database needed rebuilding. This the Database Daemon has steadfastly refused to do. After reading through some of the posts here none seemed to address the exact issue I have because after several attempts to recover as suggested I now had a dialog box permanently up saying the Database needs to be rebuild. Close this dialog down and another will open immediately. Try to rebuild the database and a dialog box will open immediately suggesting that I rebuild the database, and another, and another, and another. I've had up to 7 of these dialog boxes open at one time.

 

So I restored from the backup in Time Machine to the latest full backup, then recovered all my post, which was OK until all the software updates also came down. On rebooting I'm back where I started - rebuild the database with the dialog box refusing to go away. Closing the Daemon doesn't solve the problem as it restarts itself.

 

So How can I stop this dialog box, rebuild the database and get on with my life?

 

Best regards

 

Rob

Dear all,

as i updated to 10.8.2 suddenly Microsoft Office stopped working with the Database Daemon crashing. This is what i already did:

* Deinstalled Office completely with all library et all files
* Installed Office with latest updates
* Reinstalled 10.8.2
* created new user, same error

Did anyone experience this error? Thank you in advance!

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_CRASH (SIGTRAP)
Date/Time: 2012-11-29 09:12:39 +0000
Application Name: Microsoft Database Daemon
Application Bundle ID: com.microsoft.outlook.database_daemon
Application Signature: MDlr
Application Version: 14.0.0.100825
Crashed Module Name: unknown
Crashed Module Version: unknown
Crashed Module Offset: unknown
Blame Module Name: unknown
Blame Module Version: unknown
Blame Module Offset: unknown
Application LCID: 1031
Extra app info: Reg=en Loc=0x0407 
Crashed thread: 0
MacBook Air --- updates are automatic ... Get to the install selected hard drive and then get "must close" these before install can continue. Cannot find Microsoft Database Daemon or SyncServicesAgent to close those --- what am I doing wrong? 

Thanks

The only thing I can think of that has changes recently is that I updated the Microsoft Error Reporting a couple days ago, but now on 2 different Macbook Pro's (both running Mountain Lion), Outlook freezes with the beach ball.   If I wait several minutes it eventually unfreezes, but since email is critical, its very frustrating.  I've noticed this behaviour on 2 different machines today.   Both are connected to an Exchange server and multiple IMAP server as well.   Any ideas?

When using Outlook 2011 for Mac, the computer slows down randomly. We can start typing and for no reason the beachball will appear for an extended period of time.

 

We've archived all email older than 3 weeks, cleaned up caches, ran updates and rebuilt the mailbox but the issue persists.

 

It appears that the Microsoft AU Daemon is the culprit, but I have no idea how to fix it.

 

Any ideas?

Since migration from Entourage to Outlook with Mountain Lion as O/S I was outlook was crashing with the message: "Database Daemon Fatal Error" After various patches to Outlook and O/S  the frequency of crashes reduced substantially.  The frequency has increased dramatically when i migrated to Lion O/S.  How can i fix this as its extremely frustrating 
I downloaded Office:Mac 2011 update 14.2.3; I had to turn off Microsoft database Daemon & Sync Services Agent from the Activity Monitor  or the update would not load. After I finished downloading the update - I restarted my  Mac. When I went to my Outlook program it was totally wiped out, no contacts, e-mails, mailboxes etc. Everything was gone. What happened. I have no idea what to do---- Please HELP ME.
Running 14.2.3. of the entire Office suite.  I've had this update installed for weeks.

Today Outlook crashed, giving me a Daemon error.  I tried a rebuild, and the Daemon crash report just kept coming up every 5 seconds.

Outlook refused to open.

I trashed the Daemon files, under the impression they would be regenerated when I opened Outlook again.  No luck. Get 3 O bounces, then a quit.

Tried to recover the daemon files from Time Machine, but it somehow couldn't find them.  No luck.

Rebuilt database.  Copied to User folder desktop, created new one.  No luck.

Finally trashed Outlook from Applications.  Reinstalled from DVD disc.  Attempted to open.  No luck.

Downoaded all 3 updates from Microsoft.  Tried to install SP1, but it won't allow me, as it says there's no version it applies to.  Totally out of luck.

As you can see, I've tried many of the remedies prescribed in these forums and I'm now just dead in the water.  Please, please, please, someone help me. 

Thanks, in advance.

Brian
I tried to open Outlook and I got the message that "the database daemon has encountered a problem and has to close". Also Outlook rebuilt my identity but I still kept getting this same message when I tried to open it. I would really appreciate help with this problem.