Microsoft Database Daemon

F

flydcjets

Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: pop

When opening Entourage I get the following:

MICROSOFT DATABASE DAEMON HAS ENCOUNTERED A PROBLEM AND NEEDS TO CLOSE. WE ARE SORRY FOR THE INCONVENIENCE.

Please tell Microsoft about the problem.

I did several times and I'm not sure how to resolve it.

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-11-28 19:59:10 -0700
Application Name: Microsoft Database Daemon
Application Bundle ID: com.microsoft.entourage.database_daemon
Application Signature: MDde
Application Version: 12.1.3.080930
Crashed Module Name: CoreFoundation
Crashed Module Version: unknown
Crashed Module Offset: 0x000c415a
Blame Module Name: CoreFoundation
Blame Module Version: unknown
Blame Module Offset: 0x000c415a
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x92b3415a in .objc_class_name___NSCFSet + 0x929EA21A (CoreFoundation + 0x000c415a)
# 2 0x92b38540 in .objc_class_name___NSCFSet + 0x929EE600 (CoreFoundation + 0x000c8540)
# 3 0x000bf0cf in __mh_execute_header + 0x000BE0CF (Microsoft Database Daemon + 0x000be0cf)
# 4 0x00109d2a in CSharablePtr<CTimeZonesMap>::Set(CTimeZonesMap*) + 0x0000007C (Microsoft Database Daemon + 0x00108d2a)
# 5 0x000c0ee6 in __mh_execute_header + 0x000BFEE6 (Microsoft Database Daemon + 0x000bfee6)
# 6 0x0001dea8 in __mh_execute_header + 0x0001CEA8 (Microsoft Database Daemon + 0x0001cea8)
# 7 0x0001eafb in __mh_execute_header + 0x0001DAFB (Microsoft Database Daemon + 0x0001dafb)
# 8 0x000206ca in __mh_execute_header + 0x0001F6CA (Microsoft Database Daemon + 0x0001f6ca)
# 9 0x00015e8f in __mh_execute_header + 0x00014E8F (Microsoft Database Daemon + 0x00014e8f)
# 10 0x00015f14 in __mh_execute_header + 0x00014F14 (Microsoft Database Daemon + 0x00014f14)
# 11 0x00016a64 in __mh_execute_header + 0x00015A64 (Microsoft Database Daemon + 0x00015a64)
# 12 0x00080346 in __mh_execute_header + 0x0007F346 (Microsoft Database Daemon + 0x0007f346)
# 13 0x00080487 in __mh_execute_header + 0x0007F487 (Microsoft Database Daemon + 0x0007f487)
# 14 0x000870b9 in __mh_execute_header + 0x000860B9 (Microsoft Database Daemon + 0x000860b9)
# 15 0x00087886 in __mh_execute_header + 0x00086886 (Microsoft Database Daemon + 0x00086886)
# 16 0x00054c1b in __mh_execute_header + 0x00053C1B (Microsoft Database Daemon + 0x00053c1b)
# 17 0x0005508f in __mh_execute_header + 0x0005408F (Microsoft Database Daemon + 0x0005408f)
# 18 0x000033ee in __mh_execute_header + 0x000023EE (Microsoft Database Daemon + 0x000023ee)
# 19 0x00003315 in __mh_execute_header + 0x00002315 (Microsoft Database Daemon + 0x00002315)

X86 Thread State:
eax: 0xa02534ec ebx: 0x92b3413b ecx: 0x0000001f edx:0xbfffeac4
edi: 0xa02534f0 esi: 0x00000000 ebp: 0xbfffe9c8 esp:0xbfffe9a0
ss: 0x0000001f eip: 0x92b3415a cs: 0x00000017 ds:0x0000001f
es: 0x0000001f fs: 0x00000000 gs: 0x00000037 eflags:0x00010283

Thread 1:

# 1 0x93a9c5c6 in _signgam + 0x938FCD86 (libSystem.B.dylib + 0x000015c6)
# 2 0x93b2529b in _signgam + 0x93985A5B (libSystem.B.dylib + 0x0008a29b)
# 3 0x007bdd7d in _MerpCreateSession + 0x00000B07 (merp + 0x00002d7d)
# 4 0x007bd3e5 in _MerpCreateSession + 0x0000016F (merp + 0x000023e5)
# 5 0x007bd46c in _MerpCreateSession + 0x000001F6 (merp + 0x0000246c)
# 6 0x007bdf25 in _MerpCreateSession + 0x00000CAF (merp + 0x00002f25)
# 7 0x93acd6f5 in _signgam + 0x9392DEB5 (libSystem.B.dylib + 0x000326f5)
# 8 0x93acd5b2 in _signgam + 0x9392DD72 (libSystem.B.dylib + 0x000325b2)

