sunnysaran
asked on
DCPROMO did not create SYSVOL and NETLOGON SHARES
Hello Experts, I have this problem today. I will greatly appreciate any help.
I have a Windows 2000 Server (SP4) AD network with my exchange server running on a Win 2003 server. I had one domain controller. The DC is active and works fine, but recently the DC had lot of spyware and we are unable to see the desktop. All services work fine, but we just cannot see the desktop. Even safe mode does not help.
To save myself I tried to setup another domain controller by using DC promo. The DC promo successfully completed, but I am unfortunately unable to see the SYSVOL and NETLOGON shares.
Now since the SYSVOL and Netlogon are not shared the RFS fails. Can some help me to fix this issue. My new DC is unable to take over as the PDC when I switch off the OLD DC.
Will sincerely appreciate any help.
I have a Windows 2000 Server (SP4) AD network with my exchange server running on a Win 2003 server. I had one domain controller. The DC is active and works fine, but recently the DC had lot of spyware and we are unable to see the desktop. All services work fine, but we just cannot see the desktop. Even safe mode does not help.
To save myself I tried to setup another domain controller by using DC promo. The DC promo successfully completed, but I am unfortunately unable to see the SYSVOL and NETLOGON shares.
Now since the SYSVOL and Netlogon are not shared the RFS fails. Can some help me to fix this issue. My new DC is unable to take over as the PDC when I switch off the OLD DC.
Will sincerely appreciate any help.
Do you have a backup of the systemstate for the old DC?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
C:\Documents and Settings\Administrator.INT
Default-First-Site-Name\NE
DSA Options : IS_GC
objectGuid : bcb42711-d833-4ddb-a8c2-35
invocationID: 16196914-cbb2-4a49-b0b9-44
==== INBOUND NEIGHBORS ==========================
CN=Schema,CN=Configuration
Default-First-Site-Name\OL
objectGuid: eb395b91-95cc-4b48-a77a-0a
Last attempt @ 2007-07-12 06:48.45 was successful.
CN=Configuration,DC=interp
Default-First-Site-Name\OL
objectGuid: eb395b91-95cc-4b48-a77a-0a
Last attempt @ 2007-07-12 07:24.51 was successful.
DC=interprintusa,DC=com
Default-First-Site-Name\OL
objectGuid: eb395b91-95cc-4b48-a77a-0a
Last attempt @ 2007-07-12 07:27.18 was successful.
==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============
CN=Schema,CN=Configuration
Default-First-Site-Name\OL
objectGuid: eb395b91-95cc-4b48-a77a-0a
CN=Configuration,DC=interp
Default-First-Site-Name\MA
objectGuid: eb395b91-95cc-4b48-a77a-0a
DC=interprintusa,DC=com
Default-First-Site-Name\OL
objectGuid: eb395b91-95cc-4b48-a77a-0a
C:\Documents and Settings\Administrator.INT
(C) Copyright 1985-2000 Microsoft Corp.
C:\Documents and Settings\Administrator.INT
Default-First-Site-Name\NE
DSA Options : IS_GC
objectGuid : bcb42711-d833-4ddb-a8c2-35
invocationID: 16196914-cbb2-4a49-b0b9-44
==== INBOUND NEIGHBORS ==========================
CN=Schema,CN=Configuration
Default-First-Site-Name\OL
objectGuid: eb395b91-95cc-4b48-a77a-0a
Last attempt @ 2007-07-12 06:48.45 was successful.
CN=Configuration,DC=interp
Default-First-Site-Name\OL
objectGuid: eb395b91-95cc-4b48-a77a-0a
Last attempt @ 2007-07-12 07:24.51 was successful.
DC=interprintusa,DC=com
Default-First-Site-Name\OL
objectGuid: eb395b91-95cc-4b48-a77a-0a
Last attempt @ 2007-07-12 07:27.18 was successful.
==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============
CN=Schema,CN=Configuration
Default-First-Site-Name\OL
objectGuid: eb395b91-95cc-4b48-a77a-0a
CN=Configuration,DC=interp
Default-First-Site-Name\MA
objectGuid: eb395b91-95cc-4b48-a77a-0a
DC=interprintusa,DC=com
Default-First-Site-Name\OL
objectGuid: eb395b91-95cc-4b48-a77a-0a
C:\Documents and Settings\Administrator.INT
ASKER
FRS LOGS:
The File Replication Service is having trouble enabling replication from MAIL to NEWDC for c:\winnt\sysvol\domain using the DNS name mail.interprintusa.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name mail.interprintusa.com from this computer.
[2] FRS is not running on mail.interprintusa.com.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
The File Replication Service is having trouble enabling replication from MAIL to NEWDC for c:\winnt\sysvol\domain using the DNS name mail.interprintusa.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name mail.interprintusa.com from this computer.
[2] FRS is not running on mail.interprintusa.com.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
ASKER
FRS Event Error from OLDDC:
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\winnt\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.
[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\winnt\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.
[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
ASKER
Thank you ajbrotton and kprad. I do not have system state backup.
KPRAD - I have posted the logs you wanted. I am able o access the logs, services and the sysvol share on the old dc except see the desktop.
Any more suggestions?
KPRAD - I have posted the logs you wanted. I am able o access the logs, services and the sysvol share on the old dc except see the desktop.
Any more suggestions?
ASKER
KPRAD - I had the error below when I checked into the eventlog of my old dc. I followed the instructions below and fixed the registry entry(for DWORD Enable Journal Wrap Automatic Restore) in the OLD DC. Lo and Behold, I got my issue resolved. Thanks for the suggestion.
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\winnt\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.
[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\winnt\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.
[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value
I'm having the same issue. Did this get anywhere?
ASKER
C:\Documents and Settings\Administrator.INT
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\NE
Starting test: Connectivity
......................... NEWDC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\NE
Starting test: Replications
......................... NEWDC passed test Replications
Starting test: NCSecDesc
......................... NEWDC passed test NCSecDesc
Starting test: NetLogons
......................... NEWDC passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\OLDDC.interprintusa.com
when we were trying to reach NEWDC.
Server is not responding or is not considered suitable.
Warning: NEWDC is not advertising as a time server.
......................... NEWDC failed test Advertising
Starting test: KnowsOfRoleHolders
......................... NEWDC passed test KnowsOfRoleHolders
Starting test: RidManager
......................... NEWDC passed test RidManager
Starting test: MachineAccount
......................... NEWDC passed test MachineAccount
Starting test: Services
......................... NEWDC passed test Services
Starting test: ObjectsReplicated
......................... NEWDC passed test ObjectsReplicated
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... NEWDC passed test frssysvol
Starting test: kccevent
......................... NEWDC passed test kccevent
Starting test: systemlog
......................... NEWDC passed test systemlog
Running enterprise tests on : interprintusa.com
Starting test: Intersite
......................... interprintusa.com passed test Intersite
Starting test: FsmoCheck
......................... interprintusa.com passed test FsmoCheck
C:\Documents and Settings\Administrator.INT