Can't Establish a Delegate

[turnermarketing]

We just upgraded to SP2 and basically it is running great with the
exception of a couple of minor glitches. Applying upgrades to the
Exchange server fixed all of them but one. I can't designate someone as
a delegate. Once I select a person as a delegate and click ok, I get
this error message:

Entourage cannot connect to the Exchange server.
Make sure that your password was entered correctly and try again.
(Error: 65486)

The fact is, I know I am connected and my password is entered correctly
because I can do everything else in Entourage. I can also give someone
access to my calendar or e-mail by setting the permissions in the
folder properties.

This happens on any computer on our network, so it is either a setting
on our Exchange server or an overall glitch in SP2.

Does anyone know how to fix this?

 

[Doug Metz]

IIRC, you must establish the delegate in Outlook first. Once established,
you may modify your delegate on the Mac.

Doug

 

[turnermarketing]

you may be correct and I'll give it a try, but the documentation
clearly states that since SP2 this can be done from within Entourage.

That is very frustrating

 

[Andy Ruff]

Confirm that you have Entourage set to the backend server... If you are
connected to the frontend server, you may need to press the Advanced button
in the Delegates tab and enter your backend server in the Delegation server
field.

-Andy

 

[rliebsch]

Verified. This doesn't work "out of the box."

Additionally, even on those users/groups who were configured to hav
permissions in Outlook cannot be changed in Entourage. I als
redirected to different "delegation" servers to no avail

 

[rliebsch]

rescinded. From my assistant's computer it works. I am going to run dow
the preferences one by one. More details soon

 

[David S. Mohler]

Speaking for turnermarketing, there is only one server. There is no frontend
and backend server. Only one Exchange server on an SBS2003 server.

 

[turnermarketing]

So David, we really don't know anything new, right?

 

[rliebsch]

So far I have isolated this problem to only one computer. The setting
all match the working computers. I thought initially, this was a Tige
issue, but my other Tiger machine works without fail. I randomly teste
this feature on 15 other computers about the office. All work a
expected.

I'll try to reinstall SP2 and see how it goes..

 

[wkarraker]

There is another part to this upgrade, a patch that came out for th
Exchange server itself. Have you applied the patch yet to the server?

I am having the same problem and I know for a fact that our server ha
not been upgraded

 

[Boettcher, Scott]

Can you post the name of the update for the EXCH server please?
I think that may be my issue too.

Thanks,
SB

 

[Bill Bryson]

http://www.microsoft.com/mac/default.aspx?pid=exupsp2

 

[Nathan Herring [MSFT]]

Links to said updates are here:

<http://www.microsoft.com/mac/default.aspx?pid=exupsp2>

-nh

 

[Boettcher, Scott]

Thanks!
SB

http://www.microsoft.com/mac/default.aspx?pid=exupsp2

 

[turnermarketing]

We have applied every patch to the actual exchange server and still
cannot establish delegates.

 

[turnermarketing]

We have applied every patch to the actual exchange server and still
cannot establish delegates.

 

[Andy Ruff]

Are you able to establish delegates on any machines for any users or does it
outright fail for all machines and all users?

-Andy

 

[wkarraker]

After trying a lot of different methods I was able to fix the error. I
may have been a combination of things but this is the order I trie
that resulted in an operational Delegates function.

1. Delete the "Microsoft Database Daemon" from Sys Pref>Accounts>Logi
Items
2. Restart the computer
3. Open Entourage
4. Enter the name of the Exchange domain ("EXCHANGE04" instead of th
web address of the server for example) in the Delegates window Advance
Settings.

I have tried this on two systems that were having problems and, so far
have had success. We still have not applied the patch to the server bu
plan on doing that soon so that does not appear to affect this problem

 

[maverick]

After trying a lot of different methods I was able to fix the error. It
may have been a combination of things but this is the order I tried
that resulted in an operational Delegates function.

1. Delete the "Microsoft Database Daemon" from Sys Pref>Accounts>Login
Items
2. Restart the computer
3. Open Entourage
4. Enter the name of the Exchange domain ("EXCHANGE04" instead of the
web address of the server for example) in the Delegates window Advanced
Settings.

I have tried this on two systems that were having problems and, so far,
have had success. We still have not applied the patch to the server but
plan on doing that soon so that does not appear to affect this problem.


--
wkarraker

-Exotic Technologies Administrator-
-GMR Marketing LLC-

 

[maverick]

After trying a lot of different methods I was able to fix the error. It
may have been a combination of things but this is the order I tried
that resulted in an operational Delegates function.

1. Delete the "Microsoft Database Daemon" from Sys Pref>Accounts>Login
Items
2. Restart the computer
3. Open Entourage
4. Enter the name of the Exchange domain ("EXCHANGE04" instead of the
web address of the server for example) in the Delegates window Advanced
Settings.

I have tried this on two systems that were having problems and, so far,
have had success. We still have not applied the patch to the server but
plan on doing that soon so that does not appear to affect this problem.


--
wkarraker

-Exotic Technologies Administrator-
-GMR Marketing LLC-