X86 Thread State:
eax: 0xffffffa6 ebx: 0x93b140bf ecx: 0xb00a0a5c edx:0x93a9c5c6
edi: 0x0000022f esi: 0xfc02a1ab ebp: 0xb00a0ac8 esp:0xb00a0a5c
ss: 0x0000001f eip: 0x93a9c5c6 cs: 0x00000007 ds:0x0000001f
es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000202

Loaded modules:

0: Microsoft Database Daemon (12.1.3.080930 Reg=en Loc=0x0409): /Applications/Microsof
 
K

Kerry

Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: pop

When opening Entourage I get the following:

MICROSOFT DATABASE DAEMON HAS ENCOUNTERED A PROBLEM AND NEEDS TO CLOSE. WE ARE SORRY FOR THE INCONVENIENCE.

Please tell Microsoft about the problem.

I did several times and I'm not sure how to resolve it.

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-11-28 19:59:10 -0700
Application Name: Microsoft Database Daemon
Application Bundle ID: com.microsoft.entourage.database_daemon
Application Signature: MDde
Application Version: 12.1.3.080930
Crashed Module Name: CoreFoundation
Crashed Module Version: unknown
Crashed Module Offset: 0x000c415a
Blame Module Name: CoreFoundation
Blame Module Version: unknown
Blame Module Offset: 0x000c415a
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

# 1 0x92b3415a in .objc_class_name___NSCFSet + 0x929EA21A (CoreFoundation+ 0x000c415a)
# 2 0x92b38540 in .objc_class_name___NSCFSet + 0x929EE600 (CoreFoundation+ 0x000c8540)
# 3 0x000bf0cf in __mh_execute_header + 0x000BE0CF (Microsoft Database Daemon + 0x000be0cf)
# 4 0x00109d2a in CSharablePtr<CTimeZonesMap>::Set(CTimeZonesMap*) + 0x0000007C (Microsoft Database Daemon + 0x00108d2a)
# 5 0x000c0ee6 in __mh_execute_header + 0x000BFEE6 (Microsoft Database Daemon + 0x000bfee6)
# 6 0x0001dea8 in __mh_execute_header + 0x0001CEA8 (Microsoft Database Daemon + 0x0001cea8)
# 7 0x0001eafb in __mh_execute_header + 0x0001DAFB (Microsoft Database Daemon + 0x0001dafb)
# 8 0x000206ca in __mh_execute_header + 0x0001F6CA (Microsoft Database Daemon + 0x0001f6ca)
# 9 0x00015e8f in __mh_execute_header + 0x00014E8F (Microsoft Database Daemon + 0x00014e8f)
# 10 0x00015f14 in __mh_execute_header + 0x00014F14 (Microsoft Database Daemon + 0x00014f14)
# 11 0x00016a64 in __mh_execute_header + 0x00015A64 (Microsoft Database Daemon + 0x00015a64)
# 12 0x00080346 in __mh_execute_header + 0x0007F346 (Microsoft Database Daemon + 0x0007f346)
# 13 0x00080487 in __mh_execute_header + 0x0007F487 (Microsoft Database Daemon + 0x0007f487)
# 14 0x000870b9 in __mh_execute_header + 0x000860B9 (Microsoft Database Daemon + 0x000860b9)
# 15 0x00087886 in __mh_execute_header + 0x00086886 (Microsoft Database Daemon + 0x00086886)
# 16 0x00054c1b in __mh_execute_header + 0x00053C1B (Microsoft Database Daemon + 0x00053c1b)
# 17 0x0005508f in __mh_execute_header + 0x0005408F (Microsoft Database Daemon + 0x0005408f)
# 18 0x000033ee in __mh_execute_header + 0x000023EE (Microsoft Database Daemon + 0x000023ee)
# 19 0x00003315 in __mh_execute_header + 0x00002315 (Microsoft Database Daemon + 0x00002315)

X86 Thread State:
 eax: 0xa02534ec ebx: 0x92b3413b ecx: 0x0000001f edx:0xbfffeac4
 edi: 0xa02534f0 esi: 0x00000000 ebp: 0xbfffe9c8 esp:0xbfffe9a0
  ss: 0x0000001f eip: 0x92b3415a cs: 0x00000017 ds:0x0000001f
  es: 0x0000001f fs: 0x00000000 gs: 0x00000037 eflags:0x00010283

Thread 1:

