Re: Unable to decommission a Windows 2008 DC via dcpromo
- From: Haji <Haji@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 6 Jul 2009 05:53:01 -0700
Server2 oddly enough doesn't have a sysvol or netlogon share, which could be
an issue... I noticed that when I initially setup the server, so I manually
created them, but apparently they didn't "stick."
Neither server has a firewall active on them. Both are disabled.
All pings are successful between both servers.
"Meinolf Weber [MVP-DS]" wrote:
Hello Haji,.
Can you open and compare sysvol and netlogon share on both DCs?
Please ping between both DCs with ipaddress, computername and FQDN.
Any firewall running between them?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
dcdiag from server2, which is the new one:
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
* Verifying that the local machine server2, is a Directory Server.
Home Server = server2
* Connecting to directory service on server server2.
* Identified AD Forest.
Collecting AD specific global data
* Collecting site info.
Calling
ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=domain,DC=dns,L
DAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
The previous call succeeded
Iterating through the sites
Looking at base site object: CN=NTDS Site
Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domai
n,DC=dns
Getting ISTG and options for the site
* Identifying all servers.
Calling
ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=domain,DC=dns,L
DAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
The previous call succeeded....
The previous call succeeded
Iterating through the list of servers
Getting information for the server CN=NTDS
Settings,CN=server1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=
Configuration,DC=domain,DC=dns
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
Getting information for the server CN=NTDS
Settings,CN=server2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=
Configuration,DC=domain,DC=dns
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\server2
Starting test: Connectivity
* Active Directory LDAP Services Check
Determining IP4 connectivity
Determining IP6 connectivity
* Active Directory RPC Services Check
......................... server2 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\server2
Starting test: Advertising
Warning: DsGetDcName returned information for
\\server1.domain.dns, when we were trying to reach server2.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
......................... server2 failed test Advertising
Test omitted by user request: CheckSecurityError
Test omitted by user request: CutoffServers
Starting test: FrsEvent
* The File Replication Service Event log test
There are warning or error events within the last 24 hours
after the
SYSVOL has been shared. Failing SYSVOL replication problems
may cause
Group Policy problems.
An Warning Event occurred. EventID: 0x800034C4
Time Generated: 07/04/2009 19:53:44
Event String:
The File Replication Service is having trouble enabling
replication from server1.domain.dns to server2 for
c:\windows\sysvol\domain using the DNS name server1.domain.dns. FRS
will keep retrying.
Following are some of the reasons you would see this
warning.
[1] FRS can not correctly resolve the DNS name
server1.domain.dns from this computer.
[2] FRS is not running on server1.domain.dns.
[3] The topology information in the Active Directory
Domain Services 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.
An Warning Event occurred. EventID: 0x800034FE
Time Generated: 07/05/2009 17:59:10
Event String:
File Replication Service is scanning the data in the
system volume. Computer server2 cannot become a domain controller
until this process is complete. The system volume will then be shared
as SYSVOL.
To check for the SYSVOL share, at the command prompt,
type:
net share
When File Replication Service completes the scanning
process, the SYSVOL share will appear.
The initialization of the system volume can take some
time. The time is dependent on the amount of data in the system
volume.
An Warning Event occurred. EventID: 0x800034C4
Time Generated: 07/05/2009 18:02:00
Event String:
The File Replication Service is having trouble enabling
replication from server1.domain.dns to server2 for
c:\windows\sysvol\domain using the DNS name server1.domain.dns. FRS
will keep retrying.
Following are some of the reasons you would see this
warning.
[1] FRS can not correctly resolve the DNS name
server1.domain.dns from this computer.
[2] FRS is not running on server1.domain.dns.
[3] The topology information in the Active Directory
Domain Services 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.
An Warning Event occurred. EventID: 0x800034FE
Time Generated: 07/05/2009 18:08:29
Event String:
File Replication Service is scanning the data in the
system volume. Computer server2 cannot become a domain controller
until this process is complete. The system volume will then be shared
as SYSVOL.
To check for the SYSVOL share, at the command prompt,
type:
net share
When File Replication Service completes the scanning
process, the SYSVOL share will appear.
The initialization of the system volume can take some
time. The time is dependent on the amount of data in the system
volume.
An Warning Event occurred. EventID: 0x800034C4
Time Generated: 07/05/2009 18:10:22
Event String:
The File Replication Service is having trouble enabling
replication from server1.domain.dns to server2 for
c:\windows\sysvol\domain using the DNS name server1.domain.dns. FRS
will keep retrying.
Following are some of the reasons you would see this
warning.
[1] FRS can not correctly resolve the DNS name
server1.domain.dns from this computer.
[2] FRS is not running on server1.domain.dns.
[3] The topology information in the Active Directory
Domain Services 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.
An Warning Event occurred. EventID: 0x800034C4
Time Generated: 07/05/2009 18:18:22
Event String:
The File Replication Service is having trouble enabling
replication from server1 to server2 for c:\windows\sysvol\domain using
the DNS name server1.domain.dns. FRS will keep retrying.
Following are some of the reasons you would see this
warning.
[1] FRS can not correctly resolve the DNS name
server1.domain.dns from this computer.
[2] FRS is not running on server1.domain.dns.
[3] The topology information in the Active Directory
Domain Services 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.
......................... server2 passed test FrsEvent
Starting test: DFSREvent
The DFS Replication Event Log.
There are warning or error events within the last 24 hours
after the
SYSVOL has been shared. Failing SYSVOL replication problems
may cause
Group Policy problems.
An Error Event occurred. EventID: 0xC00004B2
Time Generated: 07/05/2009 17:59:35
Event String:
The DFS Replication service failed to contact domain
controller to access configuration information. Replication is
stopped. The service will try again during the next configuration
polling cycle, which will occur in 60 minutes. This event can be
caused by TCP/IP connectivity, firewall, Active Directory Domain
Services, or DNS issues.
Additional Information:
Error: 160 (One or more arguments are not correct.)
......................... server2 failed test DFSREvent
Starting test: SysVolCheck
* The File Replication Service SYSVOL ready test
The registry lookup failed to determine the state of the
SYSVOL. The
error returned was 0x0 "The operation completed
successfully.".
Check the FRS event log to see if the SYSVOL has successfully
been
shared.
- Follow-Ups:
- Re: Unable to decommission a Windows 2008 DC via dcpromo
- From: Meinolf Weber [MVP-DS]
- Re: Unable to decommission a Windows 2008 DC via dcpromo
- References:
- Unable to decommission a Windows 2008 DC via dcpromo
- From: Haji
- Re: Unable to decommission a Windows 2008 DC via dcpromo
- From: Meinolf Weber [MVP-DS]
- Re: Unable to decommission a Windows 2008 DC via dcpromo
- From: Haji
- Re: Unable to decommission a Windows 2008 DC via dcpromo
- From: Meinolf Weber [MVP-DS]
- Unable to decommission a Windows 2008 DC via dcpromo
- Prev by Date: Re: Clients hanging, file share browsing slows, logins take minute
- Next by Date: Re: Unable to decommission a Windows 2008 DC via dcpromo
- Previous by thread: Re: Unable to decommission a Windows 2008 DC via dcpromo
- Next by thread: Re: Unable to decommission a Windows 2008 DC via dcpromo
- Index(es):
Relevant Pages
|
Loading
