Sysvol&Netlogon_Not appear
Dear All
I have a 2012 AD Server and add a new 2012 AD Server for BDC, however, after the second AD Server join into the first DC, the Sysvol, netlogon do not create auto and shared.
The first AD Server's Sysvol and the netlogon is normal and shared. How can I fix the problem in the second server? Thanks.
First of all, I would recommend using dcdiag and repadmin
to check the health status of your DCs and the AD replication. Also, I would recommend that you refer to the recommendations I stated here: http://social.technet.microsoft.com/wiki/contents/articles/18513.active-directory-replication-issues-basic-troubleshooting-steps-single-ad-domain-in-a-single-ad-forest.aspx
You can also give a look to this: http://www.appdelivery.com/2013/11/the-case-of-the-missing-netlogon-share/
Another thing you can do is to do a non-authoritative restore of DFSR for SYSVOL as mentioned in the first article.
If none helps then you might to temporary disable security software you use on your DCs and make sure that the traffic between them is not filtered or blocked. Of couse, as this is a new DC then you are able to demote it and promote it again (Better to re-install
the OS and install the available Windows updates before promoting it again).
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile
Similar Messages
-
AD Replication issues, SYSVOL / NETLOGON not replicating
Hello Experts!
We have a client that recently called us for some assistance. The IT department had a new virtual environment stood up. They Created 3 new VMs and promoted them all to domain controllers. The current domain and forest functional levels are (and were) Server
2003. There were two existing domain controllers, both Server 2003. The new domain controllers are Server 2012 R2. After promoting the 3 new servers to DC’s, they demoted one of the old DC’s. Then they transferred FSMO roles to a new 2012 R2 DC. When they
went to demote the last server 2003 DC, it was giving them the error that it is the last DC in the domain. That’s when we were called to assist. I have since demoted 2 of the 3 new 2012 R2 DCs and transferred all FSMO roles back to the Server 2003 DC.
I have been running some tools to try and gather data. Here is the DCDIAG from the last Server 2003 DC:
C:\Documents and Settings\user>dcdiag /fix
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: domainname\server2003server
Starting test: Connectivity
......................... server2003server passed test Connectivity
Doing primary tests
Testing server: domainname\server2003server
Starting test: Replications
......................... server2003server passed test Replications
Starting test: NCSecDesc
......................... server2003server passed test NCSecDesc
Starting test: NetLogons
......................... server2003server passed test NetLogons
Starting test: Advertising
......................... server2003server passed test Advertising
Starting test: KnowsOfRoleHolders
......................... server2003server passed test KnowsOfRoleHolders
Starting test: RidManager
......................... server2003server passed test RidManager
Starting test: MachineAccount
......................... server2003server passed test MachineAccount
Starting test: Services
......................... server2003server passed test Services
Starting test: ObjectsReplicated
......................... server2003server passed test ObjectsReplicated
Starting test: frssysvol
......................... server2003server passed test frssysvol
Starting test: frsevent
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.
......................... server2003server failed test frsevent
Starting test: kccevent
......................... server2003server passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x0000410B
Time Generated: 02/18/2015 19:27:04
Event String: The request for a new account-identifier pool
An Error Event occured. EventID: 0xC4350607
Time Generated: 02/18/2015 19:28:22
Event String: Component: System Information Agent
An Error Event occured. EventID: 0xC00110CD
Time Generated: 02/18/2015 19:28:22
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00072787
Time Generated: 02/18/2015 19:28:22
Event String: The WinRM service is unable to start because of a
An Error Event occured. EventID: 0xC0060024
Time Generated: 02/18/2015 19:28:34
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0002720
Time Generated: 02/18/2015 19:32:26
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC25A001D
Time Generated: 02/18/2015 14:33:27
(Event String could not be retrieved)
An Error Event occured. EventID: 0x825A0011
Time Generated: 02/18/2015 14:33:28
(Event String could not be retrieved)
An Error Event occured. EventID: 0x825A0011
Time Generated: 02/18/2015 14:33:31
(Event String could not be retrieved)
An Error Event occured. EventID: 0x0000410B
Time Generated: 02/18/2015 14:36:18
Event String: The request for a new account-identifier pool
An Error Event occured. EventID: 0xC4350607
Time Generated: 02/18/2015 14:38:48
Event String: Component: System Information Agent
An Error Event occured. EventID: 0x00072787
Time Generated: 02/18/2015 14:38:48
Event String: The WinRM service is unable to start because of a
An Error Event occured. EventID: 0xC4350505
Time Generated: 02/18/2015 14:38:54
Event String: NIC Agent: Connectivity has been lost for the NIC
An Error Event occured. EventID: 0x825A0011
Time Generated: 02/18/2015 14:39:00
(Event String could not be retrieved)
An Error Event occured. EventID: 0x825A0011
Time Generated: 02/18/2015 14:39:14
(Event String could not be retrieved)
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168E
Time Generated: 02/18/2015 14:39:54
Event String: The dynamic registration of the DNS record
An Error Event occured. EventID: 0x0000168F
Time Generated: 02/18/2015 14:42:09
Event String: The dynamic deletion of the DNS record
An Error Event occured. EventID: 0x0000168F
Time Generated: 02/18/2015 14:42:09
Event String: The dynamic deletion of the DNS record
An Error Event occured. EventID: 0x0000168F
Time Generated: 02/18/2015 14:42:09
Event String: The dynamic deletion of the DNS record
An Error Event occured. EventID: 0x0000168F
Time Generated: 02/18/2015 14:42:09
Event String: The dynamic deletion of the DNS record
An Error Event occured. EventID: 0xC25A001D
Time Generated: 02/18/2015 14:42:10
(Event String could not be retrieved)
An Error Event occured. EventID: 0x825A0011
Time Generated: 02/18/2015 14:42:22
(Event String could not be retrieved)
An Error Event occured. EventID: 0x825A0011
Time Generated: 02/18/2015 14:42:37
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC4350607
Time Generated: 02/18/2015 14:48:03
Event String: Component: System Information Agent
An Error Event occured. EventID: 0x00072787
Time Generated: 02/18/2015 14:48:03
Event String: The WinRM service is unable to start because of a
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 14:50:06
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 14:50:06
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 14:50:06
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 14:50:07
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 14:50:07
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 14:50:07
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 14:50:07
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 14:50:07
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 14:50:07
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 14:50:07
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 02/18/2015 14:55:30
Event String: The kerberos client received a
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:11:36
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:11:37
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:11:37
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:11:38
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:11:38
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:11:38
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:11:38
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:11:38
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:11:38
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:11:39
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:16:07
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:16:08
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:16:08
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:16:09
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:16:09
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:16:09
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:16:10
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:16:10
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:16:10
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/18/2015 15:16:10
(Event String could not be retrieved)
......................... server2003server failed test systemlog
Starting test: VerifyReferences
Some objects relating to the DC server2003server have problems:
[1] Problem: Missing Expected Value
Base Object:
CN= server2003server,OU=Domain Controllers,DC=domainname,DC=com
Base Object Description: "DC Account Object"
Value Object Attribute Name: frsComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
[1] Problem: Missing Expected Value
Base Object:
CN=NTDS Settings,CN= server2003server,CN=Servers,CN=domainname,CN=Sites,CN=C
onfiguration,DC=domainname,DC=com
Base Object Description: "DSA Object"
Value Object Attribute Name: serverReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
......................... server2003server failed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : domainname
Starting test: CrossRefValidation
......................... domainname passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... domainname passed test CheckSDRefDom
Running enterprise tests on : domainname.com
Starting test: Intersite
......................... domainname.com passed test Intersite
Starting test: FsmoCheck
......................... domainname.com passed test FsmoCheck
C:\Documents and Settings\user>
Now the DCDIAG for the Server 2012 R2 DC.
2012R2DC
PS C:\Users\user > dcdiag /fix
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = 2012R2DC
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: domainname\2012R2DC
Starting test: Connectivity
......................... 2012R2DC
passed test Connectivity
Doing primary tests
Testing server: domainname\2012R2DC
Starting test: Advertising
Warning: DsGetDcName returned information for \\server2003server.domainname.com, when we were trying to reach 2012R2DC.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
......................... 2012R2DC
failed test Advertising
Starting test: FrsEvent
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.
......................... 2012R2DC
passed test FrsEvent
Starting test: DFSREvent
......................... 2012R2DC passed test DFSREvent
Starting test: SysVolCheck
......................... 2012R2DC passed test SysVolCheck
Starting test: KccEvent
......................... 2012R2DC passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... 2012R2DC passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... 2012R2DC passed test MachineAccount
Starting test: NCSecDesc
......................... 2012R2DC passed test NCSecDesc
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\2012R2DC \netlogon)
[2012R2DC] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
......................... 2012R2DC failed test NetLogons
Starting test: ObjectsReplicated
......................... 2012R2DC passed test ObjectsReplicated
Starting test: Replications
[Replications Check, 2012R2DC] DsReplicaGetInfo(PENDING_OPS, NULL) failed, error 0x2105
"Replication access was denied."
......................... 2012R2DC failed test Replications
Starting test: RidManager
......................... 2012R2DC passed test RidManager
Starting test: Services
Could not open NTDS Service on 2012R2DC, error 0x5 "Access is denied."
......................... 2012R2DC failed test Services
Starting test: SystemLog
An error event occurred. EventID: 0x0000041E
Time Generated: 02/18/2015 14:39:32
Event String:
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could
be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
An error event occurred. EventID: 0x0000041E
Time Generated: 02/18/2015 14:44:34
Event String:
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could
be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
An error event occurred. EventID: 0x40000004
Time Generated: 02/18/2015 14:47:09
Event String:
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server cr-dc3$. The target name used was C
RDC02$. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when t
he target server principal name (SPN) is registered on an account other than the account the target service is using. En
sure that the target SPN is only registered on the account used by the server. This error can also happen if the target
service account password is different than what is configured on the Kerberos Key Distribution Center for that target se
rvice. Ensure that the service on the server and the KDC are both configured to use the same password. If the server nam
e is not fully qualified, and the target domain (domainname.COM) is different from the client domain (domainname.COM),
check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify
the server.
......................... 2012R2DC failed test SystemLog
Starting test: VerifyReferences
......................... 2012R2DC passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : domainname
Starting test: CheckSDRefDom
......................... domainname passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... domainname passed test CrossRefValidation
Running enterprise tests on : domainname.com
Starting test: LocatorCheck
......................... domainname.com passed test LocatorCheck
Starting test: Intersite
......................... domainname.com passed test Intersite
PS C:\Users\user>
From here I can see SYSVOL and NETLOGON are not replicating from server2003server. When I log on to server2003server and run ‘net share’ the SYSVOL and NETLOGON shares are shared. But, when I do the same on 2012R2DC there are no NETLOGON or SYSVOL shares.
I see ntfrs issues. So I ran ntfrsutl ds on server2003server and the results are here:
C:\Documents and Settings\user>ntfrsutl ds
NTFRS CONFIGURATION IN THE DS
SUBSTITUTE DCINFO FOR DC
FRS DomainControllerName: (null)
Computer Name : SERVER2003SERVER
Computer DNS Name : SERVER2003SERVER.domainname.com
BINDING TO THE DS:
ldap_connect : SERVER2003SERVER.domainname.com
DsBind : SERVER2003SERVER.domainname.com
NAMING CONTEXTS:
SitesDn : CN=Sites,cn=configuration,dc= domainname,dc=com
ServicesDn : CN=Services,cn=configuration,dc= domainname,dc=com
DefaultNcDn: DC= domainname,DC=com
ComputersDn: CN=Computers,DC= domainname,DC=com
DomainCtlDn: OU=Domain Controllers,DC= domainname,DC=com
Fqdn : CN= SERVER2003SERVER,OU=Domain Controllers,DC= domainname,DC=com
Searching : Fqdn
COMPUTER: SERVER2003SERVER
DN : cn= SERVER2003SERVER,ou=domain controllers,dc= domainname,dc=com
Guid : d3cfdf56-a013-40ab-a2e9ffc3d88896bd
UAC : 0x00082000
Server BL : CN= SERVER2003SERVER,CN=Servers,CN=domainname,CN=Sites,CN=Configuration,D
C= SERVER2003SERVER,DC=com
Settings : cn=ntds settings,cn= SERVER2003SERVER,cn=servers,cn= domainname,cn=sites,c
n=configuration,dc= domainname,dc=com
DNS Name : SERVER2003SERVER. domainname.com
WhenCreated : 5/29/2007 10:36:30 Eastern Standard Time Eastern Daylight Time
[300]
WhenChanged : 2/17/2015 11:21:58 Eastern Standard Time Eastern Daylight Time
[300]
SUBSCRIPTION: NTFRS SUBSCRIPTIONS
DN : cn=ntfrs subscriptions,cn= SERVER2003SERVER,ou=domain controllers,dc= domainname,dc=com
Guid : 5d0ca299-209d-4814-ae6d7acd9209e10a
Working : c:\windows\ntfrs
Actual Working: c:\windows\ntfrs
WhenCreated : 5/29/2007 10:50:26 Eastern Standard Time Eastern Daylight T
ime [300]
WhenChanged : 5/29/2007 10:50:26 Eastern Standard Time Eastern Daylight T
ime [300]
SUBSCRIBER: DOMAIN SYSTEM VOLUME (SYSVOL SHARE)
DN : cn=domain system volume (sysvol share),cn=ntfrs subscriptions,cn
= SERVER2003SERVER,ou=domain controllers,dc= domainname,dc=com
Guid : fb56d707-3c40-429f-bd7c63d227b9fb5d
Member Ref: (null)
Root : c:\windows\sysvol\domain
Stage : c:\windows\sysvol\staging\domain
WhenCreated : 5/29/2007 10:50:26 Eastern Standard Time Eastern Dayligh
t Time [300]
WhenChanged : 5/29/2007 10:50:26 Eastern Standard Time Eastern Dayligh
t Time [300]
SERVER2003SERVER IS NOT A MEMBER OF ANY SET!
C:\Documents and Settings\user>
Also worth noting that when we power down SERVER2003SERVER no computer can contact a logon server.
The last line of this worries me as well. I am going to continue to work on this but I wanted to get these logs to some other eyes in case you have some ideas off the bat. Thanks in advance!I would first recommend to make sure that the new DCs are also global catalogs and to refer to IP setting recommendations I shared here: http://www.ahmedmalek.com/web/fr/home.asp
It is possible to do a non-authoritative restore of SYSVOL to make it appear on the other DCs: https://support.microsoft.com/kb/290762?wa=wsignin1.0
However, you would need to upgrade to DFSR.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile -
SYSVOL on Win8 Clients DFS link points to wrong path
Since I introduced a secondary DSfW DC I experience wrong DFS paths on
my only Win8 DSfW member computer, if the active path of
\\domain\sysvol points to the secondary DC. It points to the sysvol on
the secondary DC instead of the sysvol-msdfs.
This happens especially after extended uptime of the Win8 machine. It
does not happen on Win7 and XP clients.
One thing to take into account further is, that on Win8 UAC is on
whereas UAC is off on Win7 (and of course XP).
I already removed this machine from the domain and readded it without
changing that behaviour and I have no real influence on that, too - as
it just happens out of the blue and I see that group policies could not
be applied due to the incorrect path. If I turn this machine off in the
evening and turn it on the next day settings are correct at the
beginning, but turn wrong after 6-12 hours of uptime.
I have no idea where to dig further.
W. PrindlW_,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/ -
Hi
I have a couple of Windows 2012 domain controllers that have stopped replicating their Sysvol folders.
I believe that the issue is with DC2 as it is missing some of the newer policies, despite having a lot more folders listed (these were old policies that have been removed).
The error message listed says
‘The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled.
To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.’
I have run the ResumeReplication which says it was successful. I then get a message that I have exceeded the maximum offline time of 60 days so I increase it with
‘The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 85 days,
which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.
To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes
the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group. ‘
I tried to remove server in the DFS Management snap-in but was unable to find the option so ran the command to increase the maximum offline time
wmic.exe /namespace:\\root\microsoftdfs path dfsrMachineConfig Set MaxOfflineTimeInDays=120
I restart the DFSR service and things initially look positive in the Event Viewer until I get an error…
The DFS Replication service stopped replication on the replicated folder at local path C:\Windows\SYSVOL\domain.
Additional Information:
Error: 9073 (Content set initialization is pending journal wrap task to resume journal read)
Running DCDiag appears to be fine with the exception of reporting there are errors in event log.
Can anyone assist with any suggestions on how to recover this without the need to completely rebuild the server. Active Directory seems to be replicating without issue, it’s just the Sysvol share.
Many thanks
SimonHi Simon,
I suggest you start with these links below:
Reconnecting a Domain Controller After a Long-Term Disconnection
http://technet.microsoft.com/en-us/library/cc794960(v=WS.10).aspx
Fixing Replication Lingering Object Problems (Event IDs 1388, 1988, 2042)
http://technet.microsoft.com/en-us/library/cc949124(v=ws.10).aspx
Restoring and Rebuilding SYSVOL
http://technet.microsoft.com/en-us/library/cc816596(v=WS.10).aspx
Best Regards,
Amy Wang -
Good Evening experts,
I have a Windows 2003 Standard DC which will soon be replaced with a Windows 2008 DC. I have given the 2008 box the DC role but I have noticed neither the sysvol nor netlogon share have appeared on the new DC. When I looked into this further,
I found this error on the 2003 server:
"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:\windows\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.
I don't have another DC to pull the sysvol/netlogon details from and wanted some advice.
BudBHeld,
Cheers for your reply, I was going to go down this road but wanted to ensure I was on the correct path. In addition, this particular domain is part of an overall forest but the other child domains are fine, its just this one that won't replicate.
Do I need to do anything on the domains in the other child domains or just what you had specified above? cheers
Dinesh,
Polices and Script folder is still there. Cheers
Bud
You only need to modify one of the DC in the problem domain. There is noting to be done in all other domains which are working fine. BTW, Sysvol/Netlogon shares are not replicated to other domains.
Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R
(2010-08-12) Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 1)
(2010-08-12) Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 2)
(2010-08-12) Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 3)
(2011-06-22) Restoring The SYSVOL (Non-)Authoritatively When Either Using NTFRS Or DFS-R (Part 4)
Awinish Vishwakarma - MVP
My Blog: awinish.wordpress.com
Disclaimer This posting is provided AS-IS with no warranties/guarantees and confers no rights. -
Unable to Sync SYSVOL Folder between Domain Controllers
Good Afternoon All,
I have the following issue on my current domain configuration, I say current as we are seeking to go to Server 2012 R2 within the next few months, but for now, we are at the 2008 R2 functional level.
We have three Domain Controllers namely Server-001 to 3, with Server-002 holding the PDC Emulator Role. Now when policies are created or updated through GP Management, I have noticed that they sync without issue between Server-002 and Server-003, but not
Server-001. In the SYSVOL Folder in each DC, the folder totals in policies are as follows:
Server-001 - 72 Folders
Server-002 - 96 Folders
Server-003 - 96 Folders
So here, it can be clearly seen that there is some sort of replication issue between Server-001 and the other controllers. I have researched and read several articles and opinions regarding the same issue and have ran many of the commands outlined including
repadmin, dnslint, gposync, etc. with the only output displaying errors being gposync. I have checked all the event logs for each DC with added focus on the DFS Replication Logs and have seen no errors regarding replication on Server-001 which is the server
at fault, but have noted that it appears that Server-001 is only replicating to itself, while Servers -002 and -003 are syncing/replicating between each other. I created a text document in Server-002's SYSVOL Folder and checked in Server-003's and verified
that the document successfully synced across, but on Server-001 nothing happened. I did some research on the issue and came across non-authoritative sysvol restore as an option, but when I tried this on Server-001 via ADSI Edit, I noticed that the following
path:
OU=Domain Controllers>CN=Server-001>CN=DSFR-LocalSettings>CN=Domain System Volume
is missing. Initially, DSFR-LocalSettings was missing as well, but I re-created it. I then attempted to re-create Domain System Volume, but when I tried entering the Replication Group GUID, I got an error that "one or more of the values are not in the
correct format", even though this is the same GUID used on the other two DCs. I tried changing the value to octet, hexadecimal, etc. but nothing worked. i still got the same error. I am convinced that this is where the disconnect lies, but with no possible
idea how to fix this broken section, I am unsure how to further proceed. We were going to demote the server, bring up a 2012 R2 unit and have it seize the roles, but I convinced my Systems Administrator for us to try and see if there is a fix available before
commissioning a new server. As is, group policy is somewhat broken as policies either do no get applied at all, or, get applied to certain groups or OUs.
If you are interested I can forward you our DFSR Logs from each server, along with any other reports that I have run in the hopes that someone will be able to assist. I hope that I have been as clear as possible and have provided as much information as is
possibly required.
Thank you all in advance.Hi,
To perform non-authoritative synchronization for DFSR-replicated SYSVOL, the following article can be referred to for more information.
How to force an authoritative and non-authoritative synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS)
http://support.microsoft.com/kb/2218556/en-us
Besides, we can use dcdiag command to check the health of the DC.
Dcdiag
http://technet.microsoft.com/en-us/library/cc731968.aspx
TechNet Subscriber Support
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Best regards,
Frank Shen -
Do you have multiple Domain controllers? If so look and see which DC you created it on. If so you may want to go to your other DC and see if DFS is running there. I had this issue then realized it just wasnt replicating to one of my other servers due to DFS not running on it.
Hello All,
I have created a GPO to install a peice of asset managment software on some test machines. However, it is not showing up in the sysvol of any of the domain controllers.
I tried to delete it, and recreate using another DC but I still have the same problem.
I have manually tried to replicate across all DC's but it still isn't showing. As far as I'm aware DFS is on and working.
Please help!
This topic first appeared in the Spiceworks Community -
Linked policies not copying to sysvol\domain\policies?
This problem started recently, and I have not been able to find any resolutions online.
This is a relatively new installation of Server 2012 R2 on a small network of about 25 PCs. I was able to set up a number of GPOs without issue, but all of a sudden, newly linked GPOs are not copying to sysvol\domain\policies. That path is accessible from client
PCs, but the folder itself (5C53E...) isn't created, and gpupdate is producing the error:
The processing of Group Policy failed. Windows attempted to read the file \\dominionair.local\SysVol\dominionair.local\Policies\{5C53EB48-F4BA-4763-8500-E05BB54E3AB4}\gpt.ini from a domain controller and was not successful. Group Policy settings may
not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.
Computer Policy update has completed successfully.
To diagnose the failure, review the event log or run GPRESULT /H GPReport.html f
rom the command line to access information about Group Policy results.
I AM able to add to existing GPOs and the settings update on client PCs, so this doesn't appear to be a permissions issue. Any idea where to start on this?
Thank you!> /The processing of Group Policy failed. Windows attempted to read the
> file
> \\dominionair.local\SysVol\dominionair.local\Policies\{5C53EB48-F4BA-4763-8500-E05BB54E3AB4}\gpt.ini
> from a domain controller and was not successful./
Your sysvol replication is broken. Check NTFRS or DFSR eventlogs on all
DCs and then follow either
http://support.microsoft.com/kb/315457
(NTFRS) or
http://support.microsoft.com/kb/2218556 (DFSR).
Martin
Mal ein
GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :)) -
SYSVOL Replication Failing - 13508
We have two 2008 R2 DCs and our second DC has been getting the 13508 for months. I have checked the logs and have found no instance of 13509.
I have recently set up a third DC (server 2012 R2) and am now getting the message on that machine as well. Except, now it's showing the message for DC1 and DC2.
The File Replication Service is having trouble enabling replication from DC2 to DC3 for c:\windows\sysvol\domain using the DNS name DC2. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC2 from this computer.
[2] FRS is not running on DC2.
[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.
I'm not exactly sure what that means, but I continued to do some diagnostics. I was able to ping the FQDN with no problem. I disabled the firewalls on all boxes and tested with no luck. There is now internal firewall blocking anything and
the proper ports are open and listening.
In addition, I have noticed on the DC that is NOT receiving the 13508 error has had a couple 13562 errors-
Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller DC1 for FRS replica set configuration information.
Could not bind to a Domain Controller. Will try again at next polling cycle.
Other than that, there are no FRS errors on DC1. Here are the results of DCDiag on DC1:
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = DC1
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC1
Starting test: Connectivity
......................... DC1 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC1
Starting test: Advertising
......................... DC1 passed test Advertising
Starting test: FrsEvent
......................... DC1 passed test FrsEvent
Starting test: DFSREvent
......................... DC1 passed test DFSREvent
Starting test: SysVolCheck
......................... DC1 passed test SysVolCheck
Starting test: KccEvent
......................... DC1 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... DC1 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... DC1 passed test MachineAccount
Starting test: NCSecDesc
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=ForestDnsZones,DC=domain,DC=local
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=DomainDnsZones,DC=domain,DC=local
......................... DC1 failed test NCSecDesc
Starting test: NetLogons
......................... DC1 passed test NetLogons
Starting test: ObjectsReplicated
......................... DC1 passed test ObjectsReplicated
Starting test: Replications
......................... DC1 passed test Replications
Starting test: RidManager
......................... DC1 passed test RidManager
Starting test: Services
......................... DC1 passed test Services
Starting test: SystemLog
......................... DC1 passed test SystemLog
Starting test: VerifyReferences
......................... DC1 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : domain
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Running enterprise tests on : domain.local
Starting test: LocatorCheck
......................... domain.local passed test LocatorCheck
Starting test: Intersite
......................... domain.local passed test Intersite
Here is the result from DC2:
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = DC2
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC2
Starting test: Connectivity
......................... DC2 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC2
Starting test: Advertising
......................... DC2 passed test Advertising
Starting test: FrsEvent
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.
......................... DC2 passed test FrsEvent
Starting test: DFSREvent
......................... DC2 passed test DFSREvent
Starting test: SysVolCheck
......................... DC2 passed test SysVolCheck
Starting test: KccEvent
......................... DC2 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... DC2 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... DC2 passed test MachineAccount
Starting test: NCSecDesc
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=ForestDnsZones,DC=domain,DC=local
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=DomainDnsZones,DC=domain,DC=local
......................... DC2 failed test NCSecDesc
Starting test: NetLogons
......................... DC2 passed test NetLogons
Starting test: ObjectsReplicated
......................... DC2 passed test ObjectsReplicated
Starting test: Replications
......................... DC2 passed test Replications
Starting test: RidManager
......................... DC2 passed test RidManager
Starting test: Services
......................... DC2 passed test Services
Starting test: SystemLog
A warning event occurred.
EventID: 0x8000001D
Time Generated: 03/25/2015 10:53:38
Event String:
The Key Distribution Center (KDC) cannot find a suitable certificate to use for smart card logons, or the KDC certificate could not be verified. Smart card logon may not function correctly if this problem is not resolved. To correct this problem, either
verify the existing KDC certificate using certutil.exe or enroll for a new KDC certificate.
......................... DC2 passed test SystemLog
Starting test: VerifyReferences
......................... DC2 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : domain
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Running enterprise tests on : domain.local
Starting test: LocatorCheck
......................... domain.local passed test LocatorCheck
Starting test: Intersite
......................... domain.local passed test Intersite
And finally, here is the result from DC3:
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC3
Starting test: Connectivity
......................... DC3 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC3
Starting test: Advertising
Warning: DsGetDcName returned information for \\DC1.domain.local,
when we were trying to reach DC3.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
......................... DC3 failed test Advertising
Starting test: FrsEvent
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.
......................... DC3 passed test FrsEvent
Starting test: DFSREvent
......................... DC3 passed test DFSREvent
Starting test: SysVolCheck
......................... DC3 passed test SysVolCheck
Starting test: KccEvent
......................... DC3 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... DC3 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... DC3 passed test MachineAccount
Starting test: NCSecDesc
......................... DC3 passed test NCSecDesc
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\DC3\netlogon)
[DC3] An net use or LsaPolicy operation failed with error 67,
The network name cannot be found..
......................... DC3 failed test NetLogons
Starting test: ObjectsReplicated
......................... DC3 passed test ObjectsReplicated
Starting test: Replications
......................... DC3 passed test Replications
Starting test: RidManager
......................... DC3 passed test RidManager
Starting test: Services
......................... DC3 passed test Services
Starting test: SystemLog
......................... DC3 passed test SystemLog
Starting test: VerifyReferences
......................... DC3 passed test VerifyReferences
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : domain
Starting test: CheckSDRefDom
......................... domain passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... domain passed test CrossRefValidation
Running enterprise tests on : domain.local
Starting test: LocatorCheck
......................... domain.local passed test LocatorCheck
Starting test: Intersite
......................... domain.local passed test Intersite
Any idea what would be causing this and what my next steps would be? Let me know if I can get you any more info.
Thanks for the help in advance!Hello,
Is this is the FRSDiag_Log file? If so, I don't see that type of message anywhere. On the FRSDiag when I select all the DCs and select go, I get the following:
DC1:
FRSDiag v1.7 on 4/8/2015 8:10:49 AM
.\DC1 on 2015-04-08 at 8.10.49 AM
Checking for errors/warnings in FRS Event Log .... passed
Checking for errors in Directory Service Event Log .... passed
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size... passed
Checking Overall Disk Space and SYSVOL structure (note: integrity is not checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ... passed
Checking NtFrs Service (and dependent services) state...passed
Checking NtFrs related Registry Keys for possible problems...passed
Checking Repadmin Showreps for errors...passed
Final Result = passed
DC2:
FRSDiag v1.7 on 4/8/2015 8:10:49 AM
.\DC2 on 2015-04-08 at 8.10.49 AM
Checking for errors/warnings in FRS Event Log ....
NtFrs
4/8/2015 2:56:42 AM
Warning 13508
The File Replication Service is having trouble enabling replication
from DC1 to DC2 for c:\windows\sysvol\domain using the DNS name DC1.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC1.domain.local from this computer.
[2] FRS is not running on DC1.domain.local.
[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.
NtFrs
4/8/2015 2:33:02 AM
Warning 13508
The File Replication Service is having trouble enabling replication
from DC3 to DC2 for c:\windows\sysvol\domain using the DNS name DC3.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC3.domain.local from this computer.
[2] FRS is not running on DC3.domain.local.
[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.
NtFrs
4/7/2015 1:27:11 AM
Warning 13508
The File Replication Service is having trouble enabling replication
from DC3 to DC2 for c:\windows\sysvol\domain using the DNS name DC3.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC3.domain.local from this computer.
[2] FRS is not running on DC3.domain.local.
[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.
NtFrs
4/7/2015 1:25:07 AM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC2 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
NtFrs
4/6/2015 3:25:32 PM
Warning 13520
The File Replication Service moved the preexisting files in c:\windows\sysvol\domain to c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
The File Replication Service may delete the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time.
Files can be saved from deletion by copying them out of c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying
the files into c:\windows\sysvol\domain may lead to name conflicts if the files already exist
on some other replicating partner.
In some cases, the File Replication Service may copy a file
from c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into c:\windows\sysvol\domain instead of replicating the file from some other
replicating partner.
Space can be recovered at any time by deleting the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
NtFrs
4/6/2015 3:25:32 PM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC2 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
NtFrs
4/3/2015 10:17:06 AM
Warning 13567
File Replication Service has detected and suppressed an average of 15 or more file updates
every hour for the last 3 hours because the updates did not change the contents of
the file. The tracking records in FRS debug logs will have the filename and event time
for the suppressed updates. The tracking records have the date and time followed by :T:
as their prefix. Updates that do not change the content of the file are suppressed to prevent
unnecessary replication traffic. Following are common examples of updates that do not
change the contents of the file.
[1] Overwriting a file with a copy of the same file.
[2] Setting the same ACLs on a file multiple times.
[3] Restoring an identical copy of the file over an existing one.
Suppression of updates can be disabled by running regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs, Parameters,
and create or update the value "Suppress Identical Updates To Files" to 0 (Default is 1) to force
identical updates to replicate.
NtFrs
4/2/2015 6:28:57 PM
Warning 13567
File Replication Service has detected and suppressed an average of 15 or more file updates
every hour for the last 3 hours because the updates did not change the contents of
the file. The tracking records in FRS debug logs will have the filename and event time
for the suppressed updates. The tracking records have the date and time followed by :T:
as their prefix. Updates that do not change the content of the file are suppressed to prevent
unnecessary replication traffic. Following are common examples of updates that do not
change the contents of the file.
[1] Overwriting a file with a copy of the same file.
[2] Setting the same ACLs on a file multiple times.
[3] Restoring an identical copy of the file over an existing one.
Suppression of updates can be disabled by running regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs, Parameters,
and create or update the value "Suppress Identical Updates To Files" to 0 (Default is 1) to force
identical updates to replicate.
NtFrs
4/2/2015 4:10:11 PM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC2 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
NtFrs
4/2/2015 3:56:38 PM
Warning 13520
The File Replication Service moved the preexisting files in c:\windows\sysvol\domain to c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
The File Replication Service may delete the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time.
Files can be saved from deletion by copying them out of c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying
the files into c:\windows\sysvol\domain may lead to name conflicts if the files already exist
on some other replicating partner.
In some cases, the File Replication Service may copy a file
from c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into c:\windows\sysvol\domain instead of replicating the file from some other
replicating partner.
Space can be recovered at any time by deleting the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
NtFrs
4/2/2015 3:56:37 PM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC2 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
WARNING: Found Event ID 13508 errors without trailing 13509 ... see above for (up to) the 3 latest entries!
......... failed 9
Checking for errors in Directory Service Event Log .... passed
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size... passed
Checking Overall Disk Space and SYSVOL structure (note: integrity is not checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ...
ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
4416: 904: S0: 08:00:40> :SR: Cmd 003f5d40, CxtG 6af17002, WS ERROR_ACCESS_DENIED, To
DC1.domain.local Len: (368) [SndFail - Send Penalty]
ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
4416: 877: S0: 08:07:51> :SR: Cmd 003f5d40, CxtG 6af17002, WS ERROR_ACCESS_DENIED, To
DC1.domain.local Len: (368) [SndFail - rpc call]
ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
4416: 904: S0: 08:07:51> :SR: Cmd 003f5d40, CxtG 6af17002, WS ERROR_ACCESS_DENIED, To
DC1.domain.local Len: (368) [SndFail - Send Penalty]
ERROR on NtFrs_0004.log : "EPT_S_NOT_REGISTERED(This may indicate that DNS returns the IP address of the wrong computer. Check DNS records being returned, Check if FRS is currently running on the target server. Check if Ntfrs is registered with
the End-Point-Mapper on target server!)" : <SndCsMain:
300: 883: S0: 15:25:44> ++ ERROR - EXCEPTION (000006d9) :
WStatus: EPT_S_NOT_REGISTERED
ERROR on NtFrs_0004.log : "EPT_S_NOT_REGISTERED(This may indicate that DNS returns the IP address of the wrong computer. Check DNS records being returned, Check if FRS is currently running on the target server. Check if Ntfrs is registered with
the End-Point-Mapper on target server!)" : <SndCsMain:
300: 884: S0: 15:25:44> :SR: Cmd 002a3060, CxtG e2bb412a, WS EPT_S_NOT_REGISTERED, To
DC3.domain.local Len: (366) [SndFail - rpc exception]
ERROR on NtFrs_0004.log : "EPT_S_NOT_REGISTERED(This may indicate that DNS returns the IP address of the wrong computer. Check DNS records being returned, Check if FRS is currently running on the target server. Check if Ntfrs is registered with
the End-Point-Mapper on target server!)" : <SndCsMain:
300: 904: S0: 15:25:44> :SR: Cmd 002a3060, CxtG e2bb412a, WS EPT_S_NOT_REGISTERED, To
DC3.domain.local Len: (366) [SndFail - Send Penalty]
ERROR on NtFrs_0003.log : "RPC_S_CALL_FAILED_DNE(Indicates RPC Session was established to target, but there was a failure to send RPC call package. Check for Networking problems!)" : <SndCsMain:
1312: 883: S0: 10:19:22> ++ ERROR - EXCEPTION (000006bf) :
WStatus: RPC_S_CALL_FAILED_DNE
ERROR on NtFrs_0003.log : "RPC_S_CALL_FAILED_DNE(Indicates RPC Session was established to target, but there was a failure to send RPC call package. Check for Networking problems!)" : <SndCsMain:
1312: 884: S0: 10:19:22> :SR: Cmd 06bf9240, CxtG e2bb412a, WS RPC_S_CALL_FAILED_DNE, To
DC3.domain.local Len: (366) [SndFail - rpc exception]
ERROR on NtFrs_0003.log : "RPC_S_CALL_FAILED_DNE(Indicates RPC Session was established to target, but there was a failure to send RPC call package. Check for Networking problems!)" : <SndCsMain:
1312: 904: S0: 10:19:22> :SR: Cmd 06bf9240, CxtG e2bb412a, WS RPC_S_CALL_FAILED_DNE, To
DC3.domain.local Len: (366) [SndFail - Send Penalty]
Found 2230 ERROR_ACCESS_DENIED error(s)! Latest ones (up to 3) listed above
Found 6 EPT_S_NOT_REGISTERED error(s)! Latest ones (up to 3) listed above
Found 3 RPC_S_CALL_FAILED_DNE error(s)! Latest ones (up to 3) listed above
......... failed with 2239 error entries
Checking NtFrs Service (and dependent services) state...
ERROR : Cannot access SYSVOL share on DC2
ERROR : Cannot access NETLOGON share on DC2
......... failed 2
Checking NtFrs related Registry Keys for possible problems...
SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\SysvolReady = 0 :: ERROR: SysvolReady is not set to 1 :: SYSVOL is likely not Sharing! This key should NOT be changed manually but this should be addressed! See article KB.327781 (How to Troubleshoot
Missing SYSVOL and NETLOGON Shares on Windows Server) for further information!
failed with 1 error(s) and 0 warning(s)
Checking Repadmin Showreps for errors...passed
Final Result = failed with 2251 error(s)
DC3:
FRSDiag v1.7 on 4/8/2015 8:10:49 AM
.\DC3 on 2015-04-08 at 8.10.49 AM
Checking for errors/warnings in FRS Event Log ....
NtFrs
4/7/2015 4:52:26 PM
Warning 13508
The File Replication Service is having trouble enabling replication
from DC1 to DC3 for c:\windows\sysvol\domain using the DNS name DC1.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC1.domain.local from this computer.
[2] FRS is not running on DC1.domain.local.
[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.
NtFrs
4/7/2015 4:33:35 PM
Warning 13508
The File Replication Service is having trouble enabling replication
from DC2 to DC3 for c:\windows\sysvol\domain using the DNS name DC2.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC2.domain.local from this computer.
[2] FRS is not running on DC2.domain.local.
[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.
NtFrs
4/6/2015 3:27:45 PM
Warning 13508
The File Replication Service is having trouble enabling replication
from DC1 to DC3 for c:\windows\sysvol\domain using the DNS name DC1.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC1.domain.local from this computer.
[2] FRS is not running on DC1.domain.local.
[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.
NtFrs
4/6/2015 3:26:03 PM
Warning 13520
The File Replication Service moved the preexisting files in c:\windows\sysvol\domain to c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
The File Replication Service may delete the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time.
Files can be saved from deletion by copying them out of c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying
the files into c:\windows\sysvol\domain may lead to name conflicts if the files already exist
on some other replicating partner.
In some cases, the File Replication Service may copy a file
from c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into c:\windows\sysvol\domain instead of replicating the file from some other
replicating partner.
Space can be recovered at any time by deleting the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
NtFrs
4/6/2015 3:26:03 PM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC3 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
NtFrs
4/6/2015 1:42:46 PM
Warning 13518
The File Replication Service did not grant the user "itadmin" access to the
API "Get Internal Information".
Permissions for "Get Internal Information" can be changed by running regedit.
Click on Start, Run, and type regedit.
Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs, Parameters,
Access Checks, and highlight "Get Internal Information".
Click on the toolbar option Security and then Permissions...
Access checks can be disabled for "Get Internal Information". Double click on "Access checks are [Enabled or Disabled]" and
change the string to Disabled.
NtFrs
4/3/2015 10:24:13 AM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC3 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
NtFrs
4/3/2015 10:20:13 AM
Warning 13520
The File Replication Service moved the preexisting files in c:\windows\sysvol\domain to c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
The File Replication Service may delete the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time.
Files can be saved from deletion by copying them out of c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying
the files into c:\windows\sysvol\domain may lead to name conflicts if the files already exist
on some other replicating partner.
In some cases, the File Replication Service may copy a file
from c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into c:\windows\sysvol\domain instead of replicating the file from some other
replicating partner.
Space can be recovered at any time by deleting the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
NtFrs
4/3/2015 10:20:13 AM
Warning 13565
File Replication Service is initializing the system volume with data from another
domain controller. Computer DC3 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 initialization 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,
the availability of other domain controllers, and the replication
interval between domain controllers.
NtFrs
4/2/2015 5:30:36 PM
Warning 13567
File Replication Service has detected and suppressed an average of 15 or more file updates
every hour for the last 3 hours because the updates did not change the contents of
the file. The tracking records in FRS debug logs will have the filename and event time
for the suppressed updates. The tracking records have the date and time followed by :T:
as their prefix. Updates that do not change the content of the file are suppressed to prevent
unnecessary replication traffic. Following are common examples of updates that do not
change the contents of the file.
[1] Overwriting a file with a copy of the same file.
[2] Setting the same ACLs on a file multiple times.
[3] Restoring an identical copy of the file over an existing one.
Suppression of updates can be disabled by running regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, NtFrs, Parameters,
and create or update the value "Suppress Identical Updates To Files" to 0 (Default is 1) to force
identical updates to replicate.
WARNING: Found Event ID 13508 errors without trailing 13509 ... see above for (up to) the 3 latest entries!
......... failed 8
Checking for errors in Directory Service Event Log .... passed
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size... passed
Checking Overall Disk Space and SYSVOL structure (note: integrity is not checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ...
ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
7060: 904: S0: 07:54:33> :SR: Cmd 63f84670, CxtG aac0c4ed, WS ERROR_ACCESS_DENIED, To
DC1.domain.local Len: (366) [SndFail - Send Penalty]
ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
288: 877: S0: 08:00:12> :SR: Cmd 63f947f0, CxtG aac0c4ed, WS ERROR_ACCESS_DENIED, To
DC1.domain.local Len: (366) [SndFail - rpc call]
ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
288: 904: S0: 08:00:13> :SR: Cmd 63f947f0, CxtG aac0c4ed, WS ERROR_ACCESS_DENIED, To
DC1.domain.local Len: (366) [SndFail - Send Penalty]
Found 1786 ERROR_ACCESS_DENIED error(s)! Latest ones (up to 3) listed above
......... failed with 1786 error entries
Checking NtFrs Service (and dependent services) state...
ERROR : Cannot access SYSVOL share on DC3
ERROR : Cannot access NETLOGON share on DC3
......... failed 2
Checking NtFrs related Registry Keys for possible problems...
SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\SysvolReady = 0 :: ERROR: SysvolReady is not set to 1 :: SYSVOL is likely not Sharing! This key should NOT be changed manually but this should be addressed! See article KB.327781 (How to Troubleshoot
Missing SYSVOL and NETLOGON Shares on Windows Server) for further information!
failed with 1 error(s) and 0 warning(s)
Checking Repadmin Showreps for errors...passed
Final Result = failed with 1797 error(s)
Keep in mind that this is after I tried an authoritative restore. -
Netlogon & Sysvol not found in new 2008R2 DC
I have recently added 2008R2 server in my existing environment. Earlier, I had 2 DC's. But, Netlogon & Sysvol folders not showing in this new DC. Although, DNS & AD replication is working fine.
Thanks,
SandeshHi,
They are not getting shared out & not getting through net share as well..
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
* Verifying that the local machine Sportz2, is a Directory Server.
Home Server = Sportz2
* Connecting to directory service on server Sportz2.
* Identified AD Forest.
Collecting AD specific global data
* Collecting site info.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=sportzinteractive,DC=com,LDAP_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=sportzinteractive,DC=com
Getting ISTG and options for the site
* Identifying all servers.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=sportzinteractive,DC=com,LDAP_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=SPORTZ,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=sportzinteractive,DC=com
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=GAME,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=sportzinteractive,DC=com
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=SPORTZ2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=sportzinteractive,DC=com
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
* Identifying all NC cross-refs.
* Found 3 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SPORTZ2
Starting test: Connectivity
* Active Directory LDAP Services Check
Determining IP4 connectivity
* Active Directory RPC Services Check
......................... SPORTZ2 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SPORTZ2
Starting test: Advertising
Warning: DsGetDcName returned information for
\\SPORTZ.sportzinteractive.com, when we were trying to reach SPORTZ2.
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
......................... SPORTZ2 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.
A warning event occurred. EventID: 0x800034C4
Time Generated: 11/07/2014 16:39:52
Event String:
The File Replication Service is having trouble enabling replication from SPORTZ.sportzinteractive.com to SPORTZ2 for c:\windows\sysvol\domain using the DNS name SPORTZ.sportzinteractive.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 SPORTZ.sportzinteractive.com from this computer.
[2] FRS is not running on SPORTZ.sportzinteractive.com.
[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.
A warning event occurred. EventID: 0x800034C4
Time Generated: 11/07/2014 16:47:52
Event String:
The File Replication Service is having trouble enabling replication from GAME to SPORTZ2 for c:\windows\sysvol\domain using the DNS name GAME.sportzinteractive.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 GAME.sportzinteractive.com from this computer.
[2] FRS is not running on GAME.sportzinteractive.com.
[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.
A warning event occurred. EventID: 0x800034C4
Time Generated: 11/07/2014 16:47:52
Event String:
The File Replication Service is having trouble enabling replication from SPORTZ to SPORTZ2 for c:\windows\sysvol\domain using the DNS name SPORTZ.sportzinteractive.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 SPORTZ.sportzinteractive.com from this computer.
[2] FRS is not running on SPORTZ.sportzinteractive.com.
[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.
......................... SPORTZ2 passed test FrsEvent
Starting test: DFSREvent
The DFS Replication Event Log.
Skip the test because the server is running FRS.
......................... SPORTZ2 passed 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.
......................... SPORTZ2 passed test SysVolCheck
Starting test: KccEvent
* The KCC Event log test
Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
......................... SPORTZ2 passed test KccEvent
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=SPORTZ,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=sportzinteractive,DC=com
Role Domain Owner = CN=NTDS Settings,CN=SPORTZ,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=sportzinteractive,DC=com
Role PDC Owner = CN=NTDS Settings,CN=SPORTZ,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=sportzinteractive,DC=com
Role Rid Owner = CN=NTDS Settings,CN=SPORTZ,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=sportzinteractive,DC=com
Role Infrastructure Update Owner = CN=NTDS Settings,CN=SPORTZ,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=sportzinteractive,DC=com
......................... SPORTZ2 passed test KnowsOfRoleHolders
Starting test: MachineAccount
Checking machine account for DC SPORTZ2 on DC SPORTZ2.
* SPN found :LDAP/Sportz2.sportzinteractive.com/sportzinteractive.com
* SPN found :LDAP/Sportz2.sportzinteractive.com
* SPN found :LDAP/SPORTZ2
* SPN found :LDAP/Sportz2.sportzinteractive.com/SPORTZINTERACTI
* SPN found :LDAP/77f37d19-ffc2-4dbe-b7c3-7da2a35d444f._msdcs.sportzinteractive.com
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/77f37d19-ffc2-4dbe-b7c3-7da2a35d444f/sportzinteractive.com
* SPN found :HOST/Sportz2.sportzinteractive.com/sportzinteractive.com
* SPN found :HOST/Sportz2.sportzinteractive.com
* SPN found :HOST/SPORTZ2
* SPN found :HOST/Sportz2.sportzinteractive.com/SPORTZINTERACTI
* SPN found :GC/Sportz2.sportzinteractive.com/sportzinteractive.com
......................... SPORTZ2 passed test MachineAccount
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC SPORTZ2.
* Security Permissions Check for
DC=ForestDnsZones,DC=sportzinteractive,DC=com
(NDNC,Version 3)
* Security Permissions Check for
DC=DomainDnsZones,DC=sportzinteractive,DC=com
(NDNC,Version 3)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=sportzinteractive,DC=com
(Schema,Version 3)
Error SPORTZINTERACTI\Enterprise Read-only Domain Controllers doesn't
have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
CN=Schema,CN=Configuration,DC=sportzinteractive,DC=com
* Security Permissions Check for
CN=Configuration,DC=sportzinteractive,DC=com
(Configuration,Version 3)
* Security Permissions Check for
DC=sportzinteractive,DC=com
(Domain,Version 3)
......................... SPORTZ2 failed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Unable to connect to the NETLOGON share! (\\SPORTZ2\netlogon)
[SPORTZ2] An net use or LsaPolicy operation failed with error 67,
The network name cannot be found..
......................... SPORTZ2 failed test NetLogons
Starting test: ObjectsReplicated
SPORTZ2 is in domain DC=sportzinteractive,DC=com
Checking for CN=SPORTZ2,OU=Domain Controllers,DC=sportzinteractive,DC=com in domain DC=sportzinteractive,DC=com on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=SPORTZ2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=sportzinteractive,DC=com in domain CN=Configuration,DC=sportzinteractive,DC=com on 1 servers
Object is up-to-date on all servers.
......................... SPORTZ2 passed test ObjectsReplicated
Test omitted by user request: OutboundSecureChannels
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=ForestDnsZones,DC=sportzinteractive,DC=com
Latency information for 10 entries in the vector were ignored.
10 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=DomainDnsZones,DC=sportzinteractive,DC=com
Latency information for 10 entries in the vector were ignored.
10 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Schema,CN=Configuration,DC=sportzinteractive,DC=com
Latency information for 13 entries in the vector were ignored.
13 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Configuration,DC=sportzinteractive,DC=com
Latency information for 13 entries in the vector were ignored.
13 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=sportzinteractive,DC=com
Latency information for 10 entries in the vector were ignored.
10 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
* Replication Site Latency Check
......................... SPORTZ2 passed test Replications
Starting test: RidManager
* Available RID Pool for the Domain is 8603 to 1073741823
* SPORTZ.sportzinteractive.com is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 8103 to 8602
* rIDPreviousAllocationPool is 8103 to 8602
* rIDNextRID: 8107
......................... SPORTZ2 passed test RidManager
Starting test: Services
* Checking Service: EventSystem
* Checking Service: RpcSs
* Checking Service: NTDS
* Checking Service: DnsCache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: w32time
* Checking Service: NETLOGON
......................... SPORTZ2 passed test Services
Starting test: SystemLog
* The System Event log test
An error event occurred. EventID: 0x00000457
Time Generated: 11/07/2014 17:27:16
Event String:
Driver HP LaserJet M1530 MFP Series PCL 6 required for printer NPID5BDFA (HP LaserJet M1536dnf MFP) is unknown. Contact the administrator to install the driver before you log in again.
An error event occurred. EventID: 0x00000457
Time Generated: 11/07/2014 17:27:17
Event String:
Driver HP LaserJet 3050 Series PCL 6 required for printer HP LaserJet 3050 Series PCL 6 is unknown. Contact the administrator to install the driver before you log in again.
An error event occurred. EventID: 0x00000457
Time Generated: 11/07/2014 17:27:21
Event String:
Driver Send to Microsoft OneNote 15 Driver required for printer Send To OneNote 2013 is unknown. Contact the administrator to install the driver before you log in again.
......................... SPORTZ2 failed test SystemLog
Test omitted by user request: Topology
Test omitted by user request: VerifyEnterpriseReferences
Starting test: VerifyReferences
The system object reference (serverReference)
CN=SPORTZ2,OU=Domain Controllers,DC=sportzinteractive,DC=com and
backlink on
CN=SPORTZ2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=sportzinteractive,DC=com
are correct.
The system object reference (serverReferenceBL)
CN=SPORTZ2,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=sportzinteractive,DC=com
and backlink on
CN=NTDS Settings,CN=SPORTZ2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=sportzinteractive,DC=com
are correct.
The system object reference (frsComputerReferenceBL)
CN=SPORTZ2,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=sportzinteractive,DC=com
and backlink on
CN=SPORTZ2,OU=Domain Controllers,DC=sportzinteractive,DC=com are
correct.
......................... SPORTZ2 passed test VerifyReferences
Test omitted by user request: VerifyReplicas
Test omitted by user request: DNS
Test omitted by user request: DNS
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : sportzinteractive
Starting test: CheckSDRefDom
......................... sportzinteractive passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... sportzinteractive passed test
CrossRefValidation
Running enterprise tests on : sportzinteractive.com
Test omitted by user request: DNS
Test omitted by user request: DNS
Starting test: LocatorCheck
GC Name: \\SPORTZ.sportzinteractive.com
Locator Flags: 0xe00031fd
PDC Name: \\SPORTZ.sportzinteractive.com
Locator Flags: 0xe00031fd
Time Server Name: \\GAME.sportzinteractive.com
Locator Flags: 0xe00031fc
Preferred Time Server Name: \\SPORTZ.sportzinteractive.com
Locator Flags: 0xe00031fd
KDC Name: \\GAME.sportzinteractive.com
Locator Flags: 0xe00031fc
......................... sportzinteractive.com passed test
LocatorCheck
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... sportzinteractive.com passed test Intersite
Repadmin: running command /showrepl against full DC SPORTZ.sportzinteractive.com
Default-First-Site-Name\SPORTZ
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: e52c0e2a-8fa9-4014-92bb-285a560804b9
DSA invocationID: 5492e47d-913b-4038-a39a-b2263da484c2
==== INBOUND NEIGHBORS ======================================
DC=sportzinteractive,DC=com
Default-First-Site-Name\SPORTZ2 via RPC
DSA object GUID: 77f37d19-ffc2-4dbe-b7c3-7da2a35d444f
Last attempt @ 2014-11-07 17:39:03 was successful.
Default-First-Site-Name\GAME via RPC
DSA object GUID: a16f4055-cd68-4cbc-b5d3-33efe4e9d3ee
Last attempt @ 2014-11-07 17:50:10 was successful.
CN=Configuration,DC=sportzinteractive,DC=com
Default-First-Site-Name\SPORTZ2 via RPC
DSA object GUID: 77f37d19-ffc2-4dbe-b7c3-7da2a35d444f
Last attempt @ 2014-11-07 17:50:07 was successful.
Default-First-Site-Name\GAME via RPC
DSA object GUID: a16f4055-cd68-4cbc-b5d3-33efe4e9d3ee
Last attempt @ 2014-11-07 17:50:19 was successful.
CN=Schema,CN=Configuration,DC=sportzinteractive,DC=com
Default-First-Site-Name\GAME via RPC
DSA object GUID: a16f4055-cd68-4cbc-b5d3-33efe4e9d3ee
Last attempt @ 2014-11-07 17:22:24 was successful.
Default-First-Site-Name\SPORTZ2 via RPC
DSA object GUID: 77f37d19-ffc2-4dbe-b7c3-7da2a35d444f
Last attempt @ 2014-11-07 17:22:24 was successful.
DC=DomainDnsZones,DC=sportzinteractive,DC=com
Default-First-Site-Name\GAME via RPC
DSA object GUID: a16f4055-cd68-4cbc-b5d3-33efe4e9d3ee
Last attempt @ 2014-11-07 17:26:11 was successful.
Default-First-Site-Name\SPORTZ2 via RPC
DSA object GUID: 77f37d19-ffc2-4dbe-b7c3-7da2a35d444f
Last attempt @ 2014-11-07 17:26:14 was successful.
DC=ForestDnsZones,DC=sportzinteractive,DC=com
Default-First-Site-Name\GAME via RPC
DSA object GUID: a16f4055-cd68-4cbc-b5d3-33efe4e9d3ee
Last attempt @ 2014-11-07 17:22:24 was successful.
Default-First-Site-Name\SPORTZ2 via RPC
DSA object GUID: 77f37d19-ffc2-4dbe-b7c3-7da2a35d444f
Last attempt @ 2014-11-07 17:22:24 was successful.
Repadmin: running command /showrepl against full DC GAME.sportzinteractive.com
Default-First-Site-Name\GAME
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: a16f4055-cd68-4cbc-b5d3-33efe4e9d3ee
DSA invocationID: 247c3b4c-b394-4487-b783-99816f43300b
==== INBOUND NEIGHBORS ======================================
DC=sportzinteractive,DC=com
Default-First-Site-Name\SPORTZ2 via RPC
DSA object GUID: 77f37d19-ffc2-4dbe-b7c3-7da2a35d444f
Last attempt @ 2014-11-07 17:39:05 was successful.
Default-First-Site-Name\SPORTZ via RPC
DSA object GUID: e52c0e2a-8fa9-4014-92bb-285a560804b9
Last attempt @ 2014-11-07 17:50:40 was successful.
CN=Configuration,DC=sportzinteractive,DC=com
Default-First-Site-Name\SPORTZ2 via RPC
DSA object GUID: 77f37d19-ffc2-4dbe-b7c3-7da2a35d444f
Last attempt @ 2014-11-07 17:50:04 was successful.
Default-First-Site-Name\SPORTZ via RPC
DSA object GUID: e52c0e2a-8fa9-4014-92bb-285a560804b9
Last attempt @ 2014-11-07 17:50:29 was successful.
CN=Schema,CN=Configuration,DC=sportzinteractive,DC=com
Default-First-Site-Name\SPORTZ via RPC
DSA object GUID: e52c0e2a-8fa9-4014-92bb-285a560804b9
Last attempt @ 2014-11-07 17:19:27 was successful.
Default-First-Site-Name\SPORTZ2 via RPC
DSA object GUID: 77f37d19-ffc2-4dbe-b7c3-7da2a35d444f
Last attempt @ 2014-11-07 17:19:27 was successful.
DC=DomainDnsZones,DC=sportzinteractive,DC=com
Default-First-Site-Name\SPORTZ via RPC
DSA object GUID: e52c0e2a-8fa9-4014-92bb-285a560804b9
Last attempt @ 2014-11-07 17:25:53 was successful.
Default-First-Site-Name\SPORTZ2 via RPC
DSA object GUID: 77f37d19-ffc2-4dbe-b7c3-7da2a35d444f
Last attempt @ 2014-11-07 17:26:11 was successful.
DC=ForestDnsZones,DC=sportzinteractive,DC=com
Default-First-Site-Name\SPORTZ via RPC
DSA object GUID: e52c0e2a-8fa9-4014-92bb-285a560804b9
Last attempt @ 2014-11-07 17:19:27 was successful.
Default-First-Site-Name\SPORTZ2 via RPC
DSA object GUID: 77f37d19-ffc2-4dbe-b7c3-7da2a35d444f
Last attempt @ 2014-11-07 17:19:27 was successful.
Repadmin: running command /showrepl against full DC Sportz2.sportzinteractive.com
Default-First-Site-Name\SPORTZ2
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 77f37d19-ffc2-4dbe-b7c3-7da2a35d444f
DSA invocationID: c684c6af-e0ed-4e36-bcfc-d5d84da4e51d
==== INBOUND NEIGHBORS ======================================
DC=sportzinteractive,DC=com
Default-First-Site-Name\GAME via RPC
DSA object GUID: a16f4055-cd68-4cbc-b5d3-33efe4e9d3ee
Last attempt @ 2014-11-07 17:50:07 was successful.
Default-First-Site-Name\SPORTZ via RPC
DSA object GUID: e52c0e2a-8fa9-4014-92bb-285a560804b9
Last attempt @ 2014-11-07 17:50:43 was successful.
CN=Configuration,DC=sportzinteractive,DC=com
Default-First-Site-Name\GAME via RPC
DSA object GUID: a16f4055-cd68-4cbc-b5d3-33efe4e9d3ee
Last attempt @ 2014-11-07 17:50:22 was successful.
Default-First-Site-Name\SPORTZ via RPC
DSA object GUID: e52c0e2a-8fa9-4014-92bb-285a560804b9
Last attempt @ 2014-11-07 17:50:26 was successful.
CN=Schema,CN=Configuration,DC=sportzinteractive,DC=com
Default-First-Site-Name\SPORTZ via RPC
DSA object GUID: e52c0e2a-8fa9-4014-92bb-285a560804b9
Last attempt @ 2014-11-07 17:28:58 was successful.
Default-First-Site-Name\GAME via RPC
DSA object GUID: a16f4055-cd68-4cbc-b5d3-33efe4e9d3ee
Last attempt @ 2014-11-07 17:28:59 was successful.
DC=DomainDnsZones,DC=sportzinteractive,DC=com
Default-First-Site-Name\SPORTZ via RPC
DSA object GUID: e52c0e2a-8fa9-4014-92bb-285a560804b9
Last attempt @ 2014-11-07 17:28:59 was successful.
Default-First-Site-Name\GAME via RPC
DSA object GUID: a16f4055-cd68-4cbc-b5d3-33efe4e9d3ee
Last attempt @ 2014-11-07 17:28:59 was successful.
DC=ForestDnsZones,DC=sportzinteractive,DC=com
Default-First-Site-Name\SPORTZ via RPC
DSA object GUID: e52c0e2a-8fa9-4014-92bb-285a560804b9
Last attempt @ 2014-11-07 17:28:59 was successful.
Default-First-Site-Name\GAME via RPC
DSA object GUID: a16f4055-cd68-4cbc-b5d3-33efe4e9d3ee
Last attempt @ 2014-11-07 17:28:59 was successful. -
Sysvol share disapears repeatedly
I have been having an issue in our main production domain where the Sysvol shares will disappear on 2 of our 3 DCs. The files still exists but Sysvol and Netlogon will no longer be shared. I have run a force sync on a couple of occasions now as listed
here https://support.microsoft.com/kb/2218556?wa=wsignin1.0 However, this fixes the issue for about a day. When I check back in on the DCS they have a replication state of 2 or initial sync. What is frustrating is that all replication succeeds and appears
normal when using DCDiag and repadmin. However I am unable to even open a GPO on any DC in that domain. It gives the error Network Name not found. I have been looking this over for awhile and would really like to know if anyone has experienced anything similar
or has suggestions on what to check next.D2 and D4 is used with FRS service. I mentioned them because I did not know what your operating systems are. Since you are using 2012 Windows Sever, the SYSVOL replication is done using DFSR. So in that case it is different. Down times will not be big. The
first time I did it, I planned to do it on weekend, it took 1 hour or less though. But who knows, it is wise to be on the safe side. Look at the below articles:
How to force an authoritative and non-authoritative synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS)
SYSVOL and Group Policy out of Sync
on Server 2012 R2 DCs using DFSR
Regards.
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers? -
Windows Blue Screen Error Message Appears As Soon As IPod Connected
Everytime I connect my IPod to my computer, I get the Windows Blue Screen error message. Thought it was the cable, so plugged cable in by itself. No problem. Uninstalled IPod and ITunes software and then plugged in IPod, still got the Blue Screen. The Blue Screen says something about "recent plugged in device problem". It is not the cable, it must be the IPod. Did not have this problem when I bought it. Tried it on labtop and get the same error message. I can't do updater or anything that requires me to plug the IPod into a computer because the Blue Screen appears immediately. When I unplug, the Blue Screen remains and locks up the computer so I have to restart each time. I have tried everything I can think of. Please help.
Hi Mike thank you for replying,
I am not able to start the computer in safe mode, safe mode with networking, last good known configuration etc, Each time it quickly blue screens and restarts about two secs into the process.
I was unable to try a clean OS install from the disk as it gave the blue screen error shown in the original post. The same thing happened when I tried to use the repair option on the XP home disc. So i can't get into the computer at all to start diagnosing the fault, the only clue I have is the error message, and after searching the internet I haven't found much enlightenment from that yet.
If you can help me out or suggest where to search it would be much appreciated.
Thx -
It started yesterday when i was listening to itunes when all of a sudden the music stopped playing and i had to hold down the power button to shut it down and reboot, and then, when i logged back in, the error sound played, and then finder opened up, but the window was grayed out like i had another app selected, bu i didn't, so i tried to open up itunes and the icon started bouncing and then it stopped midbounce and i had to reboot again because finder wasnt responding. now when i log in, the error sound plays, and finder immediately stops working and then i have to reboot again because i cant click anything and i cant properly relaunch finder. please help
Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, or by a peripheral device.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including Wi-Fi on certain iMacs. The next normal boot may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test. -
If I use an adapter (female VGA to mini-DVI) for my iMac 10.4.11 OSX, I also need a cable. Should that cable be female VGA to male VGA?
Permanent vertical lines have appeared on my display, and connecting to another display (monitor) requires a cable and adapter. I want to be sure I am purchasing the correct cable for the Apple adapter.What made me think I need to format if I upgrade the OS?
I just presumed so really.
What made me think I need to constantly format computer with my problem?
Well, after many attempts to repair the drive, which fails, cannot even reach the log in screen, I am left with no other choice?
And also, I have to note now, System Preferences keeps crashing without reason, it either takes ages to load, just by clicking it to open, or clicking something within it, or it just crashes.
And temporarily, it freezes the computer totally, with no response.
Seriously, am I missing a system file or something? Anyone experienced this problem before?
My computer is literally a blank computer right now, installed VLC and Shades, updated Adobe Flash Player, installed Skype and Adium. I would say Growl from Adium caused it, but it has happened prior to Skype and Adium. Any ideas anyone?
Thanks,
From Lelouch -
"Shut Down your Mac" window appear
Hello, just now window with message that I need to turn my Mac was appeared, there was instruction that I need to hold power button for a few seconds. I made it and recived error report:
[quote]
Interval Since Last Panic Report: 5436007 sec
Panics Since Last Report: 1
Anonymous UUID: 3B48A598-F87D-45DC-9C54-E8FCEC514F82
Sun Feb 10 22:39:29 2013
panic(cpu 3 caller 0xffffff80002c4794): Kernel trap at 0xffffff7f80e10b23, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x000000040002bdeb, CR3: 0x000000006e3b302f, CR4: 0x00000000000606e0
RAX: 0x000000040002bd93, RBX: 0xffffff8019f9fd10, RCX: 0x000000040002bd93, RDX: 0xffffff800d464d10
RSP: 0xffffff807f85bae0, RBP: 0xffffff807f85baf0, RSI: 0xffffff8019f9fd10, RDI: 0xffffff800d464d10
R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0xffffff800e058400, R11: 0xffffff7f80db6c30
R12: 0xffffff8019f9fd10, R13: 0xffffff800e058400, R14: 0xffffff800d53bc00, R15: 0xffffff800e058400
RFL: 0x0000000000010203, RIP: 0xffffff7f80e10b23, CS: 0x0000000000000008, SS: 0x0000000000000010
CR2: 0x000000040002bdeb, Error code: 0x0000000000000000, Faulting CPU: 0x3
Backtrace (CPU 3), Frame : Return Address
0xffffff807f85b790 : 0xffffff8000220792
0xffffff807f85b810 : 0xffffff80002c4794
0xffffff807f85b9c0 : 0xffffff80002da55d
0xffffff807f85b9e0 : 0xffffff7f80e10b23
0xffffff807f85baf0 : 0xffffff7f80e0d2f2
0xffffff807f85bb10 : 0xffffff7f80e0e5df
0xffffff807f85bb40 : 0xffffff800063dd21
0xffffff807f85bba0 : 0xffffff7f80e0bfb8
0xffffff807f85bbe0 : 0xffffff800063baeb
0xffffff807f85bc20 : 0xffffff7f80e0bf16
0xffffff807f85bc40 : 0xffffff8000656fbb
0xffffff807f85bd80 : 0xffffff80002a3f08
0xffffff807f85be80 : 0xffffff8000223096
0xffffff807f85beb0 : 0xffffff80002148a9
0xffffff807f85bf10 : 0xffffff800021bbd8
0xffffff807f85bf70 : 0xffffff80002aef10
0xffffff807f85bfb0 : 0xffffff80002daec3
Kernel Extensions in backtrace:
com.apple.iokit.IOAudioFamily(1.8.6f18)[8D690452-BF17-3DA0-BCAD-F1BCF1495926]@0 xffffff7f80e03000->0xffffff7f80e2ffff
dependency: com.apple.kext.OSvKernDSPLib(1.3)[CF50CA5A-4AF6-3E28-B84B-9619535445E7]@0xfffff f7f80dfd000
BSD process name corresponding to current thread: coreaudiod
Mac OS version:
11G63
Kernel version:
Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64
Kernel UUID: FF3BB088-60A4-349C-92EA-CA649C698CE5
System model name: iMac12,1 (Mac-942B5BF58194151B)
System uptime in nanoseconds: 182546829266205
last loaded kext at 165547627665565: com.apple.filesystems.msdosfs 1.7.1 (addr 0xffffff7f80798000, size 57344)
last unloaded kext at 166466121855806: com.apple.driver.AppleUSBCDC 4.1.22 (addr 0xffffff7f80795000, size 12288)
loaded kexts:
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AppleBluetoothMultitouch 70.12
com.apple.driver.IOBluetoothA2DPAudioDriver 4.0.8f17
com.apple.driver.IOBluetoothSCOAudioDriver 4.0.8f17
com.apple.driver.AudioAUUC 1.59
com.apple.driver.AGPM 100.12.75
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleMikeyHIDDriver 122
com.apple.driver.AppleHDA 2.2.5a5
com.apple.driver.AppleMikeyDriver 2.2.5a5
com.apple.driver.AppleUpstreamUserClient 3.5.9
com.apple.kext.ATIFramebuffer 7.3.2
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.driver.AppleSMCPDRC 5.0.0d8
com.apple.iokit.IOBluetoothSerialManager 4.0.8f17
com.apple.driver.AppleSMCLMU 2.0.1d2
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AudioIPCDriver 1.2.3
com.apple.driver.ApplePolicyControl 3.1.33
com.apple.driver.ACPI_SMC_PlatformPlugin 5.0.0d8
com.apple.driver.AppleLPC 1.6.0
com.apple.ATIRadeonX3000 7.3.2
com.apple.driver.AppleBacklight 170.2.2
com.apple.driver.AppleMCCSControl 1.0.33
com.apple.driver.AppleIntelHD3000Graphics 7.3.2
com.apple.driver.BroadcomUSBBluetoothHCIController 4.0.8f17
com.apple.iokit.SCSITaskUserClient 3.2.1
com.apple.driver.AppleUSBCardReader 3.0.6
com.apple.iokit.IOAHCISerialATAPI 2.0.3
com.apple.driver.AppleIRController 312
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 33
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.1.0
com.apple.driver.AppleUSBHub 5.1.0
com.apple.driver.AirPort.Atheros40 505.67.1
com.apple.iokit.AppleBCM5701Ethernet 3.2.4b8
com.apple.driver.AppleEFINVRAM 1.6.1
com.apple.driver.AppleFWOHCI 4.9.0
com.apple.driver.AppleAHCIPort 2.3.1
com.apple.driver.AppleUSBEHCI 5.1.0
com.apple.driver.AppleACPIButtons 1.5
com.apple.driver.AppleRTC 1.5
com.apple.driver.AppleHPET 1.7
com.apple.driver.AppleSMBIOS 1.9
com.apple.driver.AppleACPIEC 1.5
com.apple.driver.AppleAPIC 1.6
com.apple.driver.AppleIntelCPUPowerManagementClient 195.0.0
com.apple.nke.applicationfirewall 3.2.30
com.apple.security.quarantine 1.4
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 195.0.0
com.apple.driver.AppleBluetoothHIDKeyboard 160.7
com.apple.driver.AppleHIDKeyboard 160.7
com.apple.driver.AppleMultitouchDriver 231.4
com.apple.driver.IOBluetoothHIDDriver 4.0.8f17
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 2.2.5a5
com.apple.iokit.IOSurface 80.0.2
com.apple.iokit.IOSerialFamily 10.0.5
com.apple.iokit.IOFireWireIP 2.2.5
com.apple.iokit.IOAudioFamily 1.8.6fc18
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleHDAController 2.2.5a5
com.apple.iokit.IOHDAFamily 2.2.5a5
com.apple.driver.AppleSMC 3.1.3d10
com.apple.driver.IOPlatformPluginLegacy 5.0.0d8
com.apple.driver.AppleSMBusPCI 1.0.10d0
com.apple.driver.AppleGraphicsControl 3.1.33
com.apple.driver.IOPlatformPluginFamily 5.1.1d6
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.driver.AppleThunderboltEDMSink 1.1.8
com.apple.driver.AppleThunderboltEDMSource 1.1.8
com.apple.driver.AppleSMBusController 1.0.10d0
com.apple.kext.ATI6000Controller 7.3.2
com.apple.kext.ATISupport 7.3.2
com.apple.iokit.IONDRVSupport 2.3.4
com.apple.driver.AppleIntelSNBGraphicsFB 7.3.2
com.apple.iokit.IOGraphicsFamily 2.3.4
com.apple.driver.AppleThunderboltDPOutAdapter 1.8.5
com.apple.driver.AppleThunderboltDPInAdapter 1.8.5
com.apple.driver.AppleThunderboltDPAdapterFamily 1.8.5
com.apple.driver.AppleThunderboltPCIDownAdapter 1.2.5
com.apple.driver.AppleUSBBluetoothHCIController 4.0.8f17
com.apple.iokit.IOBluetoothFamily 4.0.8f17
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.2.1
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOSCSIBlockCommandsDevice 3.2.1
com.apple.iokit.IOUSBMassStorageClass 3.0.3
com.apple.iokit.IOSCSIArchitectureModelFamily 3.2.1
com.apple.iokit.IOUSBHIDDriver 5.0.0
com.apple.driver.AppleUSBMergeNub 5.1.0
com.apple.driver.AppleUSBComposite 5.0.0
com.apple.driver.AppleThunderboltNHI 1.6.0
com.apple.iokit.IOThunderboltFamily 2.0.3
com.apple.iokit.IOUSBUserClient 5.0.0
com.apple.iokit.IO80211Family 420.3
com.apple.iokit.IOEthernetAVBController 1.0.1b1
com.apple.iokit.IONetworkingFamily 2.1
com.apple.iokit.IOFireWireFamily 4.4.8
com.apple.iokit.IOAHCIFamily 2.0.8
com.apple.iokit.IOUSBFamily 5.1.0
com.apple.driver.AppleEFIRuntime 1.6.1
com.apple.iokit.IOHIDFamily 1.7.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 177.8
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 331.7
com.apple.iokit.IOStorageFamily 1.7.2
com.apple.driver.AppleKeyStore 28.18
com.apple.driver.AppleACPIPlatform 1.5
com.apple.iokit.IOPCIFamily 2.7
com.apple.iokit.IOACPIFamily 1.4
Model: iMac12,1, BootROM IM121.0047.B1F, 4 processors, Intel Core i5, 2.5 GHz, 4 GB, SMC 1.71f22
Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x02FE, 0x45424A3231554538424655302D444A2D4620
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x02FE, 0x45424A3231554538424655302D444A2D4620
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x9A), Atheros 9380: 4.0.67.5-P2P
Bluetooth: Version 4.0.8f17, 2 service, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: ST3500418AS, 500,11 GB
Serial ATA Device: OPTIARC DVD RW AD-5690H
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x850b, 0xfa200000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0xfa111000 / 5
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 4
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfd110000 / 3[/quote]
Can anyone explain me what it was?Why would you want a start button to stop something?
Seriously, I would not routinely shut down your Mac. It is not necessary. Just set it to sleep in System Preferences > Energy Saver.
When you are not using it, just walk away. Things will work better that way. Most of my Macs don't get shut down except while restarting them for software updates. This might be once every couple of months.
Maybe you are looking for
-
Replacement of Tax Columns from AP Tables to ZX Tables
Explanation of Queries : 11i Query: select DIST_MATCH_TYPE, LINE_TYPE_LOOKUP_CODE, AMOUNT_INCLUDES_TAX_FLAG, DISTRIBUTION_LINE_NUMBER, LINE_GROUP_NUMBER, TAX_CODE_OVERRIDE_FLAG, TAX_RECOVERY_OVERRIDE_FLAG, TAX_RECOVERY_RATE, VAT_CODE from AP_INVOICE_
-
This is going to be pretty general because I have really have no clue and no error messages to go on. I went on vacation a week ago. I got back and Photochop CS4 doesn't work. It starts up ok and then when I try to open a file (File>Open) it crashes
-
CSV file generation with timestamp time details
CREATE OR REPLACE PROCEDURE extract_proc AS l_rows number; begin l_rows := extract_function('select * from table1 where date1 between trunc(sysdate) and sysdate 'MYDIR1', 'test.csv'); end; I have a procedure extract_proc shown above which create a CS
-
Hi everybody. Im trying to manipulate data of idocs in a implementation of IDOC_DATA_MAPPER: I want to change a field but I can´t get it. Does anyone knows how this badi works to can change the data???? Thanks a lot. Regards
-
i am trying to generate a report using a multiselect list. The following SQL query for the report gives an error => 1 error has occurred Query cannot be parsed within the Builder. ORA-00933: SQL command not properly ended declare v_sql varchar2(32276