Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

Windows 2008 R2 DC do not have the Sysvol and Netlogon Shares

Hello All I need a Big Help,

I Have a Domain with one Windows 2008 R2 domain controller running on forest and domain levels at 2008 R2.
This domain controller is working normal, But I need add another Windows 2008 R2 server as a second domain controller.
When I promote this second domain controller, the Sysvol and Netlogon shares does not appears.
If I take a look at c:\windows\sysvol, the DCPROMO creates the sysvol folder structure but with no files inside it.
Can anyone help me to resolve this, I tried to find out here some solutions, but I can only find solutions base on mixed environment, when you have Windows 2003 and 2008 together and the replication is based on NTFRS not on DFS.

Thanks a lot for any help.
0
thebugs
Asked:
thebugs
1 Solution
 
ChrisCommented:
0
 
ChrisCommented:
if that doesn't work what do you get out of dcdiag or event logs
0
 
Mike KlineCommented:
What events are you seeing in your logs, have you tested/verified replication.  

Thanks

Mike
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
Lee W, MVPTechnology and Business Process AdvisorCommented:
If memory serves, FRS is still used in 2008 R2.  Or it may be based on the Domain level.  I'd try the fix used in FRS.  I'm fairly certain that will take care of your issue.  (BurFlags fix).
0
 
ChrisCommented:
it uses DFSR to replicate rather than the standard 2003 DFS

so look under the event logs and then application logs where you will see the additional ones for domain controllers and look at the DFS Replication log and see if its full of red or yellow
0
 
thebugsAuthor Commented:
Hello all, Thanks for the reply,

I Found the issue but not the resolution, Looking at DFS logs, I saw that I getting several errors It´s starts with the warning 2212, that says:

"The DFS Replication service has detected an unexpected shutdown on volume C:. This can occur if the service terminated abnormally (due to a power loss, for example) or an error occurred on the volume. The service has automatically initiated a recovery process. The service will rebuild the database if it determines it cannot reliably recover. No user action is required.
 
Additional Information:
Volume: C:
GUID: CA31CC2B-17D3-11E1-B230-806E6F6E6963"

Than I get another error 2104,

"The DFS Replication service failed to recover from an internal database error on volume C:. Replication has been stopped for all replicated folders on this volume.
 
Additional Information:
Error: 9214 (Internal database error (-1605))
Volume: CA31CC2B-17D3-11E1-B230-806E6F6E6963
Database: C:\System Volume Information\DFSR"

And after all that I get that last error 2004:

The DFS Replication service stopped replication on volume C:. This failure can occur because the disk is full, the disk is failing, or a quota limit has been reached. This can also occur if the DFS Replication service encountered errors while attempting to stage files for a replicated folder on this volume.
 
Additional Information:
Error: 9014 (Database failure)
Volume: CA31CC2B-17D3-11E1-B230-806E6F6E6963"

So, I Saw at my disk space and it has 17 GB of free space.
Tried the CHKDSK but no error found.
Inside System and application logs, there is no error regarding lost of connectivity of c:.

I Saw in a few places that, we have to shutdown the DFS services, delete the replication partners and uninstall the dfs, after that delete c:\system volume information\dfs folder and than re - install DFS services and recreate the replication partner, but this resolution is for a DFS service installed without the ADDS.

So the question is, how do I resolve this?

Please help me.
0
 
ChrisCommented:
there is this that matches all the errors

http://support.microsoft.com/kb/2517913

or this might be more workable from a technet forum - i know its 2003 but...its common to try this on file servers with DFS/DFSR

According to the following article, this error may be caused by lack of disk space or corrupt DFSR files.
Error event IDs 2014 and 2004 and other Error events may be logged when you try to perform a replication on a Windows Server 2003 R2-based server that has DFSR installed
http://support.microsoft.com/kb/95755
 
1.Please check the size of replicated folder and free space of the problematic server.
2.Please check if the NT AUTHORITY\System account has Full Control permissions on "System Volume Information" folder.
3.If there are enough free space, please try deleting the DFS-R folder for troubleshooting.  
a.Stop the "DFS Replication" service on problem server.
b.On the system drive on problem server, show hidden files and system protected files. Give all permission on "System Volume Information" folder to you.
c.Double-click "System Volume Information", we should find DFSR folder. Backup this folder to avoid data loss.
d.Delete all "DfsrPrivate" folder in DFSR if there are several subfolder.
Restart "DFS Replication" service and test.
0
 
thebugsAuthor Commented:
Hello all,

