Entourage 2008 appears to connect to Exchange2007 but no folder or mail

[holmess001]

I'm totally stumped. Entourage 2008 was working great, then we had an Exchange 2007 server problem where I had to recreate the Exchange IIS virtual directories. Since, then Entourage appears to connect but my folders and email are all gone. Here's some detail:

1. OWA works fine; Outlook clients connect fine; even Apple Mail connects to Exchange fine.
2. The reason I think Entourage is connecting is that if I intentionally put in an incorrect password in my account setup, I get the usual error message.
3. I've tried creating a new Mac OS X user and configuring a whole new identity, but same result.
4. I've tried creating an account for another user on the server (to see if maybe there is a problem with my mailbox), but same result -- no folders or mail.
5. I've tried creating an account for a user on our other Exchange server (this one 2003) and that works fine.
6. I'm configuring the Entourage account manually using "servername/exchange/[email protected]". Again, I don't get any errors. After I click OK the new account blinks "Not connected" a few times, but then settles down in what appears to be a connected state.

Any help would be appreciated. Thanks. -steve

 

[holmess001]

To add to the above, I've now tried uninstalling Office 2008 and installing Entourage 2004. No luck. This time I could see my old exchange folders, but I'm pretty sure this was just a cached copy. The data was from the time I upgraded to Office 2008. The folders did not update, but as with 2008, no error messages.

 

[Z]

I'm totally stumped. Entourage 2008 was working great, then we had an Exchange 2007 server problem where I had to recreate the Exchange IIS virtual directories. Since, then Entourage appears to connect but my folders and emailare all gone. Here's some detail:

1. OWA works fine; Outlook clients connect fine; even Apple Mail connects to Exchange fine.
2. The reason I think Entourage is connecting is that if I intentionally put in an incorrect password in my account setup, I get the usual error message.
3. I've tried creating a new Mac OS X user and configuring a whole new identity, but same result.
4. I've tried creating an account for another user on the server (to see if maybe there is a problem with my mailbox), but same result -- no folders or mail.
5. I've tried creating an account for a user on our other Exchange server (this one 2003) and that works fine.
6. I'm configuring the Entourage account manually using "servername/exchange/[email protected]". Again, I don't get any errors. After I click OK the new account blinks "Not connected" a few times, but then settles down inwhat appears to be a connected state.

Any help would be appreciated. Thanks. -steve

I'm having the same problem... if you can get to solve this, please
answer to this group.

Thanks,
Zaiden

 

[Barry Wainwright]

I'm having the same problem... if you can get to solve this, please
answer to this group.

Thanks,
Zaiden

what happens if you create a new exchange account in entourage - does that
connect to the server OK?

(Entourage, unlike Outlook, can have more than one exchange account
configured, and you can create a second account accessing the same exchange
account as well - useful for testing).

 

[Stephen Holmes]

Hi Barry,

Other accounts added to Entourage exhibit the same behavior. They seem to
connect in that I don't get an error message if I enter the correct password
but do get an error message when I enter the incorrect one. However, no mail
or folders ever populate.

 

[Matthias Utrata]

Hi,
I am experiencing the same problem.
Unfortunately only when connecting from outside the LAN.
The reason as far as we have investigated is that even Entourage 2008 does
not support RPC over HTTP.
This is more than poor for Microsoft - to have incompatible products on the
market....
Best regards,
Matthias

 

[Stephen Holmes]

Hi Matthias,

I think our problems may be a little different. I'm connecting to my LAN,
and my account is set to access my backend server, though I've tried
connecting to the front end server, through the firewall from outside the
LAN -- pretty much every combination I can think of, but no help.

 

[Stephen Holmes]

Problem solved by installing Rollout 1 to Exchange 2007 SP1 on the server.
Don't know how or why, but as soon as I finished the install, mail began to
magically appear. Didn't even need to restart Entourage.

 

[josef.adams]

So we seemed to be having the same problem. Entourage would go to
connect to the CAS server on the external network, but would just
drop. What we found out after doing a support call with MS, was that
SSL needed to be unchecked on the Virtual Directories on the MB
servers. On the CAS they were fine, but the when the CAS goes to get
the users mailbox, it just bombs out. So we unchecked the Require SSL
on the virtual directories on our MB servers, and reconnected
entourage on the outside, and BAM!!! Mail starts showing up, as well
as public folders....

 

[josef.adams]

So we seemed to be having the same problem. Entourage would go to
connect to the CAS server on the external network, but would just
drop. What we found out after doing a support call with MS, was that
SSL needed to be unchecked on the Virtual Directories on the MB
servers. On the CAS they were fine, but the when the CAS goes to get
the users mailbox, it just bombs out. So we unchecked the Require SSL
on the virtual directories on our MB servers, and reconnected
entourage on the outside, and BAM!!! Mail starts showing up, as well
as public folders....

Oh, and by the way, after installing the Rollout 1 to SP 1, it still
didnt work.

 

[josef.adams]

Oh, and by the way, after installing the Rollout 1 to SP 1, it still
didnt work.

 

[retwmt]

So we seemed to be having the same problem. Entourage would go to
connect to the CAS server on the external network, but would just
drop. What we found out after doing a support call with MS, was that
SSL needed to be unchecked on the Virtual Directories on the MB
servers. On the CAS they were fine, but the when the CAS goes to get
the users mailbox, it just bombs out. So we unchecked the Require SSL
on the virtual directories on our MB servers, and reconnected
entourage on the outside, and BAM!!! Mail starts showing up, as well
as public folders....

I am also having the same issue, however I am pretty new to Exchange.
I would like to try to unchecked the SLL on Virtual Directories,
however I am not sure where I do this in exchange can you elaborate?
Thanks

 

[retwmt]

So we seemed to be having the same problem. Entourage would go to
connect to the CAS server on the external network, but would just
drop. What we found out after doing a support call with MS, was that
SSL needed to be unchecked on the Virtual Directories on the MB
servers. On the CAS they were fine, but the when the CAS goes to get
the users mailbox, it just bombs out. So we unchecked the Require SSL
on the virtual directories on our MB servers, and reconnected
entourage on the outside, and BAM!!! Mail starts showing up, as well
as public folders....

I am also having the same issue, however I am pretty new to Exchange.
I would like to try to unchecked the SLL on Virtual Directories,
however I am not sure where I do this in exchange can you elaborate?
Thanks

 

[Stephen Holmes]

Start | Administrative Tools | Internet Information Server (IIS) Manager.
Then in IIS, go to Web Sites | Default Web Site. In there you will see a
number of items. The ones you need to care about are Exchange, Public,
Exchweb, and owa. You will do exactly the same thing for all four. That is--

1. Right click on the item;
2. Go to the ³Directory Security² tab
3. Go to ³Edit² in the Secure Communications section
4. Uncheck the ³Require Secure Channel (SSL)² checkbox.

Repeat for the other 3 items.

For what it¹s worth, these items are unchecked on my Exchange server too.
However, SSL still works; it just isn¹t required. I have my firewall server
set to require SSL for OWA connections from the Internet, so I¹m still
pretty comfortable about security.

Finally, when I was having this same problem a few weeks ago, it was
magically fixed by installing a new patch to the Exchange Server, which for
reasons I never understood, did not show up in the usual Microsoft Updates.
It¹s Rollup 1 to Exchange 2007 SP1. I installed that and mail started
flowing immediately.