Entourage 2004 with Mac OS X 10.3.3 Network User Account

[Marc Mintz]

When our users log in using a network account, they can open Entourage
2004 (located on the local Mac), but when it attempts to open their
Server/Volumes/DataVolume/Users/~/Documents/Microsoft User Data/2004
Identities/Main Identity/ mail, Entourage gives an error stating the
mail database is corrupted, and to rebuild it. Rebuilding shows no
problem. Opening the same account locally opens mail with no problem.

Is entourage 2004 incompatible with Network user accounts?

marc
(e-mail address removed)

 

[Barry Wainwright]

When our users log in using a network account, they can open Entourage
2004 (located on the local Mac), but when it attempts to open their
Server/Volumes/DataVolume/Users/~/Documents/Microsoft User Data/2004
Identities/Main Identity/ mail, Entourage gives an error stating the
mail database is corrupted, and to rebuild it. Rebuilding shows no
problem. Opening the same account locally opens mail with no problem.

Is entourage 2004 incompatible with Network user accounts?

marc
(e-mail address removed)

No, it isn't but what is probably happening is that when the user
disconnects from the network the database daemon is still running and hasn't
written it's buffers out to the database (the daemon is the little
application that does all the database access and keeps track of items that
need to pass an alarm/alert to the user, even when office apps are not
running). This will cause the corruption warning you are seeing.

The fix is to quit all office apps before disconnecting the network and then
to do one of the following:

1. run this applescript to quit the daemon:

tell application "Microsoft Database Daemon" to quit

You can save this one line script as an application and run it by
double-clicking, or as a compiled script and save it in the system scripts
folder (~/Library/Scripts/) - if scriptMenu is installed then the script can
be selected from the menubar at any time.

2. Open up 'Activity Monitor (from /Applications/Utilities/), if the list
of processes is not visible, select 'Show Activity Monitor' from the Monitor
menu. Find the entry for 'Database Daemon', and double-click it. Then click
on the 'quit' button

Either method will cause the daemon to gracefully exit, writing it's file
buffers out to the network disk before doing so. After this, your users
should not see any more corruption notices.