Thanks for all responses, I tried deleting of the DFSR folder and the errors at Event Viewer stopped,  but I still don´t have the replication of the sysvol and netlogon, and still don´t have it shared on the second server.
I also getting some errors on the DFSR debug logs on both servers, ( c:\windows \debug ), as I show bellow:

20130116 22:54:04.883 3472 SRTR   957 [WARN] SERVER_EstablishSession Failed to establish a replicated folder session. connId:{A8C9DDD9-1D3A-4E55-ABB4-FC88834BDC0C} csId:{DC8FF479-DBF1-4F37-B006-A73B85982263} Error:
+      [Error:9051(0x235b) UpstreamTransport::EstablishSession upstreamtransport.cpp:808 3472 C The content set is not ready]
+      [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:532 3472 C The content set is not ready]
+      [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:471 3472 C The content set is not ready]
20130116 22:55:00.290 1728 DOWN  4186 DownstreamTransport::EstablishSession Failed on connId:{F3DD74E6-FCE3-4D28-A28D-1A2C32B80D4E} csId:{DC8FF479-DBF1-4F37-B006-A73B85982263} rgName:Domain System Volume Error:
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4179 1728 C A failure was reported by the remote partner]
+      [Error:9051(0x235b) DownstreamTransport::EstablishSession downstreamtransport.cpp:4179 1728 C The content set is not ready]
20130116 22:55:00.290 1728 INCO  7487 InConnection::RestartSession Retrying establish contentset session. connId:{F3DD74E6-FCE3-4D28-A28D-1A2C32B80D4E} csId:{DC8FF479-DBF1-4F37-B006-A73B85982263} csName:SYSVOL Share
20130116 22:55:00.290 1728 INCO  1042 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error:
+      [Error:9027(0x2343) InConnection::EstablishSession inconnection.cpp:6172 1728 C A failure was reported by the remote partner]
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4200 1728 C A failure was reported by the remote partner]
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4179 1728 C A failure was reported by the remote partner]
+      [Error:9051(0x235b) DownstreamTransport::EstablishSession downstreamtransport.cpp:4179 1728 C The content set is not ready]
20130116 22:55:00.291 1728 ISYN    68 InitialSyncManager::ReturnToken InitialSync sync step not finished yet. Wake up other session tasks.
20130116 22:56:05.775  688 SRTR   957 [WARN] SERVER_EstablishSession Failed to establish a replicated folder session. connId:{A8C9DDD9-1D3A-4E55-ABB4-FC88834BDC0C} csId:{DC8FF479-DBF1-4F37-B006-A73B85982263} Error:
+      [Error:9051(0x235b) UpstreamTransport::EstablishSession upstreamtransport.cpp:808 688 C The content set is not ready]
+      [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:532 688 C The content set is not ready]
+      [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:471 688 C The content set is not ready]
20130116 22:57:00.659 1728 DOWN  4186 DownstreamTransport::EstablishSession Failed on connId:{F3DD74E6-FCE3-4D28-A28D-1A2C32B80D4E} csId:{DC8FF479-DBF1-4F37-B006-A73B85982263} rgName:Domain System Volume Error:
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4179 1728 C A failure was reported by the remote partner]
+      [Error:9051(0x235b) DownstreamTransport::EstablishSession downstreamtransport.cpp:4179 1728 C The content set is not ready]
20130116 22:57:00.659 1728 INCO  7487 InConnection::RestartSession Retrying establish contentset session. connId:{F3DD74E6-FCE3-4D28-A28D-1A2C32B80D4E} csId:{DC8FF479-DBF1-4F37-B006-A73B85982263} csName:SYSVOL Share
20130116 22:57:00.659 1728 INCO  1042 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error:
+      [Error:9027(0x2343) InConnection::EstablishSession inconnection.cpp:6172 1728 C A failure was reported by the remote partner]
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4200 1728 C A failure was reported by the remote partner]
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4179 1728 C A failure was reported by the remote partner]
+      [Error:9051(0x235b) DownstreamTransport::EstablishSession downstreamtransport.cpp:4179 1728 C The content set is not ready]
20130116 22:57:00.659 1728 ISYN    68 InitialSyncManager::ReturnToken InitialSync sync step not finished yet. Wake up other session tasks.

Anyone have any idea about it?

Thanks again.
0
 
thebugsAuthor Commented:
Hello all,

Thanks a lot for all your answers, After months of trying I changed the FSMO owner to the second server, after that the sysvol and netlogon were replicated and the shares appeared.

Thanks
0
 
thebugsAuthor Commented:
I just resolved my problem doing this.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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