Troubleshooting Error Code 0×8004010f

Written by Mike Rede on June 4, 2009

Many times when using Outlook you will encounter synchronization errors. Here’s another synchronization error to watch out for. The 0×8004010f error code is a generic reference for MAPI errors. You can see it for many problems related to using Outlook and it will often show up during rebuilds of the Offline Address List.

You can use the Microsoft Exchange Server Error Code lookup tool, “err.exe”, to view the error this way:

C:WXPsystem32>err 0×8004010f
# for hex 0×8004010f / decimal -2147221233
ecNotFound ec.h
ecAttachNotFound ec.h
ecUnknownRecip ec.h
ecPropNotExistent ec.h
MAPI_E_NOT_FOUND mapicode.h
# 5 matches found for “0×8004010f”

The sync log will show the Outlook error like this:

Synchronizing Mailbox <name>
Done
Microsoft Exchange offline address book
0×8004010f

Outlook clients can get the 0×8004010f error code for a variety of reasons. Most often this will occur when downloading or generating the offline address book. Some of these reasons are listed below.

Sometimes an administrator will attempt to download the offline address book in Microsoft Outlook or Exchange Server but the download fails or the list is not generated successfully in the case of an attempt to generate the list. The synchronization log will show events such as:

Synchronizing Mailbox <name>
Done
Microsoft Exchange offline address book
0X80004005

Synchronizing Mailbox <name>
Done
Microsoft Exchange offline address book
0×8004010f

When you try to generate an offline address list on the default Offline Address Lists folder in Exchange 2000 or 2003 Server, the list may not be generated successfully. The following events are logged in the application event log:

Event Type: Warning
Event Source: MSExchangeSA
Event Category: OAL Generator
Event ID: 9109
Date: <date>
Time: <time>
User: N/A
Computer: <server name>
Description:
OALGen encountered an error [0x8004010f]. This may be normal operation. Check other logged events to see if this is a serious error.
For more information, click http://search.support.microsoft.com/search/?adv=1.

Event Type: Warning
Event Source: MSExchangeSA
Event Category: OAL Generator
Event ID: 9116
Date: <date>
Time: <time>
User: N/A
Computer: <server name>
Description:
OALGen encountered an error while generating the changes.oab file for differential downloads. Clients will not be able to incrementally update to the new version of the OAL. This is normal if this is the first time this OAL has been generated. There is no previous version for clients to start with. Check other logged events to see if this is a serious error. (Global Address List) For more information, click http://search.support.microsoft.com/search/?adv=1.

You may also see the following events:
Event Type: Warning
Event Source: MSExchangeSA
Event Category: OAL Generator
Event ID: 9109
Date: <date>
Time: <time>
User: N/A
Computer: <server name>
Description:
OALGen encountered an error [0x80040107]. This may be normal operation. Check other logged events to see if this is a serious error.
For more information, click http://search.support.microsoft.com/search/?adv=1.

Event Type: Error
Event Source: MSExchangeSA
Event Category: OAL Generator
Event ID: 9127
Date: <date>
Time: <time>
User: N/A
Computer: <server name>
Description:
OALGen encountered error [0x80040107] while calculating the OALs.

These errors can occur under the following conditions:
• The OAB Version 2, OAB Version 3 or OAB Version 4 system folder is missing from the public folder store.
• The All Address Lists or All Global Address Lists containers contain sub-containers, instead of just address list objects. 
• The offline address list was deleted and then it was re-created with the same name.

When an offline address list is deleted, it stays in the system public folder for seven days. If a new offline address list with the same name is created in this seven-day period, a new public folder that is named OAB Version 2, OAB Version 3 or OAB Version 4 folder is created under the public folder that is associated with the deleted offline address list. A new public folder for the new offline address list is created. Because the OAB Version 2, OAB Version 3 or OAB Version 4 folder is already located in the deleted offline address list public folder, an updated OAB Version 2 folder is not created for the new offline address list public folder. When the client computer tries to locate the OAB Version 2 folder for the new offline address list, it cannot find it because the folder does not exist.

Here are some workarounds to correct these issues.

Workaround 1: Create a new offline address list with a different name.
1. Start Exchange System Manager.
2. Expand Recipients.
3. Right-click Offline Address Lists, click New, and then click Offline Address List.
4. Type the name that you want in the Offline Address List Name box, and then click Browse.
(The new offline address list name must be different from the originally deleted offline address list name.)
5. In the Select Exchange Server dialog box, click the appropriate server,
6. Click OK, and then click Next.
7. Under Address Lists, click the Default Global Address List , and then click Next two times.
8. Click Finish.

Workaround 2: Remove the container objects and leave only the address list objects. Container objects cannot be enumerated which causes the 0×8004010f error.

Workaround 3: If you delete an offline address list, you must wait greater than seven (7) days before you can create an offline address list with the same name.

Liked this post? Share it!
  • Digg
  • Slashdot
  • del.icio.us
  • StumbleUpon
  • Mixx
  • Fleck
  • Furl
  • Ma.gnolia
  • MisterWong
  • NewsVine
  • Reddit
  • Spurl
  • Technorati
  • TwitThis
Subscribe to my RSS feed

Leave a Comment

Comment Policy