Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Address book will not update for 03/07 clients

Status
Not open for further replies.

ryrae

MIS
Aug 31, 2004
89
US
We recently upgraded from Exchange 2003 to 2007 without any major issues. Within the past couple weeks we have noticed that the address book will not update for 03 or 07 Outlook clients. We have attempted to force an update from the server side and force a download from the client, but have been unsuccessful. The last update time for any of the .lzx files in the Exchange OAB directory is Nov 25th. Nothing has been modifed so we are not sure where is issue could have started. The ExchangeOAB directory is shared out and has the default share/NTFS permissions. Any help is appreciated. Thanks

A+, Network+, MCP
 
I have posted this from the eventviewer on the CAS/HUB server......

Process MSExchangeFDS.exe (PID=5344). Could not find directory \\ExchangeCluster\ExchangeOAB\36de1d00-fdb3-4651-9a88-df774617a92a. This is normal if the directory has never been generated. Otherwise, make sure this directory and share has read permission for the "Exchange Servers" group.
 
Interesting. You're not actually trying to run the CAS role on a cluster, are you?

Have you verified the permissions on the share mentioned?

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Yes, we have two Exchange 07 boxes along with two CAS/HUBs in a CCR role. The two Exchange boxes are clustered with a heartbeat monitor between the two. I have noticed that the share is present on mailserver1, but not on mailserver2. When you try the UNC of the cluster...\\mailcluster it does not display the share. It seems as if the two servers are not replicating data between each other....
 
CAS/HUB are not supported in CCR. HT is naturally load balancing, and you can use Windows load balancing for the CAS role.

You need to move those roles off the cluster.

See where it says
You cannot install the Hub Transport server role on a server that is configured as part of a cluster.

Same applies to the CAS role.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
We had a major power outage and when we shutdown the servers the failover for the exchange servers worked, but they did not failback. So the cluster was looking to mailbox2 rather than mailbox1 for everything and for some reason the addressbook share was not replicated over to mailbox2 it was only on mailbox1 so when it tried to push out the addressbook it couldn't find the share on the server and failed. We restarted mailbox2 so it failed back to mailbox1 and everything worked again. We are still looking into the reason why that shared directory was not replicated over to the second exchange server in the cluster.
 
Because you're not supposed to run it on a cluster. Not supported. Not recommended. Ain't going to work right.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
I beleive that it is supported....we have a CCR(cluster continuous replication) setup. Two exchange mailbox servers(One active/one passive) setup in a cluster, along with Two Hub transport servers(file share witness). This setup is supported and recommended as our setup mimics the high availability architechture found on Microsoft's Technet documentation.
 
Please provide a link, as the only thing supported in a cluster is the mailbox role. Hub transport has load balancing inside, and CAS requires external load balancing via either software or hardware.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Yes, the mailbox servers are clustered(mailbox1/mailbox2=mailboxcluster). Our two HUB transport servers are load balancing. the problem we had was mailbox1 was shutdown so it failed over to mailbox2, which didn't have the addressbook share. I was under the impression that if they are setup in a cluster that everything would be replicated from the active(mailbox1) to the passive(mailbox2). Sorry I don't have a link to the exact environment, but what I have is from Technet and it is the Microsoft Exchange Server 2007 Coponent Architecture map.
 
Ok - my bad. I was thinking you were having problems with the distribution (done by the CAS servers), not the actual generation of it. I apologize.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top