Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1003
  • Last Modified:

Exchange Error 8004010f

I've recently setup a EX2003 server in a native domain that has a mixed-mode Exchange environment. We are attempting to migrate from 5.5 to EX2003.

After a fewfailed installation attempts we deleted the Exchange Org and started from scratch. I am currently able to migrate a mailbox to the new server, connect Outlook to that mailbox, and send and receive mail ONLY TO MY GMAIL ACCOUNT. When I attempt to send/recieve to/from and internal account I receive the message "8004010f, The operation failed, an object could not be found".

I've read tons of posts on this error, but none of the fixes seem to work. Has anyone else experienced this and what would be a good place to start? I'm so close to being 100% on this server and I'd like to start migrating away from 5.5 ASAP.

Thanks- J
0
bigjrocksit
Asked:
bigjrocksit
  • 7
  • 4
1 Solution
 
MesthaCommented:
Without know what element is causing the error from the log in Outlook it is hard to know.
The most common cause of that error is the Offline Address Book public folder doesn't exist.

Simon.
0
 
bigjrocksitAuthor Commented:
I've attached the details of the event ID's in the case that anyone can pinpoint where this error may be.

Every "fix" for these errors seem to be either overly-complicated or does not resolve the issue.

I'm open to anything at this point, but I don't like the fact that I keep making changes to the system to resolve these issues and nothing works. I'm starting to worry that by the time I find the right fix it won't work because I've made so many changes to the system/AD.

Thanks again-
Event Type:	Error
Event Source:	MSExchangeSA
Event Category:	OAL Generator 
Event ID:	9126
Date:		6/29/2009
Time:		12:58:38 PM
User:		N/A
Computer:	ALLIED2003MAIL
Description:
OALGen encountered error 8004010e while calculating the offline address list for address list '\Global Address List'.  This offline address list will not be available for client download.  
- Default Offline Address List 
 
 
 
 
Event Type:	Error
Event Source:	MSExchangeSA
Event Category:	OAL Generator 
Event ID:	9330
Date:		6/29/2009
Time:		12:58:38 PM
User:		N/A
Computer:	ALLIED2003MAIL
Description:
OALGen encountered error 8004010e (internal ID 500139c) accessing Active Directory ALLIED for '\Global Address List'. 
- Default Offline Address List 
 
 
 
Event Type:	Error
Event Source:	MSExchangeSA
Event Category:	OAL Generator 
Event ID:	9338
Date:		6/29/2009
Time:		12:58:38 PM
User:		N/A
Computer:	ALLIED2003MAIL
Description:
Active Directory ALLIED returned error 8004010e while generating the offline address list for '\Global Address List'.  This offline address list will not be generated. 
- Default Offline Address List 

Open in new window

0
 
bigjrocksitAuthor Commented:
Here's the log from the Outlook client-
2009.06.30 08:06:24 <<<< Logging Started (level is LTF_TRACE) >>>>
2009.06.30 08:06:24 Microsoft Exchange Server: Synch operation started (flags = 00000001)
2009.06.30 08:06:24 Microsoft Exchange Server: UploadItems: 0 messages to send
2009.06.30 08:06:24 Microsoft Exchange Server: Synch operation completed
2009.06.30 08:10:17 Microsoft Exchange Server: Synch operation started (flags = 00000001)
2009.06.30 08:10:17 Microsoft Exchange Server: UploadItems: 0 messages to send
2009.06.30 08:10:17 Microsoft Exchange Server: Synch operation completed
2009.06.30 08:10:22 Microsoft Exchange Server: Synch operation started (flags = 00000001)
2009.06.30 08:10:22 Microsoft Exchange Server: UploadItems: 0 messages to send
2009.06.30 08:10:22 Microsoft Exchange Server: Synch operation completed
2009.06.30 08:11:26 Microsoft Exchange Server: Synch operation started (flags = 00000001)
2009.06.30 08:11:26 Microsoft Exchange Server: UploadItems: 0 messages to send
2009.06.30 08:11:26 Microsoft Exchange Server: Synch operation completed

Open in new window

0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
MesthaCommented:
Have you replicated the Offline Address Book from the Exchange 5.5 server to the Exchange 2003 server?
Wiping out the Exchange org may well have done damage to the original Exchange installation. Damage that cannot be repaired.

Simon.
0
 
bigjrocksitAuthor Commented:
What's the best way to do that?
I see that there are objects in the "Microsoft Exchagne System Objects" container, but I'm not sure if that's what you're talking about.

thanks for your help, I'm going insane......
0
 
MesthaCommented:
The Offline Address is a system public folder. This KB article goes through the full process for removing Exchange 5.5 from an Exchange 2003 based system, which is what you need to be following.
http://support.microsoft.com/default.aspx?kbid=822450

Simon.
0
 
bigjrocksitAuthor Commented:
Thanks Simon- you've been a great help.

Going through the steps I noticed that the OAB was NOT replicating with the new 2003 server. I added the new server to the replication settings for all the folders it suggested.

My next question is how long should I wait/what steps should I take to test that the address book replication is working? I rebooted the server for good measure and tried to "rebuild" the OAB and I still received the errors listed above in Event Viewer.
0
 
MesthaCommented:
Replication of public and system folders off any version previous to Exchange 2003 SP1 can take days - I am not kidding. It also cannot be made to go any faster. When I am migrating off Exchange 5.5/2000 I get the machine up as quickly as possible so I can set the replication going, I usually do a migration over a week or more because of the migration delays.

Basically replication on those products is very conservative because they are from an era when 10baseT was new, and LAN bandwidth was limited.

Simon.
0
 
bigjrocksitAuthor Commented:
Thanks- I could use a day off from this.

I also just retrieved a copy of nspitool from a contact at Microsoft to help me check for mangled settings in Active Directory. I have read that if there are any null/invalid settings the OAB will not generate and will also cause the errors I'm seeing.

I'll update you on what I find while using this tool. Also, if you'd like a copy of this tool I can forward it on to you, I don't think it's available out there any longer.
0
 
bigjrocksitAuthor Commented:
OK- the server is 100% now.

Here's what was broken:
The new server did not have correct permissions to the container in AD that housed the OAB. Once we gave full permissions to the server account to this container everything started working.

We are able to send/receive internal/external mail and all of the errors have vanished from Event Viewer. I have already started migrating mailboxes and all looks well.

Thanks for your help Sir-
0
 
bigjrocksitAuthor Commented:
This document is really important if you're going to go through this migration. The thing that got us was the security settings for the OAB AD container. Thanks again Sir-
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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