Error 16008 & network home folders ("roaming" profiles)

[Pete Curtner]

New install of Entourage 2004 connecting to an existing Exchange server,
upgraded from Outlook in Classic. Was able to successfully copy all
personal folders back up to the server, but since finishing that move,
Entourage flashes an "Error 16008" dialog a few times, the crashes.

All forms of the database rebuild complete successfully without discovering
or repairing any errors. Repairing disk permissions on the startup volume
using Disk Utility doesn't turn up anything. Logging into that user's homw
account from another machine with a completely brand-spankin-new copy
of office 2004 reproduces the crashes.

Several other sites (MiT, MacNN, VT, etc) have mentioned this problem,
some users have reported success launching Word 2004 and/or the
Microsoft Database Daemon (in /M$ Office 2004/Office/) before launching
Entourage, but in this user's case it continues to crash. The solution to the
Office v.X version of this problem, copying the Carbon Registration file
created by a local account over to the network user's library, doesn't work as
Office 2004 doesn't use that file anymore.

Considering how many networked-home users we have, if this doesn't get
resolved quickly we're going to have big problems.

-p

 

[Jeremy Egger]

We are having the same problem. Networked home directories are not
working. We have 9 sites that are tied via ldap and using a managed
client environment. Nothing I have tried seems to work. Any
suggestions that people may have would greatly be appreciated.

Thanks.

 

[suzie]

We are having the same problem. Networked home directories are not

working. We have 9 sites that are tied via ldap and using a managed

client environment. Nothing I have tried seems to work. Any
suggestions that people may have would greatly be appreciated.

Thanks.

I am having the same issue. I work at a school and all our users
(well almost all) use networked home directories. We used Entourage X
last year and it worked well. I have contacted Microsoft about this
error and I was told that Microsoft does not support Entourage in this
environment. This is a reported bug (bug #91983), but they are not
working to fix it. I have spent hours on the phone trying to solve
this with them. I told my representative that the statment " we
don’t support this issue" is a cop-out response. They just simply
have chosen not to address this issue which is obviously a problem for
many users. (but then again we are Mac users). I have 115 licence of
Office 2004 and I’m ticked off about this. If Mircrosoft does not
support their products in a networked environment then it should be
stated so on the box or in the documentation that comes with the
product. Everyone with this issue should call Microsoft and complain,
then maybe they will at least try to resolve this issue.
My case # has not been closed yet, I will post any helpful information
I receive , but since I have heard over and over again that "this is
not something that is supported by Microsoft" I’m not going to hold
my breath. I intend to start using Apple Mail for my networked
users, I know this will work!

 

[Tezz_M]

I am having the same issue. I work at a school and all our
users (well almost all) use networked home directories. We
used Entourage X last year and it worked well. I have
contacted Microsoft about this error and I was told that
Microsoft does not support Entourage in this environment. This
is a reported bug (bug #91983), but they are not working to
fix it. I have spent hours on the phone trying to solve this
with them. I told my representative that the statment " we
don’t support this issue" is a cop-out response. They just
simply have chosen not to address this issue which is
obviously a problem for many users. (but then again we are Mac
users). I have 115 licence of Office 2004 and I’m ticked off
about this. If Mircrosoft does not support their products in
a networked environment then it should be stated so on the box
or in the documentation that comes with the product. Everyone
with this issue should call Microsoft and complain, then maybe
they will at least try to resolve this issue.
My case # has not been closed yet, I will post any helpful
information I receive , but since I have heard over and over
again that "this is not something that is supported by
Microsoft" I’m not going to hold my breath. I intend to
start using Apple Mail for my networked users, I know this
will work!

Hello

I am no mac whiz so I’m not sure whether anything I’m about to write
is actually useful to anyone, but thought I would share the experience
in case it is.

All of a sudden one afternoon a couple of weeks ago I started getting
the mail error 16008 on my home Entourage program (it had worked fine
in the morning). All copies at the officed were working well on all
machines at but my home version just decided to die on me.

So what I did was made a folder on the desktop and dragged all my
account in-boxes and sent mail and saved emails into it, literally
just dragged them over which made them .mbox files in that folder.

Then I dragged the ’database’ file from the main identities in the
Office X identities folder in my user documents folder, I also
exported a copy of my address book. You might have to quit and
re-start Entoruage a couple of times because it quite often doesn’t
like doing any of this when it’s in its foul ’16008’ mood, but
eventually I got it all copied out.

Then I restarted the mac and Entourage and it gave me the basic set up
screen again which I ignored but noticed that it was recieving and
sending emails just fine when I set up one of my email addresses.

So, I started copying everything back in except the old database. You
can either import this stuff or just copy it in, both work. It hasn’t
let me down again yet. I’ve kept the old database file just in case I
ever need anything off it - it’s over 2GB!

Like I said, don’t know if this helps anyone, but when I started
having the problem I looked up this website and a couple of little
hints helped me get back on track and working properly from home
again. I had resorted to using Netscape - that’s how desperate I was -
but thank god my fiddling with the database worked! Good luck!