Hi there, I've been battling this issue for a while now. Exchange 2007 front end and back end server pair were built to replace the same Exchange 2003 servers. Everything was migrated across, and the 2003 servers just turned off (they still exist in the domain etc so can be turned on if necessary, and this issue happens whether they're on or off). Basically, every Outlook client of any flavour (2003/2007/2010) when connected gets a send/receive error 0x8004010F during every send/receive. All the clients are remote to the server (Outlook Anywhere) and none ever go LAN-local as the server's at a hosting site. I thought the issue was related to OAB generation and publishing, so i've recreated the OAB, recreated the virtual directories for delivery, and checked everything out I think I could, and still the error persists. I even had the same error message occur on a SBS2008 server at another client site which I fixed using the methods i'd tried on this one and it fixed that one, so I think my error might be a little more deep-seated. Interestingly, the sync failure notices i'd checked on my local client have got considerably less as a result of the work i've done to try and sort this, but still without sync notices I get the error. Does anyone therefore have the definitive list on things to try?

In your mixed version environment, the OAB isn't delivered to the clients via HTTP, so recreating the virtual directory will of been limited use. It uses the old method of public folders. Primary reason for this error message is that the OAB system folders in the public folder store do not have a replica added to them - if they exist. If you don't have a public folder store then that is your problem - you cannot support Outlook 2003 clients without one. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

I'm happy to remove the Exchange 2003 environment, and my Exchange 2007 servers do have a public folder structure (I even created a working PF calendar yesterday so I know it's ok). Would removing the Exchange 2003 servers go some way towards solving things? You seem to say that I can serve the OAB to clients by http(s) but hint that this might not work for Outlook 2003 clients? How do I support OAB distribution for Outlook 2003/2007/2010 clients with what I have? I'm happy not to have Exchange 2003 in the architecture now it's devoid of mailboxes. Thanks, Mike.

This doesn't really have anything to do with the Exchange 2003 servers, but you should go through the process to remove them. There are things that have to be done. However did you replicate the system folders from Exchange 2003 to Exchange 2007? That is often forgotten, because it isn't a visible item. Go through this article: http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx Make sure that you have done everything. The web based distribution method doesn't work for Outlook 2003 full stop. Therefore if you want to support the older version you must use public folder distribution. This can be in combination with or as an alternative to web based distribution for the newer clients. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

OK, i've now removed the Exchange 2003 environment entirely. What now? Cheers, Mike.

Are you still getting the same error? If so, you need to check a number of things. The error is cannot find. Thus: Ensure that you have a public folder store on the Exchange 2010 server. If you don't then you will have to add one. You must have a public folder store to support Outlook 2003 clients. Configure the OAB distribution to use either Public Folders only or a combination of public folders and web distribution. Ensure that you have OAB and some sub directories in the System Folders of the public folder store - use the Public Folder management console in the toolbox. Ensure that the sub folders have at least one replica listed on their properties. Check that there is a public folder store allocated to each mailbox database - it doesn't always assign one automatically when creating a new database. Finally, after doing all that, if you have had to make any changes, restart the information store service. SimonSimon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

On Thu, 3 Mar 2011 16:36:29 +0000, Pentangle Internet Limited wrote: >OK, i've now removed the Exchange 2003 environment entirely. You didn't remove the Administrative Group, did you? You still need the old AG in the organization as long as you have users that have that AG in thier legacyExchangeDN property values and make use of the system folders from that AG. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Thu, 3 Mar 2011 16:36:29 +0000, Pentangle Internet Limited wrote: >OK, i've now removed the Exchange 2003 environment entirely. You didn't remove the Administrative Group, did you? You still need the old AG in the organization as long as you have users that have that AG in thier legacyExchangeDN property values and make use of the system folders from that AG. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP Nope, not touched AD at all.

Are you still getting the same error? If so, you need to check a number of things. The error is cannot find. Thus: Ensure that you have a public folder store on the Exchange 2010 server. If you don't then you will have to add one. You must have a public folder store to support Outlook 2003 clients. Configure the OAB distribution to use either Public Folders only or a combination of public folders and web distribution. Ensure that you have OAB and some sub directories in the System Folders of the public folder store - use the Public Folder management console in the toolbox. Ensure that the sub folders have at least one replica listed on their properties. Check that there is a public folder store allocated to each mailbox database - it doesn't always assign one automatically when creating a new database. Finally, after doing all that, if you have had to make any changes, restart the information store service. Simon Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me. 1) Yes I have a PF store. This error still occurs on all flavours of Outlook though. 2) OAB distribution configured for both PF and web. 3) OFFLINE ADDRESS BOOK and subfolders exists in PF, and contains folders for OAB versions 2 3a and 4. 4) All OAB versions in the PF have a single replica (which is the original location) listed 5) The mailbox database has this public folder store allocated Both servers have been rebooted. Still no joy (and i'm not sure whether items 1-5 would have affected the error occurring on my Outlook 2010 anyway)