# 1 0x93a9c5c6 in _signgam + 0x938FCD86 (libSystem.B.dylib + 0x000015c6)
# 2 0x93b2529b in _signgam + 0x93985A5B (libSystem.B.dylib + 0x0008a29b)
# 3 0x007bdd7d in _MerpCreateSession + 0x00000B07 (merp + 0x00002d7d)
# 4 0x007bd3e5 in _MerpCreateSession + 0x0000016F (merp + 0x000023e5)
# 5 0x007bd46c in _MerpCreateSession + 0x000001F6 (merp + 0x0000246c)
# 6 0x007bdf25 in _MerpCreateSession + 0x00000CAF (merp + 0x00002f25)
# 7 0x93acd6f5 in _signgam + 0x9392DEB5 (libSystem.B.dylib + 0x000326f5)
# 8 0x93acd5b2 in _signgam + 0x9392DD72 (libSystem.B.dylib + 0x000325b2)

X86 Thread State:
 eax: 0xffffffa6 ebx: 0x93b140bf ecx: 0xb00a0a5c edx:0x93a9c5c6
 edi: 0x0000022f esi: 0xfc02a1ab ebp: 0xb00a0ac8 esp:0xb00a0a5c
  ss: 0x0000001f eip: 0x93a9c5c6 cs: 0x00000007 ds:0x0000001f
  es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000202

Loaded modules:

0: Microsoft Database Daemon (12.1.3.080930 Reg=en Loc=0x0409): /Applications/Microsof
Click to expand...

Run the Entourage database utility to make sure that your DB isn't
corrupted. On launching Entourage hold down the option key. Choose the
Verify option. If the database reports problems that is why the Daemon
is giving you these errors. If it reports problems you can try rebuild
to repair the database (Note: there is a known issue to Microsoft that
rebuild can cause problems which won't let you launch into your main
identity - period). If rebuild works the daemon errors should stop.
Finally, you can turn off the daemon check by going to the last option
set prefs and untick >Perform Database Integrity....<. I wouldn't
suggest this though as it is trying to tell you that there's a problem
with the Entourage DB.

The other thing I would encourage everyone to do is scream bloody
murder to Microsoft regarding all these issues we're dealing with in
08. They don't seem to listen but I've always felt the squeaky wheel
gets the oil but it is Microsoft we're dealing with.
 
F

flydcjets

