DFS on Server 2008 – Error ID: 9032 (The connection is shutting down). Event ID: 5002
1. The problematic replicated folder is “waiting for initial replication”, this could be due to the not setting the primary member.
Please run the following command to find if you have any primary server already for that RG name (IsPrimary=Yes)
Dfsradmin Membership List /RGname:<replication group name> /attr:MemName,RFName,IsPrimary
If the result shows the value for IsPramary attribute is “No”, that means you don’t have any primary server. In this situation, you may set the primary server using the following command
Dfsradmin Membership Set /RGName:<replication group name> /RFName:<replicated folder name> /MemName:<computer name of the member you want to set> /IsPrimary:True
EX. dfsradmin membership set /RGname:contoso.com\namespace\testfolder /RFName:testfolder /memname:Win-DFS-1 /isPrimary:True
2. The actual size of the problematic replicated folder is 3.82GB and the configured size for the staging folder is 4G. I would like to suggest that you set the size of the staging folder is 2 times in large of the replicated folder. It is better to be 7.64GB in size.
3. This member is waiting for initial replication for replicated folder <problematic replicated folder> and is not currently participating in replication. Please check <problematic replicated folder> is enabled in the corresponding replication group.
4. Also, to verify that the DFS replication service can work normally, please make sure that the both of the DFS member servers can be resolved the name of each other. Meanwhile, please verify that the “DFS Replication” and “DFS Namespace” services are started on both DFS member servers.
5. This delay can occur because the member is waiting for the DFS Replication service to retrieve replication settings from Active Directory Domain Services. After the member detects that it is part of replication group, the member will begin initial replication.
There are five common causes of the error that can be occurred, please refer to the following Storage team blog to check if it can be helpful for you.
6. Meanwhile, please download the portqry tool and install it on another server. You can use the following command to verify that the required ports are open.
a. Click Start, click Run, type cmd in the Open box, and then click OK.
b. Type “portqry -n problem_server -e 135” (without quotation mark)
Download: PortQryUI – User Interface for the PortQry Command Line Port Scanner