From the mailbag this morning….

“Can you assist or point me in the right direction please.
I am following the MS guide v3 and have got an error with “Move Exchange Server Public Folders” section. pg40

When i right click on the public folder store and then click move all replicas I get an error as follows

An existing connection was forcibly closed by the remote host.
Facility Win32
ID no: c0072746
Exchange System Manager

I have ignored and carried on in the meantime and am currently at page 49 Migrate internal website.

I cannot find any resolutions for this error on the web.

I have tried using ADSI Edit and removed msExchSecureBindings using port 443 from the source server & checked destination but it was not set there.

Can you help? IS this a show stopper or can i ignore. we do not use the public folders here”


First off the ADSIedit should work… I’d start by retracing the steps to make sure that the 443 truly is removed

A good blog post that recaps the issues is here:

PROBLEM: Public Folder Migration


Go to Start – Programs – Support Tools – Tools and launch ADSI Edit.
>> In the left side pane expand the Configuration container.
>> Next expand CN=Configuration
>> Then CN=Services
>> CN=Microsoft Exchange
>> CN=” “your organization name here>
>> CN=Administrative Groups
>> CN=First Administrative Group
>> CN=Servers
>> CN=Protocols
>> CN=1
>> Right Click on CN=Exadmin and choose Properties.
>> In the Properties dialog box observed that msExchSecureBindings was set to 443
>> Removed the entry 443 from msExchSecureBindings
>> Close out of ADSI Edit,
>> Restarted IISadmin service.

That should fix the issue, if it doesn’t we have additional options…..

We can workaround the issue by doing the following:

Move Content Replica back to SBS 2003
Verify Item count and size in outlook
Export to PST from outlook
Move Replica back to SBS 2008
Import PST from outlook (Do not import dupe)
Mount Blank PF database/Or delete PF Database from ADSIEDIT Manually.

Using Outlook and exporting out to PST is actually a step that many do as a safety net anyway…

The common issues that trigger public folder replication issues during migration are

Smarthost on SMTP Virtual Server
Outbound Security on SMTP Virtual Server
Outbound Port on SMTP Virtual Server
Blocked Senders list
Authentication on SMTP Virtual Server

More resources include:

842273    How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003;EN-US;842273
Understanding Public Folder Replication
Three Part Troubleshooting Series

If you don’t use public folders though you can just plow on after this step and go on and ignore the error.  It’s only when you really DO use public folders that you are sweating bullets when this step doesn’t work.

So plow forth my friend and let me know how the migration goes.

(Special thanks to Damian and Wayne and Jim who all contributed to this post with some very timely information to enable me to make a more complete answer for everyone)


One Response to An existing connection was forcibly closed by the remote host

  1. Graham Campbell says:

    Thanks for getting back to me on this Susan

    I have double checked those steps by doing this

    On SBS2008 box
    1 open ADSI Edit
    2 Action Menu / Connect to
    3 On Connections Settings dialog I chose Select a well known naming context & selected Configuration in the drop down & entered the domain name in the “select or type domain or server”
    4 I then followed the instructions below to get to the CN=Exadmin, right clicked, chose properties and found msExchSecureBindings. The Value is not set.
    5 I have restarted the source server and restarted IIS admin service on destination server and still get the same error.

    I have also ran through the blog post already and didn’t have to change anything

    I am going to plow on ahead now & will let you know how I get on.


    Graham Campbell