• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2335
  • Last Modified:

Exchange 2003 error..OALGen encountered error 8004011b.Outlook hangs trying to retrieve data from the server

Problem Description
Users started experiencing problems with Exchange 2003 (SP2) that's sitting on SBS 2003.  All clients use outlook 2003 in cache mode. The problem occurs when users click on send & receive, outlook hangs and users get a warning message Outlook is trying to retrieve data from the server. Login from outlook web access is not a problem.

Event Logs
Checked exchange services and found that Event ID 9331, 9360, 1031 all logged on the servers application event log.

This errors referred to offline address book not being able update the changes hence clients were not being updated. We also noticed on the event logs Symantec mail security update failures.

1.
Time: 05:36:35 Source: MSExchangeSA EventID: 9331
OALGen encountered error 8004011b (internal ID 5020114) accessing the public folder store while generating the offline address list for address list '\Global Address List'.
- Default Offline Address List

2.
Time: 05:36:35 Source: MSExchangeSA EventID: 9360
OALGen encountered an error while generating the changes.oab file for version 2 and 3 differential downloads of address list '\Global Address List'. The offline address list has not been updated so clients will not be able to download the current set of changes. Check other logged events to find the cause of this error.
If the cause of the problem was intentional or cannot be resolved, OALGen can be forced to post a full offline address list by creating the DWORD registry key 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi ces\MSExchangeSA\Parameters\OAL post full if diff fails' and setting it to 1 on this server. When OALGen next generates the offline address list, clients will perform a full OAB download. After that time, the registry key should be removed to prevent further full downloads.
- Default Offline Address List

3. Time: 06:00:48 Source: MSExchangeSA EventID: 1031
One of the System Attendant's task is blocked.
Function: COffLineABGenTask::Work

Step taken to resolve the issue so far
"      Followed instructions on the event id MSExchangeSA EventID: 9360 on how to resolve the issue. This did not work.

"      Followed the solutions suggested by Microsoft article on the issue http://support.microsoft.com/kb/922255 . This still did not solve the problem.

"      Rebuild the global and recipient policies. Still did not solve the problem

Restarted the server, problem temporarily goes away but after a week or so its the same issue.


Ran exchange best practise analyser and got this warning message

The 'gateway Proxy' attribute for Recipient Update Service 'Recipient Update Service ' contains old data that was not fully processed. This data has existed since 2008-09-15T00:51:48Z and should be manually removed to avoid accidental changes to user addresses deleted this entry using adsiedit.msc utility form the active directory.

I have also just created a exception in my AV to exclude Exchange folders

Monitoring the issue for now. Has anyone gone thru this problem before? Any suggestion on what to do next would be appreciated.
0
TeamMaclean
Asked:
TeamMaclean
1 Solution
 
apache09Commented:
And if you turn off Cached Exhcange Mode, do these users still have the same problem?

Also, do all Office 2003 users have the latest SP installed:
Office 2003 SP3
http://www.microsoft.com/downloads/details.aspx?FamilyID=E25B7049-3E13-433B-B9D2-5E3C1132F206&displaylang=en

0
 
SurajCommented:
I feel you would have to concentrate on the issue reported in the ExBPA.

The 'gateway Proxy' attribute for Recipient Update Service 'Recipient Update Service ' contains old data that was not fully processed. This data has existed since 2008-09-15T00:51:48Z and should be manually removed to avoid accidental changes to user addresses deleted this entry using adsiedit.msc utility form the active directory.

Open Adsiedit.msc from a machine where you have the windows support tools been installed. Expand

CN=Configuration
CN=Services
CN=Microsoft Exchange
CN=<Exchange organization Name>
CN=Address Lists Container
CN=Recipient Update Service

Right click on CN=Recipient Update Service (Enterprise Configuration) and check for the gatewayproxy attribbute and if in case it does have any entries you would have to remove it.

Similarly check for CN=Recipeint Update Service (Domain Name) and check for the same attribute and clear the values.

Once this is done restart the MSExchangeSA service and you rebuild the OAB.

This should resolve the issue.

Thanks,
x-sam
0
 
TeamMacleanAuthor Commented:
hi there,

finally nailed it "I think"

thanks for the help. i did all that but the problem remained. yesterday I made some config changes and i did not get the errors and emails seem to be working fine.


Changes made were

1. Unchecked the option to force a rescan after live update of symantec mail security. you can find this option under SCAN advance setting.
reference http://bobchristian.blogspot.com/2005/02/symantec-mail-security-settings.html.

(very helpful in setting up a standard document for installtion of symantec mail secuirty in your enviroment.)

2. Excluded in Symantec Antivirus C:\Program Files\Symantec\SMSMSE\6.0\Server and all sub directories also excluded was exchange D:\Program Files\Exchsrvr and sub directories.

3. Removed message tracking from the server. " Read somewhere that this can aslo cause problem"

I hope this was it and I don't get this annoying errors again. I will monitor this for some time and lets see. I belive force scanning on information store was the culprit as in the blog it states clearly the issue's we can get. this option is there by default.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now