On Nov 28, 10:02�pm, (e-mail address removed) wrote: > Version:
2008 > Operating System: Mac OS X 10.5 (Leopard) > Processor: Intel >
Email Client: pop > > When opening Entourage I get the following: > >
MICROSOFT DATABASE DAEMON HAS ENCOUNTERED A PROBLEM AND NEEDS TO CLOSE.
WE ARE SORRY FOR THE INCONVENIENCE. > > Please tell Microsoft about the
problem. > > I did several times and I'm not sure how to resolve it. >
Microsoft Error Reporting log version: 2.0 > > Error Signature: > Exception:
Click to expand...
EXC_BAD_ACCESS > Date/Time: 2008-11-28 19:59:10 -0700 > Application Name:
Microsoft Database Daemon > Application Bundle ID: com.microsoft.entourage.database_daemon
Application Signature: MDde > Application Version: 12.1.3.080930 > Crashed
Click to expand...
Module Name: CoreFoundation > Crashed Module Version: unknown > Crashed
Module Offset: 0x000c415a > Blame Module Name: CoreFoundation > Blame
Module Version: unknown > Blame Module Offset: 0x000c415a > Application
LCID: 1033 > Extra app info: Reg=en Loc=0x0409 > > Thread 0 crashed: >
# 1 0x92b3415a in .objc_class_name___NSCFSet + 0x929EA21A (CoreFoundation
Click to expand...
+ 0x000c415a) > # 2 0x92b38540 in .objc_class_name___NSCFSet + 0x929EE600
(CoreFoundation + 0x000c8540) > # 3 0x000bf0cf in __mh_execute_header
+ 0x000BE0CF (Microsoft Database Daemon + 0x000be0cf) > # 4 0x00109d2a
in CSharablePtr::Set(CTimeZonesMap*) + 0x0000007C (Microsoft Database
Daemon + 0x00108d2a) > # 5 0x000c0ee6 in __mh_execute_header + 0x000BFEE6
(Microsoft Database Daemon + 0x000bfee6) > # 6 0x0001dea8 in __mh_execute_header
+ 0x0001CEA8 (Microsoft Database Daemon + 0x0001cea8) > # 7 0x0001eafb
in __mh_execute_header + 0x0001DAFB (Microsoft Database Daemon + 0x0001dafb)
# 8 0x000206ca in __mh_execute_header + 0x0001F6CA (Microsoft Database
Click to expand...
Daemon + 0x0001f6ca) > # 9 0x00015e8f in __mh_execute_header + 0x00014E8F
(Microsoft Database Daemon + 0x00014e8f) > # 10 0x00015f14 in __mh_execute_header
+ 0x00014F14 (Microsoft Database Daemon + 0x00014f14) > # 11 0x00016a64
in __mh_execute_header + 0x00015A64 (Microsoft Database Daemon + 0x00015a64)
# 12 0x00080346 in __mh_execute_header + 0x0007F346 (Microsoft Database
Click to expand...
Daemon + 0x0007f346) > # 13 0x00080487 in __mh_execute_header + 0x0007F487
(Microsoft Database Daemon + 0x0007f487) > # 14 0x000870b9 in __mh_execute_header
+ 0x000860B9 (Microsoft Database Daemon + 0x000860b9) > # 15 0x00087886
in __mh_execute_header + 0x00086886 (Microsoft Database Daemon + 0x00086886)
# 16 0x00054c1b in __mh_execute_header + 0x00053C1B (Microsoft Database
Click to expand...
Daemon + 0x00053c1b) > # 17 0x0005508f in __mh_execute_header + 0x0005408F
(Microsoft Database Daemon + 0x0005408f) > # 18 0x000033ee in __mh_execute_header
+ 0x000023EE (Microsoft Database Daemon + 0x000023ee) > # 19 0x00003315
in __mh_execute_header + 0x00002315 (Microsoft Database Daemon + 0x00002315)edx:0xbfffeac4 > �edi: 0xa02534f0 esi: 0x00000000 ebp: 0xbfffe9c8
esp:0xbfffe9a0 > � ss: 0x0000001f eip: 0x92b3415a cs: 0x00000017
ds:0x0000001f > � es: 0x0000001f fs: 0x00000000 gs: 0x00000037
eflags:0x00010283 > > Thread 1: > > # 1 0x93a9c5c6 in _signgam + 0x938FCD86
(libSystem.B.dylib + 0x000015c6) > # 2 0x93b2529b in _signgam + 0x93985A5B
(libSystem.B.dylib + 0x0008a29b) > # 3 0x007bdd7d in _MerpCreateSession
+ 0x00000B07 (merp + 0x00002d7d) > # 4 0x007bd3e5 in _MerpCreateSession
+ 0x0000016F (merp + 0x000023e5) > # 5 0x007bd46c in _MerpCreateSession
+ 0x000001F6 (merp + 0x0000246c) > # 6 0x007bdf25 in _MerpCreateSession
+ 0x00000CAF (merp + 0x00002f25) > # 7 0x93acd6f5 in _signgam + 0x9392DEB5
(libSystem.B.dylib + 0x000326f5) > # 8 0x93acd5b2 in _signgam + 0x9392DD72
(libSystem.B.dylib + 0x000325b2) > > X86 Thread State: > �eax:
0xffffffa6 ebx: 0x93b140bf ecx: 0xb00a0a5c edx:0x93a9c5c6 > �edi:
0x0000022f esi: 0xfc02a1ab ebp: 0xb00a0ac8 esp:0xb00a0a5c > � ss:
0x0000001f eip: 0x93a9c5c6 cs: 0x00000007 ds:0x0000001f > � es:
0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000202 > > Loaded
modules: > > 0: Microsoft Database Daemon (12.1.3.080930 Reg=en Loc=0x0409):
/Applications/Microsof





