StevenMooreSmartsoft
asked on
GAL does not update in Cached Outlook Mode
We have Exchange 2007 after what we thought was a successful transition from Exchange 2003. Exchange 2003 is no longer in the Exchange Organisation. With Exchange 2007 our organisation uses Outlook 2007 Clients. We have a few users that we deleted after the transition and also a few users we added after the transition. These changes in the GAL or effectively the OAB appear to be O.K. server side but not on a client using Outlook 2007. Here is what I can and cannot do !
The recipients are NOT hidden from the Exchange Address Lists
The recipients DO show up in the "All Users" Address List
The recipients DO show up when Outlook 2007 is NOT in cached Mode
The recipients resolve correctly in Outlook Web Access
One of my Servers has Outlook, and the correct GAL is viewed from the Server.
I have adjusted the update schedule of the updates for the OAB from 05:00 once a day to 3 times a day.
I have updated the OAB using the command line on the EMS
I have subsequently downloaded the updated OAB on the Client side Outlook 2007 at Send/Receive Address Book.
It appears that the Server somehow has the correct GAL but it is not being reflected in the download to the Client Outlook 2007.
I have also checked that the default / primary SMTP addresses of the user matches that same name in the General Properties and in the Alias - and they do !
Does anyone have any answer to this issue - In Outlook cached mode - I have users in the GAL who have been deleted, that I do not want to see, and there are users who are newly added that I cannot see, but would be resolved if I type in their full email address !
All of these changes were made 3 days ago, so I don't think Exchange 2007 is miraculously going to sort something out for me.
Any suggestions greatly received.
Alistair
The recipients are NOT hidden from the Exchange Address Lists
The recipients DO show up in the "All Users" Address List
The recipients DO show up when Outlook 2007 is NOT in cached Mode
The recipients resolve correctly in Outlook Web Access
One of my Servers has Outlook, and the correct GAL is viewed from the Server.
I have adjusted the update schedule of the updates for the OAB from 05:00 once a day to 3 times a day.
I have updated the OAB using the command line on the EMS
I have subsequently downloaded the updated OAB on the Client side Outlook 2007 at Send/Receive Address Book.
It appears that the Server somehow has the correct GAL but it is not being reflected in the download to the Client Outlook 2007.
I have also checked that the default / primary SMTP addresses of the user matches that same name in the General Properties and in the Alias - and they do !
Does anyone have any answer to this issue - In Outlook cached mode - I have users in the GAL who have been deleted, that I do not want to see, and there are users who are newly added that I cannot see, but would be resolved if I type in their full email address !
All of these changes were made 3 days ago, so I don't think Exchange 2007 is miraculously going to sort something out for me.
Any suggestions greatly received.
Alistair
ASKER
Yes - I have updated / done a rebuild on the OAB
It can be done via the command line in the Exchange Management Shell or within the GUI of the Exchange Management Console in Exchange 2007.
It is like the Cached Mode Outlook 2007 clients are not downloading the rebuilt version of the OAB.
It can be done via the command line in the Exchange Management Shell or within the GUI of the Exchange Management Console in Exchange 2007.
It is like the Cached Mode Outlook 2007 clients are not downloading the rebuilt version of the OAB.
I think it's more likely that the rebuild isn't working properly, than the clients not downloading it... But either way it's a little out of my league unfortunately, I remember having this exact problem quite some time ago with 2003, and we had to pay a company we had a support agreement with to get their Exchange Guru to take a look... He sorted it in about an hour but whatever he did sounded very complicated when he explained it to me!
I'll be keeping an eye on this one to see if anyone solves it, but i'll be no use to you! Sorry!
I'll be keeping an eye on this one to see if anyone solves it, but i'll be no use to you! Sorry!
ASKER
Pete,
Thanks for your input so far.
Anyone else out there got an idea on a resolution for this ?
Alistair
Thanks for your input so far.
Anyone else out there got an idea on a resolution for this ?
Alistair
Is this happening for all Outlook clients?
ASKER
All clients on Outlook 2007 in Cached Mode
Even if you create a new profile for a user in Outlook?
ASKER
A new profile makes no diffrence to the issue ?
Any related events in Event viewer after running a rebuild of the OAB?
ASKER
After an update of the OAB I see this innthe Application Log
OALGen encountered error 80004005 (internal ID 50101ee) accessing the public folder store while generating the offline address list for address list '/'.
- Default Offline Address List
plus
OALGen encountered error 80004005 while cleaning the offline address list public folders under /o=SMARTSOFT/cn=addrlists/
- Default Offline Address List
Surely the OAB must be correct somewhere when the GAL is correct in Outlook for NON-CACHED Mode.
The issue is ONLY in Cached Mode Outlook ?
Any ideas ?
OALGen encountered error 80004005 (internal ID 50101ee) accessing the public folder store while generating the offline address list for address list '/'.
- Default Offline Address List
plus
OALGen encountered error 80004005 while cleaning the offline address list public folders under /o=SMARTSOFT/cn=addrlists/
- Default Offline Address List
Surely the OAB must be correct somewhere when the GAL is correct in Outlook for NON-CACHED Mode.
The issue is ONLY in Cached Mode Outlook ?
Any ideas ?
ASKER
This question is still open and we have had no new responses. The problem still persists.
Do we have any further suggestions toi rectify this issue ?
Do we have any further suggestions toi rectify this issue ?
Here is a copy and paste of the answer to a different question (but the same problem) -
"First thing to check with OAB errors is that there is a replica on the system folder.
See the second part of this article on my web site:
http://www.amset.info/exchange/oab-error.asp"
NOTE - this is not MY website, but a different members called Sembee (who happens to know a heck of a lot about Exchange), so check it out and see if it helps...
"First thing to check with OAB errors is that there is a replica on the system folder.
See the second part of this article on my web site:
http://www.amset.info/exchange/oab-error.asp"
NOTE - this is not MY website, but a different members called Sembee (who happens to know a heck of a lot about Exchange), so check it out and see if it helps...
P.S. It was the accepted solution to a problem where the OAL rebuild left the exact same errors in the event log that you are receiving... So it SHOULD work!
ASKER
Pete,
I will try your suggestions and get back to you.
Alistair
I will try your suggestions and get back to you.
Alistair
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
steve can u give bit more details how u did it ?
I'm afraid I have no experience with Exchange 2k7, just Exchange 2k3, but I had the same problem in 2k3 and forcing the OAB to 'rebuild' using System Manager solved the problem.
I'm guessing what you said means you've already done this, but just wanted to check exactly what you meant by 'updated'.
Thanks!
Pete