'Could not open that feature' error

I could really use some help. I have recently switched over to OS X =
Server=20
10.3, and all my workstations to Panther as well. I tell this because I =
believe=20
it has bearing. I also set up a directory domain which handles =
authentication=20
for the workstations, and the server maintains the home directories as =
well.=20

If I log into locally to a machine and create an account, the account =
works=20
fine. However, if I log into an account that resides on the server and =
create a=20
new Exchange account in Entourage 2004, all seems okay until I close =
the=20
software and reopen it. As soon as I do I get the message 'Could not =
open=20
that feature,' and Entourage quits. Repeated attempts generally give the =

same error, and occasionally I get a bad database error, which a rebuild =
has=20
no affect on.=20

I thought it was an authentication error at first, but I do not believe =
it is even=20
getting that far. Now I think perhaps a permissions problem with where =
the=20
files are, or that Entourage is having problems locating the folder =
where the=20
database resides. However, I do have one account that is set up this =
way=20
that is working. The first 2 times I set it up, it had the problem =
described=20
above, but the third time the machine seized, and after I rebooted it =
worked=20
fine. The setups are identical between the two accounts.

I could go on and on, but I will stop here. Does anyone know of a known=20
issue with doing things this way or have any ideas?

Thanks.

dre
Thu Oct 07 17:29:29 CDT 2004

I am also having basically the same issue...local account with Entourage
works fine, I log out and log into my network account which resides on OS X
Server and I get "error unknown feature (16008)". I also have fussed with
permissions and rebuilt the database, etc. The version I am using is Office
2004 standard, all the other office apps work with no problems using the
network account.

Anyone know what this error is related too? Any help very appreciated!

Thanks,

:tech

On 10/4/04 2:22 PM, in article 178801c4aa58$412e64e0$3501280a@phx.gbl, "Ken
Davis" <kdavis@ren-mark.com> wrote:

> I could really use some help. I have recently switched over to OS X Server
> 10.3, and all my workstations to Panther as well. I tell this because I
> believe
> it has bearing. I also set up a directory domain which handles authentication
> for the workstations, and the server maintains the home directories as well.
>
> If I log into locally to a machine and create an account, the account works
> fine. However, if I log into an account that resides on the server and create
> a
> new Exchange account in Entourage 2004, all seems okay until I close the
> software and reopen it. As soon as I do I get the message 'Could not open
> that feature,' and Entourage quits. Repeated attempts generally give the
> same error, and occasionally I get a bad database error, which a rebuild has
> no affect on.
>
> I thought it was an authentication error at first, but I do not believe it is
> even
> getting that far. Now I think perhaps a permissions problem with where the
> files are, or that Entourage is having problems locating the folder where the
> database resides. However, I do have one account that is set up this way
> that is working. The first 2 times I set it up, it had the problem described
> above, but the third time the machine seized, and after I rebooted it worked
> fine. The setups are identical between the two accounts.
>
> I could go on and on, but I will stop here. Does anyone know of a known
> issue with doing things this way or have any ideas?
>
> Thanks.

Diane
Fri Oct 08 17:34:23 CDT 2004

I don't use Exchange so I can't offer any advice, but check the Exchange
Support Page for help. Be sure to download the PDF: Microsoft Office 2004
for Mac: Working with Exchange Server

<http://www.entourage.mvps.org/exchange/index.html>

--
Diane Ross
Mac MVP
Entourage Help Page <http://www.entourage.mvps.org/>



> From: dre <dre@cnemedia.com>
> Newsgroups: microsoft.public.mac.office.entourage
> Date: Thu, 07 Oct 2004 15:29:29 -0700
> Subject: Re: 'Could not open that feature' error
>
> I am also having basically the same issue...local account with Entourage
> works fine, I log out and log into my network account which resides on OS X
> Server and I get "error unknown feature (16008)". I also have fussed with
> permissions and rebuilt the database, etc. The version I am using is Office
> 2004 standard, all the other office apps work with no problems using the
> network account.
>
> Anyone know what this error is related too? Any help very appreciated!
>
> Thanks,
>
> :tech
>
> On 10/4/04 2:22 PM, in article 178801c4aa58$412e64e0$3501280a@phx.gbl, "Ken
> Davis" <kdavis@ren-mark.com> wrote:
>
>> I could really use some help. I have recently switched over to OS X Server
>> 10.3, and all my workstations to Panther as well. I tell this because I
>> believe
>> it has bearing. I also set up a directory domain which handles authentication
>> for the workstations, and the server maintains the home directories as well.
>>
>> If I log into locally to a machine and create an account, the account works
>> fine. However, if I log into an account that resides on the server and create
>> a
>> new Exchange account in Entourage 2004, all seems okay until I close the
>> software and reopen it. As soon as I do I get the message 'Could not open
>> that feature,' and Entourage quits. Repeated attempts generally give the
>> same error, and occasionally I get a bad database error, which a rebuild has
>> no affect on.
>>
>> I thought it was an authentication error at first, but I do not believe it is
>> even
>> getting that far. Now I think perhaps a permissions problem with where the
>> files are, or that Entourage is having problems locating the folder where the
>> database resides. However, I do have one account that is set up this way
>> that is working. The first 2 times I set it up, it had the problem described
>> above, but the third time the machine seized, and after I rebooted it worked
>> fine. The setups are identical between the two accounts.
>>
>> I could go on and on, but I will stop here. Does anyone know of a known
>> issue with doing things this way or have any ideas?
>>
>> Thanks.
>
>