Run the Entourage database utility to make sure that your DB isn't corrupted.
On launching Entourage hold down the option key. Choose the Verify option.
If the database reports problems that is why the Daemon is giving you
these errors. If it reports problems you can try rebuild to repair the
database (Note: there is a known issue to Microsoft that rebuild can cause
problems which won't let you launch into your main identity - period).
If rebuild works the daemon errors should stop. Finally, you can turn
off the daemon check by going to the last option set prefs and untick
Perform Database Integrity.... suggest this though as it is trying to
Click to expand...
tell you that there's a problem with the Entourage DB.





The other thing I would encourage everyone to do is scream bloody murder
to Microsoft regarding all these issues we're dealing with in 08. They
don't seem to listen but I've always felt the squeaky wheel gets the oil
but it is Microsoft we're dealing with.




I ran the utility, and everything was ok, and database rebuild was required. Now the issue occurs when I turn on my macbook, and when ever I use any MS office program.
Very frustrating.
 
A

Allen A Watson

flydcjets said:
I ran the utility, and everything was ok, and database rebuild was
required. Now the issue occurs when I turn on my macbook, and when
ever I use any MS office program. Very frustrating.
Click to expand...

There must still be some kind of database problem. First, I'd suggest
getting into System Preferences, Accounts, and for the Login Items for
your user account, locate and delete any instances of the database
daemon. It normally is there only once; if more than once, that may be
your problem. If it is there only once, deleting it here may not fix
your problem but it won't hurt. The daemon will start and add itself
back when you launch Entourage next.

Try doing the rebuild a second time. If that comes up clean (no errors
found), it could be some undetectable corruption. That's been an issue
in the past, but as far as I know, all known instances of that have been
fixed.

If the problem still exists, launch Entourage and try switching to a new
identity: From the Entourage menu, select "Switch Identity", and create
a new identity. See if the daemon crashes while running a while in that
new identity. Since this new identity will be using a newly created,
separate database, there should be no corruption. If the crash occurs,
the problem is in the program, not the data. In that case, try using the
"Remove Office" application to remove your Office apps, and then
reinstall. This will not affect your data in any way.
 
F

flydcjets

flydcjets wrote:




I ran the utility, and everything was ok, and database rebuild was >
Click to expand...
required. Now the issue occurs when I turn on my macbook, and when > ever
I use any MS office program. Very frustrating.





There must still be some kind of database problem. First, I'd suggest
getting into System Preferences, Accounts, and for the Login Items for
your user account, locate and delete any instances of the database daemon.
It normally is there only once; if more than once, that may be your problem.
If it is there only once, deleting it here may not fix your problem but
it won't hurt. The daemon will start and add itself back when you launch
Entourage next.





Try doing the rebuild a second time. If that comes up clean (no errors
found), it could be some undetectable corruption. That's been an issue
in the past, but as far as I know, all known instances of that have been
fixed.





If the problem still exists, launch Entourage and try switching to a new
identity: From the Entourage menu, select "Switch Identity", and create
a new identity. See if the daemon crashes while running a while in that
new identity. Since this new identity will be using a newly created, separate
database, there should be no corruption. If the crash occurs, the problem
is in the program, not the data. In that case, try using the "Remove Office"
application to remove your Office apps, and then reinstall. This will
not affect your data in any way.




I accomplished the first paragraph by removing the database daemon through system preferences and rebuild the database. The same problem "Database Error" returned. I was unable to try the switch identities, due to the database daemon. In this case should I try removing and reinstalling Office Apps?
 
D

Diane Ross

flydcjets said:
I accomplished the first paragraph by removing the database daemon through
system preferences and rebuild the database.
Click to expand...

Just to be sure, exactly how did you remove the Microsoft Database daemon?
The same problem "Database Error"
returned.
Click to expand...

Was this the exact wording for the error?
I was unable to try the switch identities, due to the database
daemon.
Click to expand...

If you move the Office 2008 Identities folder to the desktop and let
Entourage create a new one, does it open with no problems? It should open in
a new Identity for testing.
In this case should I try removing and reinstalling Office Apps?
Click to expand...

No. Reinstalling doesn't fix problems like this.

Steps to help determine where the problem is located.

1) you can eliminate your Identity by creating a new Identity in Entourage
and see if you experience the same problem.

2) if a new Identity still exhibits the same issues, then create a new User
in System Preferences and test Entourage there.

A) test first in a new Identity
B) move your Main Identity in your regular User to Shared folder. Now in the
new User, drag from Shared your Main Identity to the Microsoft User Data
folder --> Office 2008 Identities folder. Does it open in the new User?

3) If the problems still exist in the new User, it's a problem with your
base OS files. If running the Apple combo does not fix, then you might need
to do an "Archive & Install".

<http://www.entourage.mvps.org/troubleshoot/combo.html>
 
F

flydcjets

I tried the download as suggested, and still have the same problem, only now the MS Database Daemon appears before even opening any MS Office 08 application.
 
D

Diane Ross

[email protected] said:
I tried the download as suggested, and still have the same problem, only now
the MS Database Daemon appears before even opening any MS Office 08
application.
Click to expand...

I offered several suggestion like moving your Identity to the desktop and I
asked you several questions. You have not responded to those yet.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Entourage won't startup any more 4
microsoft sync services--since downloadingupdate to Blackberry Desktop manager 1
Sync Servises Error 3
Entourage stopped syncing with iCal 5
Microsoft sync services has a problem and needs to close 7
Micro sync service 0
Entourage crashes after sync 5
Entourage crashes 0

Top