Exchange 2007 – 2010 Upgrade and EventID 1020

During a recent migration from Exchange Server 2007 to Exchange Server 2010 SP3 I ran into some pretty interesting issues. In particular, public folder hierarchy was replicating, but not public folder content. The reason in this instance was two-fold, but both stemmed from the same source.

Scenario 1

Symptoms

  • The public folder hierarchy replicates from your Exchange 2007 server to your Exchange 2010 server, but not the public folder contents.

Given Assumptions

  • Both Exchange 2007 and Exchange 2010 are coexisting in the same Exchange Organization.
  • Replication partners for public folders have been set in the Public Folder Management area of the Exchange Management Console
  • Running the Exchange Powershell Command Get-PublicFolderStatistics yields the public folder hierarchy, but not the public folder contents (number of entries is 0 for each)
  • The following error was resident in the 2010 Server Application Event Log when trying to force public folder replication and key to diagnosing the issue. Your mileage may vary.

Log Name:      Application
Source:        MSExchange Store Driver
Date:          Date and Time
Event ID:      1020
Task Category: MSExchangeStoreDriver
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Computer
Description:
The store driver couldn’t deliver the public folder replication message “Backfill Request (SMTP Address)” because the following error occurred: Property: [0x3ff00102] , PropertyErrorCode: UnknownError, PropertyErrorDescription: 0x80040107.

Resolution

Oddly enough, this is a known and documented issue by Microsoft. Took some digging to figure it out though. This bug is fixed in Update Rollup 2 for Exchange 2010 SP3.


Scenario 2

Now, if you’ve arrived at this page and your symptoms are slightly different, keep reading on.

A very similar issue exists that will throw event id 1020 and prevent migration as well. If you have ever had an Exchange 2003 Server in your Organization, you may encounter this error.

Thats right – even if it was 10 years ago, if you at any point in time had an Exchange 2003 server in your Exchange Organization, you will encounter this error. The reason is because Microsoft does a pretty poor job of cleaning up remnants of Exchange 2003 when it is pulled out of the organization.

Log Name: Application
Source: MSExchange Store Driver
Event ID: 1020
Level: Error
Description:

The store driver couldnt deliver the public folder replication message “Hierarchy (PublicFolder@contoso.com)” because the following error occurred: The Active Directory user wasn’t found.

Note the reference to PublicFolder@consoto.com instead of 0x80040107 in the Event Log above.

In an environment where Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 previously existed, and all those servers have been removed, there is a chance that an Administraive Group (First Administrative Group or another custom Administrative Group) remains with a Servers container, but no servers inside it.

During replicaiton, when the Exchange 2010 Store Driver sees the empty Servers container in Active Directory, it’s expecting a System Attendant object inside the container and when it is not found the error occurs.

In this scenario, the resolution is pretty intimidating. It involves using ADSIEdit and removing the blank CN=Servers container within the Configuration context of your domain.

  1. Start the ADSI Edit tool. To do this, click Start , click Run , type adsiedit.msc , and then click OK
  2. Expand Configuration Container [servername.domainname.com] , and then expand CN=Configuration,DC=DomainName,DC=com
  3. Expand CN=Services, expand CN=Microsoft Exchange, and then expand CN=OrganizationName where OrganizationName is the name of your Exchange organization.
  4. You will see the empty Administrative Group. Expand the CN=AdministrativeGroupName
  5. Expand CN=Servers
  6. Verify there are no server objects listed under the Servers container
  7. Right click on the emtpy CN=Servers Container and choose Delete.

See http://support.microsoft.com/kb/2487271 for more information.

I actually had both of these issues, with the ADSIEdit being required before finding out that there was another issue which SP3 Rollup2 resolves.

All data and information provided on this site is for informational purposes only. The author(s) make no guarantees as to accuracy, completeness, currentness, suitability, or validity of any information on this site and will not be liable for any errors or omissions in this information or any losses, injuries, or damages arising from its display or use. All information is provided on an as-is basis.

Leave a Comment

Your email address will not be published. Required fields are marked *