Entourage no longer connects to Exchange server

[Eric Barrett]

Hello,

I've run into a problem with Entourage we're it will no longer connect to my
work's exchange server. I don't get an error message unless I try and send
a message from Entourage. In that case, I get the following:

Quit and restart Entourage. If this problem continues you might need to
verify and rebuild the Entourage database.

I also get this message when I try and check the global address book. I
tried rebuilding the database as the message suggests, but no luck. I've
also tried emptying the folder's cache, uninstalling and reinstalling
Office, created a new user account on my Mac and got the same problem, and
even done an Archive and Install of OSX. Still get the same error. I'm
stumped and have pretty much exhausted all my resources here. Any other
ideas of what I can do? Thanks,

Eric

 

[Corentin Cras-Méneur]

Quit and restart Entourage. If this problem continues you might need to
verify and rebuild the Entourage database.

And did you try to rebuild?? (option key down while you launch
Entourage)
It does look like a database corruption,


Corentin

 

[Eric Barrett]

Yes, sorry if that wasn't clear in my last message, but I did try to rebuild
the database. No luck.

Eric

 

[Corentin Cras-Méneur]

Yes, sorry if that wasn't clear in my last message, but I did try to rebuild
the database. No luck.

It could be a corrupted preference. I've seen that in the past.
Try setting the Entourage preference file aside and relaunch the
application to see if it makes any difference. These files don't contain
much anyway. Most of the important settings are in the identity itself.
You wouldn't have much to re-set.

Corentin

 

[Pawan Kapoor]

Did you recently installed Safari 4?

 

[Eric Barrett]

I tried that with the Preference files in ~/Library/Preferences and no luck.
I wouldn't really expect it to since I tried with a new user on this machine
as well with the same issue. Are there any global preferences I should be
looking at? I didn't see anything in /Library/Preferences that looked like
they had anything to do with Entourage.

Eric

 

[Eric Barrett]

Nope, still on 3.1.2.

Eric

Did you recently installed Safari 4?

 

[Eric Barrett]

Just some more details. I am able to see the public folders. I'm obviously
connecting to my Exchange server, but not downloading my mail. I've tried
deleting a a suspect e-mail which I thought might cause problems, but that
didn't help. I'm also wondering if I quit Entourage while it was still
connecting the server and that may have caused issues. I've already tried
to repair the database and empty my cache, though, so I'm not sure if
there's anything else I could do if that was causing the problem.

Eric

 

[Pawan Kapoor]

Did you tried creating a new identity?

Nope, still on 3.1.2.

Eric

 

[Eric Barrett]

Yep, new identity as well as creating a new user on the Mac and still have
the same issue.

Eric

 

[Corentin Cras-Méneur]

Are there any global preferences I should be
looking at? I didn't see anything in /Library/Preferences that looked like
they had anything to do with Entourage.

Nope.
If you are still seeing it in a new user account, it could be either a
bug in Entourage or in the server :-\
I'm starting to believe there is somethign awfully wrong with the
server.
Can you ask the server admin whether everything is perfectly up to date
on the server??


Corentin

 

[Eric Barrett]

So after spending the better part of two days trying to figure out this
issue, it turns out we've been upgraded to an Exchange 2007 server. I had
to update the exchange server in my account settings. There's some
documentation on this already, but in case anyone stumbles upon this and has
the same issue, say your Exchange server had been set to 123.abc.com and
your e-mail address is (e-mail address removed), you'd need to change your exchange
server to "123.abc.com/exchange/[email protected]". Hopefully, that'll help
someone else who all of a sudden can't get any new mail.

Eric

 

[Corentin Cras-Méneur]

So after spending the better part of two days trying to figure out this
issue, it turns out we've been upgraded to an Exchange 2007 server.

[...]

I'm glad you figured out what was wrong Eric,

Corentin