Go Back   TechArena Community > Technical Support > Computer Help > Windows Server > Active Directory
Become a Member!
Forgot your username/password?
Register Tags Active Topics RSS Search Mark Forums Read

Sponsored Links



Errors when DCDiag is run - LsaPolicy operation failed with error

Active Directory


Reply
 
Thread Tools Search this Thread
  #1  
Old 14-02-2006
Misdept
 
Posts: n/a
Errors when DCDiag is run - LsaPolicy operation failed with error

I had a old Windows 2K Domain controller (called DS1) which I demoted and
removed from the LAN.
The roles (schema master and Domain naming master) this server was running
were moved before demotion to another domain controller on our domain.
I then installed a new server runinng W2k3 and named it DS1. This server was
then promoted to a domain controller on the domain. I have since been getting
error messages when I run "dcdiag" on the server, and replication does not
appear to be working as my "netlogon" share is not created. I am also getting
"replication latency warnings".

Can anyone assist or put me in the right direction to solve this problem.
The actual log file with the errors (after running dcdiag) is below.


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\DS1
Starting test: Connectivity
......................... DS1 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DS1
Starting test: Replications
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DS10
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DS11
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DS10
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
......................... DS1 passed test Replications
Starting test: NCSecDesc
......................... DS1 passed test NCSecDesc
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\DS1\netlogon)
[DS1] An net use or LsaPolicy operation failed with error 1203, No
network provider accepted the given network path..
......................... DS1 failed test NetLogons
Starting test: Advertising
......................... DS1 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... DS1 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... DS1 passed test RidManager
Starting test: MachineAccount
......................... DS1 passed test MachineAccount
Starting test: Services
......................... DS1 passed test Services
Starting test: ObjectsReplicated
......................... DS1 passed test ObjectsReplicated
Starting test: frssysvol
......................... DS1 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.
......................... DS1 failed test frsevent
Starting test: kccevent
......................... DS1 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x40000004
Time Generated: 02/14/2006 14:40:24
Event String: The kerberos client received a

......................... DS1 failed test systemlog
Starting test: VerifyReferences
......................... DS1 passed test VerifyReferences

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 : datapoint
Starting test: CrossRefValidation
......................... datapoint passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... datapoint passed test CheckSDRefDom

Running enterprise tests on : datapoint.com
Starting test: Intersite
......................... datapoint.com passed test Intersite
Starting test: FsmoCheck
......................... datapoint.com passed test FsmoCheck


Reply With Quote
  #2  
Old 15-02-2006
Paul Bergson
 
Posts: n/a
Re: Errors when DCDiag is run - LsaPolicy operation failed with error

I don't have a specific answer for you. Can you check your sites and
services and see if there are defined links for all intersites (If you have
any). Not sure if you have any but little bits and pieces of info I'm
getting from this and KB articles are making it sound like you don't have
the schema fully replicated. I can't state that for sure but that is the
most I could find.

What switches did you set on dcdiag? Did you run in verbose with enterprise
checks?

Run dcdiag and netdiag in verbose mode.

If you download a gui script I wrote it should be simple to set and run. It
also has the option to run individual tests without having to learn all the
switch options. The script also automagically outputs the test details to a
text file and calls this text file up at the completion of the test. This
makes it much easier to read and save the details for future use and
analysis.

The script is at http://www.pbbergs.com and select downloads, download
dcdiag and netdiag gui it and save it to c:\program files\support tools\

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

Also download frsdiag and ultrasound, this will provide a full host of log
files to pour through:

FrsDiag
http://www.microsoft.com/downloads/d...displaylang=en

Ultrasound
http://www.microsoft.com/downloads/d...displaylang=en

Intrasite troubleshooting
http://support.microsoft.com/default...b;en-us;249256


Also, is there a firewall that could be between the troubled dc and the
others?


--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
http://www.pbbergs.com/

This posting is provided "AS IS" with no warranties, and confers no rights.


"Misdept" <Misdept@discussions.microsoft.com> wrote in message
news:F4B35E0B-A4EB-44F5-A154-91EE1EEC5411@microsoft.com...
>I had a old Windows 2K Domain controller (called DS1) which I demoted and
> removed from the LAN.
> The roles (schema master and Domain naming master) this server was running
> were moved before demotion to another domain controller on our domain.
> I then installed a new server runinng W2k3 and named it DS1. This server
> was
> then promoted to a domain controller on the domain. I have since been
> getting
> error messages when I run "dcdiag" on the server, and replication does not
> appear to be working as my "netlogon" share is not created. I am also
> getting
> "replication latency warnings".
>
> Can anyone assist or put me in the right direction to solve this problem.
> The actual log file with the errors (after running dcdiag) is below.
>
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site-Name\DS1
> Starting test: Connectivity
> ......................... DS1 passed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\DS1
> Starting test: Replications
> REPLICATION LATENCY WARNING
> ERROR: Expected notification link is missing.
> Source DS10
> Replication of new changes along this path will be delayed.
> This problem should self-correct on the next periodic sync.
> REPLICATION LATENCY WARNING
> ERROR: Expected notification link is missing.
> Source DS11
> Replication of new changes along this path will be delayed.
> This problem should self-correct on the next periodic sync.
> REPLICATION LATENCY WARNING
> ERROR: Expected notification link is missing.
> Source DS10
> Replication of new changes along this path will be delayed.
> This problem should self-correct on the next periodic sync.
> ......................... DS1 passed test Replications
> Starting test: NCSecDesc
> ......................... DS1 passed test NCSecDesc
> Starting test: NetLogons
> Unable to connect to the NETLOGON share! (\\DS1\netlogon)
> [DS1] An net use or LsaPolicy operation failed with error 1203, No
> network provider accepted the given network path..
> ......................... DS1 failed test NetLogons
> Starting test: Advertising
> ......................... DS1 passed test Advertising
> Starting test: KnowsOfRoleHolders
> ......................... DS1 passed test KnowsOfRoleHolders
> Starting test: RidManager
> ......................... DS1 passed test RidManager
> Starting test: MachineAccount
> ......................... DS1 passed test MachineAccount
> Starting test: Services
> ......................... DS1 passed test Services
> Starting test: ObjectsReplicated
> ......................... DS1 passed test ObjectsReplicated
> Starting test: frssysvol
> ......................... DS1 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.
> ......................... DS1 failed test frsevent
> Starting test: kccevent
> ......................... DS1 passed test kccevent
> Starting test: systemlog
> An Error Event occured. EventID: 0x40000004
> Time Generated: 02/14/2006 14:40:24
> Event String: The kerberos client received a
>
> ......................... DS1 failed test systemlog
> Starting test: VerifyReferences
> ......................... DS1 passed test VerifyReferences
>
> 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 : datapoint
> Starting test: CrossRefValidation
> ......................... datapoint passed test CrossRefValidation
> Starting test: CheckSDRefDom
> ......................... datapoint passed test CheckSDRefDom
>
> Running enterprise tests on : datapoint.com
> Starting test: Intersite
> ......................... datapoint.com passed test Intersite
> Starting test: FsmoCheck
> ......................... datapoint.com passed test FsmoCheck
>



Reply With Quote
  #3  
Old 20-02-2006
Misdept
 
Posts: n/a
Re: Errors when DCDiag is run - LsaPolicy operation failed with e

Paul,

Thanks for the response.

In answer to your question - We do not have a firewall in place between DC's.

At the moment replication between DC's is working and the sysvol and
netlogon shares have been created on the server DS1. It appears the problem
was with DNS as the Zone transfers option was not selected on one of our DNS
servers. Enabling this and restarting DNS seems to have fixed the problem.

I recently ran the FRSDIAG utility and there appears to be errors in the
debug log file with error access denied found in the ntfrs_0003.log file. Do
you have any idea what this is all about? See below for log file

..\DS1 on 2006-02-20 at 12.02.22 PM
------------------------------------------------------------

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 ...
ERROR on NtFrs_0003.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
3556: 904: S0: 19:19:14> :SR: Cmd 0123e6a0, CxtG 5926ad06, WS
ERROR_ACCESS_DENIED, To ds.datapoint.com Len: (350) [SndFail - Send
Penalty]
ERROR on NtFrs_0003.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
1548: 877: S0: 19:19:14> :SR: Cmd 01239ad8, CxtG 187ff805, WS
ERROR_ACCESS_DENIED, To ds.datapoint.com Len: (620) [SndFail - rpc call]
ERROR on NtFrs_0003.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
1548: 904: S0: 19:19:14> :SR: Cmd 01239ad8, CxtG 187ff805, WS
ERROR_ACCESS_DENIED, To ds.datapoint.com Len: (620) [SndFail - Send
Penalty]

Found 800 ERROR_ACCESS_DENIED error(s)! Latest ones (up to 3) listed above

......... failed with 800 error entries
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 = failed with 800 error(s)

--------------------------------------------------------------------------

Below is a cutdown copy of the ntfrs_0003.log file containing the errors,
also note the "Marking connection inconsistent" errors on the servers DS1 and
DS11.

<FrsDsFindComputer: 1444: 8796: S2: 11:08:21> :DS: Computer
FQDN is cn=ds1,ou=domain controllers,dc=datapoint,dc=com
<FrsDsFindComputer: 1444: 8802: S2: 11:08:21> :DS: Computer's
dns name is ds1.datapoint.com
<FrsDsFindComputer: 1444: 8816: S2: 11:08:21> :DS: Settings
reference is cn=ntds
settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com
<FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:08:21> :DS: Marking
connection inconsistent.(cn=4e70f121-8d76-40a8-aec0-2b891205e41d,cn=ntds
settings,cn=ds11,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
<FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:08:21> :DS: Marking
connection inconsistent.(cn=20a0ef8b-325e-4323-944f-0b4cd48711bf,cn=ntds
settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
<FrsHashCalcString: 1444: 4842: S0: 11:08:21> Name =
S-1-5-21-4259660283-2661013885-1605721479-3686
<FrsHashCalcString: 1444: 4842: S0: 11:08:21> Name =
S-1-5-21-4259660283-2661013885-1605721479-3686
<FrsHashCalcString: 1444: 4842: S0: 11:08:21> Name =
S-1-5-21-4259660283-2661013885-1605721479-5811
<FrsHashCalcString: 1444: 4842: S0: 11:08:21> Name =
S-1-5-21-4259660283-2661013885-1605721479-5811
<FrsHashCalcString: 1444: 4842: S0: 11:08:21> Name =
S-1-5-21-4259660283-2661013885-1605721479-5811
<SndCsMain: 2680: 877: S0: 11:08:21> :SR: Cmd
0025fc28, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - rpc call]
<SndCsMain: 2680: 904: S0: 11:08:21> :SR: Cmd
0025fc28, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - Send Penalty]
<ThSupWaitThread: 3656: 505: S1: 11:10:56> :S:
ChgOrdRetryCS: Waiting
<ThSupWaitThread: 3656: 533: S1: 11:10:56> :S:
ChgOrdRetryCS: normal wait
<SndCsMain: 2680: 877: S0: 11:11:51> :SR: Cmd
0123f668, CxtG 187ff805, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - rpc call]
<SndCsMain: 2680: 904: S0: 11:11:51> :SR: Cmd
0123f668, CxtG 187ff805, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - Send Penalty]
<FrsDsFindComputer: 1444: 8796: S2: 11:13:21> :DS: Computer
FQDN is cn=ds1,ou=domain controllers,dc=datapoint,dc=com
<FrsDsFindComputer: 1444: 8802: S2: 11:13:21> :DS: Computer's
dns name is ds1.datapoint.com
<FrsDsFindComputer: 1444: 8816: S2: 11:13:21> :DS: Settings
reference is cn=ntds
settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com
<FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:13:21> :DS: Marking
connection inconsistent.(cn=4e70f121-8d76-40a8-aec0-2b891205e41d,cn=ntds
settings,cn=ds11,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
<FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:13:21> :DS: Marking
connection inconsistent.(cn=20a0ef8b-325e-4323-944f-0b4cd48711bf,cn=ntds
settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
<SndCsMain: 1624: 877: S0: 11:13:21> :SR: Cmd
0121e080, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - rpc call]
<SndCsMain: 1624: 904: S0: 11:13:21> :SR: Cmd
0121e080, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - Send Penalty]
<RcsSetCxtionSchedule: 1344: 7365: S0: 11:15:23> :X: 187ff805,
schedule is on
<RcsSetCxtionSchedule: 1344: 7365: S0: 11:15:23> :X: 5926ad06,
schedule is on
<RcsSetCxtionSchedule: 1344: 7365: S0: 11:15:23> :X: bfe96219,
schedule is on
<RcsSetCxtionSchedule: 1344: 7365: S0: 11:15:23> :X: e62ce0d4,
schedule is on
<RcsSetCxtionSchedule: 1344: 7365: S0: 11:15:23> :X: 70d0bced,
schedule is on
<SndCsMain: 1624: 877: S0: 11:15:23> :SR: Cmd
0121dab0, CxtG 187ff805, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - rpc call]
<SndCsMain: 1624: 904: S0: 11:15:23> :SR: Cmd
0121dab0, CxtG 187ff805, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - Send Penalty]
<SndCsMain: 1208: 877: S0: 11:15:23> :SR: Cmd
0123ee48, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - rpc call]
<SndCsMain: 1208: 904: S0: 11:15:23> :SR: Cmd
0123ee48, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - Send Penalty]
<MainWait: 3024: 619: S0: 11:15:56> Wait thread is
exiting.
<ThSupWaitThread: 3656: 505: S1: 11:15:56> :S: Wait: Waiting
<ThSupWaitThread: 3656: 533: S1: 11:15:56> :S: Wait: normal
wait
<FrsDsFindComputer: 1444: 8796: S2: 11:18:21> :DS: Computer
FQDN is cn=ds1,ou=domain controllers,dc=datapoint,dc=com
<FrsDsFindComputer: 1444: 8802: S2: 11:18:21> :DS: Computer's
dns name is ds1.datapoint.com
<FrsDsFindComputer: 1444: 8816: S2: 11:18:21> :DS: Settings
reference is cn=ntds
settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com
<FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:18:21> :DS: Marking
connection inconsistent.(cn=4e70f121-8d76-40a8-aec0-2b891205e41d,cn=ntds
settings,cn=ds11,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
<FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:18:21> :DS: Marking
connection inconsistent.(cn=20a0ef8b-325e-4323-944f-0b4cd48711bf,cn=ntds
settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
<SndCsMain: 1208: 877: S0: 11:18:21> :SR: Cmd
01240cb8, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - rpc call]
<SndCsMain: 1208: 904: S0: 11:18:21> :SR: Cmd
01240cb8, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - Send Penalty]
<ThSupWaitThread: 3656: 505: S1: 11:23:21> :S: SndCs: Waiting
<ThSupWaitThread: 3656: 533: S1: 11:23:21> :S: SndCs: normal
wait
<ThSupWaitThread: 3656: 505: S1: 11:23:21> :S: SndCs: Waiting
<ThSupWaitThread: 3656: 533: S1: 11:23:21> :S: SndCs: normal
wait
<ThSupWaitThread: 3656: 505: S1: 11:23:21> :S: ReplicaCs:
Waiting
<ThSupWaitThread: 3656: 533: S1: 11:23:21> :S: ReplicaCs:
normal wait
<ThSupWaitThread: 3656: 505: S1: 11:23:21> :S: ReplicaCs:
Waiting
<ThSupWaitThread: 3656: 533: S1: 11:23:21> :S: ReplicaCs:
normal wait
<FrsDsFindComputer: 1444: 8796: S2: 11:23:21> :DS: Computer
FQDN is cn=ds1,ou=domain controllers,dc=datapoint,dc=com
<FrsDsFindComputer: 1444: 8802: S2: 11:23:21> :DS: Computer's
dns name is ds1.datapoint.com
<FrsDsFindComputer: 1444: 8816: S2: 11:23:21> :DS: Settings
reference is cn=ntds
settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com
<FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:23:21> :DS: Marking
connection inconsistent.(cn=4e70f121-8d76-40a8-aec0-2b891205e41d,cn=ntds
settings,cn=ds11,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
<FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:23:21> :DS: Marking
connection inconsistent.(cn=20a0ef8b-325e-4323-944f-0b4cd48711bf,cn=ntds
settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
<SndCsMain: 1208: 877: S0: 11:23:21> :SR: Cmd
01240e20, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - rpc call]
<SndCsMain: 1208: 904: S0: 11:23:21> :SR: Cmd
01240e20, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - Send Penalty]
<FrsDsFindComputer: 1444: 8796: S2: 11:28:21> :DS: Computer
FQDN is cn=ds1,ou=domain controllers,dc=datapoint,dc=com
<FrsDsFindComputer: 1444: 8802: S2: 11:28:21> :DS: Computer's
dns name is ds1.datapoint.com
<FrsDsFindComputer: 1444: 8816: S2: 11:28:21> :DS: Settings
reference is cn=ntds
settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com
<FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:28:21> :DS: Marking
connection inconsistent.(cn=4e70f121-8d76-40a8-aec0-2b891205e41d,cn=ntds
settings,cn=ds11,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
<FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:28:21> :DS: Marking
connection inconsistent.(cn=20a0ef8b-325e-4323-944f-0b4cd48711bf,cn=ntds
settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
<SndCsMain: 1208: 877: S0: 11:28:21> :SR: Cmd
01232338, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - rpc call]
<SndCsMain: 1208: 904: S0: 11:28:21> :SR: Cmd
01232338, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com Len:
(350) [SndFail - Send Penalty]

--------------------------------------------
Any help would be appreciated.

"Paul Bergson" wrote:

> I don't have a specific answer for you. Can you check your sites and
> services and see if there are defined links for all intersites (If you have
> any). Not sure if you have any but little bits and pieces of info I'm
> getting from this and KB articles are making it sound like you don't have
> the schema fully replicated. I can't state that for sure but that is the
> most I could find.
>
> What switches did you set on dcdiag? Did you run in verbose with enterprise
> checks?
>
> Run dcdiag and netdiag in verbose mode.
>
> If you download a gui script I wrote it should be simple to set and run. It
> also has the option to run individual tests without having to learn all the
> switch options. The script also automagically outputs the test details to a
> text file and calls this text file up at the completion of the test. This
> makes it much easier to read and save the details for future use and
> analysis.
>
> The script is at http://www.pbbergs.com and select downloads, download
> dcdiag and netdiag gui it and save it to c:\program files\support tools\
>
> Just select both dcdiag and netdiag make sure verbose is set. (Leave the
> default settings for dcdiag as set when selected)
>
> Also download frsdiag and ultrasound, this will provide a full host of log
> files to pour through:
>
> FrsDiag
> http://www.microsoft.com/downloads/d...displaylang=en
>
> Ultrasound
> http://www.microsoft.com/downloads/d...displaylang=en
>
> Intrasite troubleshooting
> http://support.microsoft.com/default...b;en-us;249256
>
>
> Also, is there a firewall that could be between the troubled dc and the
> others?
>
>
> --
>
>
> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
> http://www.pbbergs.com/
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Misdept" <Misdept@discussions.microsoft.com> wrote in message
> news:F4B35E0B-A4EB-44F5-A154-91EE1EEC5411@microsoft.com...
> >I had a old Windows 2K Domain controller (called DS1) which I demoted and
> > removed from the LAN.
> > The roles (schema master and Domain naming master) this server was running
> > were moved before demotion to another domain controller on our domain.
> > I then installed a new server runinng W2k3 and named it DS1. This server
> > was
> > then promoted to a domain controller on the domain. I have since been
> > getting
> > error messages when I run "dcdiag" on the server, and replication does not
> > appear to be working as my "netlogon" share is not created. I am also
> > getting
> > "replication latency warnings".
> >
> > Can anyone assist or put me in the right direction to solve this problem.
> > The actual log file with the errors (after running dcdiag) is below.
> >
> >
> > Domain Controller Diagnosis
> >
> > Performing initial setup:
> > Done gathering initial info.
> >
> > Doing initial required tests
> >
> > Testing server: Default-First-Site-Name\DS1
> > Starting test: Connectivity
> > ......................... DS1 passed test Connectivity
> >
> > Doing primary tests
> >
> > Testing server: Default-First-Site-Name\DS1
> > Starting test: Replications
> > REPLICATION LATENCY WARNING
> > ERROR: Expected notification link is missing.
> > Source DS10
> > Replication of new changes along this path will be delayed.
> > This problem should self-correct on the next periodic sync.
> > REPLICATION LATENCY WARNING
> > ERROR: Expected notification link is missing.
> > Source DS11
> > Replication of new changes along this path will be delayed.
> > This problem should self-correct on the next periodic sync.
> > REPLICATION LATENCY WARNING
> > ERROR: Expected notification link is missing.
> > Source DS10
> > Replication of new changes along this path will be delayed.
> > This problem should self-correct on the next periodic sync.
> > ......................... DS1 passed test Replications
> > Starting test: NCSecDesc
> > ......................... DS1 passed test NCSecDesc
> > Starting test: NetLogons
> > Unable to connect to the NETLOGON share! (\\DS1\netlogon)
> > [DS1] An net use or LsaPolicy operation failed with error 1203, No
> > network provider accepted the given network path..
> > ......................... DS1 failed test NetLogons
> > Starting test: Advertising
> > ......................... DS1 passed test Advertising
> > Starting test: KnowsOfRoleHolders
> > ......................... DS1 passed test KnowsOfRoleHolders
> > Starting test: RidManager
> > ......................... DS1 passed test RidManager
> > Starting test: MachineAccount
> > ......................... DS1 passed test MachineAccount
> > Starting test: Services
> > ......................... DS1 passed test Services
> > Starting test: ObjectsReplicated
> > ......................... DS1 passed test ObjectsReplicated
> > Starting test: frssysvol
> > ......................... DS1 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.
> > ......................... DS1 failed test frsevent
> > Starting test: kccevent
> > ......................... DS1 passed test kccevent
> > Starting test: systemlog
> > An Error Event occured. EventID: 0x40000004
> > Time Generated: 02/14/2006 14:40:24
> > Event String: The kerberos client received a
> >
> > ......................... DS1 failed test systemlog
> > Starting test: VerifyReferences
> > ......................... DS1 passed test VerifyReferences
> >
> > 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 : datapoint
> > Starting test: CrossRefValidation
> > ......................... datapoint passed test CrossRefValidation
> > Starting test: CheckSDRefDom
> > ......................... datapoint passed test CheckSDRefDom
> >
> > Running enterprise tests on : datapoint.com
> > Starting test: Intersite
> > ......................... datapoint.com passed test Intersite
> > Starting test: FsmoCheck
> > ......................... datapoint.com passed test FsmoCheck
> >

>
>
>

Reply With Quote
  #4  
Old 21-02-2006
Paul Bergson
 
Posts: n/a
Re: Errors when DCDiag is run - LsaPolicy operation failed with e

Sorry I don't. Have you tried other tools such as Ultrasound to try and
give you more info?

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
http://www.pbbergs.com/

This posting is provided "AS IS" with no warranties, and confers no rights.


"Misdept" <Misdept@discussions.microsoft.com> wrote in message
news:C8275573-0488-479F-A8E0-59039F78E45B@microsoft.com...
> Paul,
>
> Thanks for the response.
>
> In answer to your question - We do not have a firewall in place between
> DC's.
>
> At the moment replication between DC's is working and the sysvol and
> netlogon shares have been created on the server DS1. It appears the
> problem
> was with DNS as the Zone transfers option was not selected on one of our
> DNS
> servers. Enabling this and restarting DNS seems to have fixed the problem.
>
> I recently ran the FRSDIAG utility and there appears to be errors in the
> debug log file with error access denied found in the ntfrs_0003.log file.
> Do
> you have any idea what this is all about? See below for log file
>
> .\DS1 on 2006-02-20 at 12.02.22 PM
> ------------------------------------------------------------
>
> 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 ...
> ERROR on NtFrs_0003.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
> 3556: 904: S0: 19:19:14> :SR: Cmd 0123e6a0, CxtG 5926ad06, WS
> ERROR_ACCESS_DENIED, To ds.datapoint.com Len: (350) [SndFail - Send
> Penalty]
> ERROR on NtFrs_0003.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
> 1548: 877: S0: 19:19:14> :SR: Cmd 01239ad8, CxtG 187ff805, WS
> ERROR_ACCESS_DENIED, To ds.datapoint.com Len: (620) [SndFail - rpc
> call]
> ERROR on NtFrs_0003.log : "ERROR_ACCESS_DENIED" : <SndCsMain:
> 1548: 904: S0: 19:19:14> :SR: Cmd 01239ad8, CxtG 187ff805, WS
> ERROR_ACCESS_DENIED, To ds.datapoint.com Len: (620) [SndFail - Send
> Penalty]
>
> Found 800 ERROR_ACCESS_DENIED error(s)! Latest ones (up to 3) listed above
>
> ......... failed with 800 error entries
> 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 = failed with 800 error(s)
>
> --------------------------------------------------------------------------
>
> Below is a cutdown copy of the ntfrs_0003.log file containing the errors,
> also note the "Marking connection inconsistent" errors on the servers DS1
> and
> DS11.
>
> <FrsDsFindComputer: 1444: 8796: S2: 11:08:21> :DS: Computer
> FQDN is cn=ds1,ou=domain controllers,dc=datapoint,dc=com
> <FrsDsFindComputer: 1444: 8802: S2: 11:08:21> :DS: Computer's
> dns name is ds1.datapoint.com
> <FrsDsFindComputer: 1444: 8816: S2: 11:08:21> :DS: Settings
> reference is cn=ntds
> settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com
> <FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:08:21> :DS: Marking
> connection inconsistent.(cn=4e70f121-8d76-40a8-aec0-2b891205e41d,cn=ntds
> settings,cn=ds11,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
> <FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:08:21> :DS: Marking
> connection inconsistent.(cn=20a0ef8b-325e-4323-944f-0b4cd48711bf,cn=ntds
> settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
> <FrsHashCalcString: 1444: 4842: S0: 11:08:21> Name =
> S-1-5-21-4259660283-2661013885-1605721479-3686
> <FrsHashCalcString: 1444: 4842: S0: 11:08:21> Name =
> S-1-5-21-4259660283-2661013885-1605721479-3686
> <FrsHashCalcString: 1444: 4842: S0: 11:08:21> Name =
> S-1-5-21-4259660283-2661013885-1605721479-5811
> <FrsHashCalcString: 1444: 4842: S0: 11:08:21> Name =
> S-1-5-21-4259660283-2661013885-1605721479-5811
> <FrsHashCalcString: 1444: 4842: S0: 11:08:21> Name =
> S-1-5-21-4259660283-2661013885-1605721479-5811
> <SndCsMain: 2680: 877: S0: 11:08:21> :SR: Cmd
> 0025fc28, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - rpc call]
> <SndCsMain: 2680: 904: S0: 11:08:21> :SR: Cmd
> 0025fc28, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - Send Penalty]
> <ThSupWaitThread: 3656: 505: S1: 11:10:56> :S:
> ChgOrdRetryCS: Waiting
> <ThSupWaitThread: 3656: 533: S1: 11:10:56> :S:
> ChgOrdRetryCS: normal wait
> <SndCsMain: 2680: 877: S0: 11:11:51> :SR: Cmd
> 0123f668, CxtG 187ff805, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - rpc call]
> <SndCsMain: 2680: 904: S0: 11:11:51> :SR: Cmd
> 0123f668, CxtG 187ff805, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - Send Penalty]
> <FrsDsFindComputer: 1444: 8796: S2: 11:13:21> :DS: Computer
> FQDN is cn=ds1,ou=domain controllers,dc=datapoint,dc=com
> <FrsDsFindComputer: 1444: 8802: S2: 11:13:21> :DS: Computer's
> dns name is ds1.datapoint.com
> <FrsDsFindComputer: 1444: 8816: S2: 11:13:21> :DS: Settings
> reference is cn=ntds
> settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com
> <FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:13:21> :DS: Marking
> connection inconsistent.(cn=4e70f121-8d76-40a8-aec0-2b891205e41d,cn=ntds
> settings,cn=ds11,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
> <FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:13:21> :DS: Marking
> connection inconsistent.(cn=20a0ef8b-325e-4323-944f-0b4cd48711bf,cn=ntds
> settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
> <SndCsMain: 1624: 877: S0: 11:13:21> :SR: Cmd
> 0121e080, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - rpc call]
> <SndCsMain: 1624: 904: S0: 11:13:21> :SR: Cmd
> 0121e080, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - Send Penalty]
> <RcsSetCxtionSchedule: 1344: 7365: S0: 11:15:23> :X: 187ff805,
> schedule is on
> <RcsSetCxtionSchedule: 1344: 7365: S0: 11:15:23> :X: 5926ad06,
> schedule is on
> <RcsSetCxtionSchedule: 1344: 7365: S0: 11:15:23> :X: bfe96219,
> schedule is on
> <RcsSetCxtionSchedule: 1344: 7365: S0: 11:15:23> :X: e62ce0d4,
> schedule is on
> <RcsSetCxtionSchedule: 1344: 7365: S0: 11:15:23> :X: 70d0bced,
> schedule is on
> <SndCsMain: 1624: 877: S0: 11:15:23> :SR: Cmd
> 0121dab0, CxtG 187ff805, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - rpc call]
> <SndCsMain: 1624: 904: S0: 11:15:23> :SR: Cmd
> 0121dab0, CxtG 187ff805, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - Send Penalty]
> <SndCsMain: 1208: 877: S0: 11:15:23> :SR: Cmd
> 0123ee48, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - rpc call]
> <SndCsMain: 1208: 904: S0: 11:15:23> :SR: Cmd
> 0123ee48, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - Send Penalty]
> <MainWait: 3024: 619: S0: 11:15:56> Wait thread is
> exiting.
> <ThSupWaitThread: 3656: 505: S1: 11:15:56> :S: Wait:
> Waiting
> <ThSupWaitThread: 3656: 533: S1: 11:15:56> :S: Wait:
> normal
> wait
> <FrsDsFindComputer: 1444: 8796: S2: 11:18:21> :DS: Computer
> FQDN is cn=ds1,ou=domain controllers,dc=datapoint,dc=com
> <FrsDsFindComputer: 1444: 8802: S2: 11:18:21> :DS: Computer's
> dns name is ds1.datapoint.com
> <FrsDsFindComputer: 1444: 8816: S2: 11:18:21> :DS: Settings
> reference is cn=ntds
> settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com
> <FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:18:21> :DS: Marking
> connection inconsistent.(cn=4e70f121-8d76-40a8-aec0-2b891205e41d,cn=ntds
> settings,cn=ds11,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
> <FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:18:21> :DS: Marking
> connection inconsistent.(cn=20a0ef8b-325e-4323-944f-0b4cd48711bf,cn=ntds
> settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
> <SndCsMain: 1208: 877: S0: 11:18:21> :SR: Cmd
> 01240cb8, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - rpc call]
> <SndCsMain: 1208: 904: S0: 11:18:21> :SR: Cmd
> 01240cb8, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - Send Penalty]
> <ThSupWaitThread: 3656: 505: S1: 11:23:21> :S: SndCs:
> Waiting
> <ThSupWaitThread: 3656: 533: S1: 11:23:21> :S: SndCs:
> normal
> wait
> <ThSupWaitThread: 3656: 505: S1: 11:23:21> :S: SndCs:
> Waiting
> <ThSupWaitThread: 3656: 533: S1: 11:23:21> :S: SndCs:
> normal
> wait
> <ThSupWaitThread: 3656: 505: S1: 11:23:21> :S: ReplicaCs:
> Waiting
> <ThSupWaitThread: 3656: 533: S1: 11:23:21> :S: ReplicaCs:
> normal wait
> <ThSupWaitThread: 3656: 505: S1: 11:23:21> :S: ReplicaCs:
> Waiting
> <ThSupWaitThread: 3656: 533: S1: 11:23:21> :S: ReplicaCs:
> normal wait
> <FrsDsFindComputer: 1444: 8796: S2: 11:23:21> :DS: Computer
> FQDN is cn=ds1,ou=domain controllers,dc=datapoint,dc=com
> <FrsDsFindComputer: 1444: 8802: S2: 11:23:21> :DS: Computer's
> dns name is ds1.datapoint.com
> <FrsDsFindComputer: 1444: 8816: S2: 11:23:21> :DS: Settings
> reference is cn=ntds
> settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com
> <FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:23:21> :DS: Marking
> connection inconsistent.(cn=4e70f121-8d76-40a8-aec0-2b891205e41d,cn=ntds
> settings,cn=ds11,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
> <FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:23:21> :DS: Marking
> connection inconsistent.(cn=20a0ef8b-325e-4323-944f-0b4cd48711bf,cn=ntds
> settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
> <SndCsMain: 1208: 877: S0: 11:23:21> :SR: Cmd
> 01240e20, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - rpc call]
> <SndCsMain: 1208: 904: S0: 11:23:21> :SR: Cmd
> 01240e20, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - Send Penalty]
> <FrsDsFindComputer: 1444: 8796: S2: 11:28:21> :DS: Computer
> FQDN is cn=ds1,ou=domain controllers,dc=datapoint,dc=com
> <FrsDsFindComputer: 1444: 8802: S2: 11:28:21> :DS: Computer's
> dns name is ds1.datapoint.com
> <FrsDsFindComputer: 1444: 8816: S2: 11:28:21> :DS: Settings
> reference is cn=ntds
> settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com
> <FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:28:21> :DS: Marking
> connection inconsistent.(cn=4e70f121-8d76-40a8-aec0-2b891205e41d,cn=ntds
> settings,cn=ds11,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
> <FrsDsGetSysvolCxtions: 1444: 3488: S0: 11:28:21> :DS: Marking
> connection inconsistent.(cn=20a0ef8b-325e-4323-944f-0b4cd48711bf,cn=ntds
> settings,cn=ds1,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=datapoint,dc=com)
> <SndCsMain: 1208: 877: S0: 11:28:21> :SR: Cmd
> 01232338, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - rpc call]
> <SndCsMain: 1208: 904: S0: 11:28:21> :SR: Cmd
> 01232338, CxtG 5926ad06, WS ERROR_ACCESS_DENIED, To ds.datapoint.com
> Len:
> (350) [SndFail - Send Penalty]
>
> --------------------------------------------
> Any help would be appreciated.
>
> "Paul Bergson" wrote:
>
>> I don't have a specific answer for you. Can you check your sites and
>> services and see if there are defined links for all intersites (If you
>> have
>> any). Not sure if you have any but little bits and pieces of info I'm
>> getting from this and KB articles are making it sound like you don't have
>> the schema fully replicated. I can't state that for sure but that is the
>> most I could find.
>>
>> What switches did you set on dcdiag? Did you run in verbose with
>> enterprise
>> checks?
>>
>> Run dcdiag and netdiag in verbose mode.
>>
>> If you download a gui script I wrote it should be simple to set and run.
>> It
>> also has the option to run individual tests without having to learn all
>> the
>> switch options. The script also automagically outputs the test details
>> to a
>> text file and calls this text file up at the completion of the test.
>> This
>> makes it much easier to read and save the details for future use and
>> analysis.
>>
>> The script is at http://www.pbbergs.com and select downloads, download
>> dcdiag and netdiag gui it and save it to c:\program files\support tools\
>>
>> Just select both dcdiag and netdiag make sure verbose is set. (Leave the
>> default settings for dcdiag as set when selected)
>>
>> Also download frsdiag and ultrasound, this will provide a full host of
>> log
>> files to pour through:
>>
>> FrsDiag
>> http://www.microsoft.com/downloads/d...displaylang=en
>>
>> Ultrasound
>> http://www.microsoft.com/downloads/d...displaylang=en
>>
>> Intrasite troubleshooting
>> http://support.microsoft.com/default...b;en-us;249256
>>
>>
>> Also, is there a firewall that could be between the troubled dc and the
>> others?
>>
>>
>> --
>>
>>
>> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
>> http://www.pbbergs.com/
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "Misdept" <Misdept@discussions.microsoft.com> wrote in message
>> news:F4B35E0B-A4EB-44F5-A154-91EE1EEC5411@microsoft.com...
>> >I had a old Windows 2K Domain controller (called DS1) which I demoted
>> >and
>> > removed from the LAN.
>> > The roles (schema master and Domain naming master) this server was
>> > running
>> > were moved before demotion to another domain controller on our domain.
>> > I then installed a new server runinng W2k3 and named it DS1. This
>> > server
>> > was
>> > then promoted to a domain controller on the domain. I have since been
>> > getting
>> > error messages when I run "dcdiag" on the server, and replication does
>> > not
>> > appear to be working as my "netlogon" share is not created. I am also
>> > getting
>> > "replication latency warnings".
>> >
>> > Can anyone assist or put me in the right direction to solve this
>> > problem.
>> > The actual log file with the errors (after running dcdiag) is below.
>> >
>> >
>> > Domain Controller Diagnosis
>> >
>> > Performing initial setup:
>> > Done gathering initial info.
>> >
>> > Doing initial required tests
>> >
>> > Testing server: Default-First-Site-Name\DS1
>> > Starting test: Connectivity
>> > ......................... DS1 passed test Connectivity
>> >
>> > Doing primary tests
>> >
>> > Testing server: Default-First-Site-Name\DS1
>> > Starting test: Replications
>> > REPLICATION LATENCY WARNING
>> > ERROR: Expected notification link is missing.
>> > Source DS10
>> > Replication of new changes along this path will be delayed.
>> > This problem should self-correct on the next periodic sync.
>> > REPLICATION LATENCY WARNING
>> > ERROR: Expected notification link is missing.
>> > Source DS11
>> > Replication of new changes along this path will be delayed.
>> > This problem should self-correct on the next periodic sync.
>> > REPLICATION LATENCY WARNING
>> > ERROR: Expected notification link is missing.
>> > Source DS10
>> > Replication of new changes along this path will be delayed.
>> > This problem should self-correct on the next periodic sync.
>> > ......................... DS1 passed test Replications
>> > Starting test: NCSecDesc
>> > ......................... DS1 passed test NCSecDesc
>> > Starting test: NetLogons
>> > Unable to connect to the NETLOGON share! (\\DS1\netlogon)
>> > [DS1] An net use or LsaPolicy operation failed with error 1203,
>> > No
>> > network provider accepted the given network path..
>> > ......................... DS1 failed test NetLogons
>> > Starting test: Advertising
>> > ......................... DS1 passed test Advertising
>> > Starting test: KnowsOfRoleHolders
>> > ......................... DS1 passed test KnowsOfRoleHolders
>> > Starting test: RidManager
>> > ......................... DS1 passed test RidManager
>> > Starting test: MachineAccount
>> > ......................... DS1 passed test MachineAccount
>> > Starting test: Services
>> > ......................... DS1 passed test Services
>> > Starting test: ObjectsReplicated
>> > ......................... DS1 passed test ObjectsReplicated
>> > Starting test: frssysvol
>> > ......................... DS1 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.
>> > ......................... DS1 failed test frsevent
>> > Starting test: kccevent
>> > ......................... DS1 passed test kccevent
>> > Starting test: systemlog
>> > An Error Event occured. EventID: 0x40000004
>> > Time Generated: 02/14/2006 14:40:24
>> > Event String: The kerberos client received a
>> >
>> > ......................... DS1 failed test systemlog
>> > Starting test: VerifyReferences
>> > ......................... DS1 passed test VerifyReferences
>> >
>> > 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 : datapoint
>> > Starting test: CrossRefValidation
>> > ......................... datapoint passed test
>> > CrossRefValidation
>> > Starting test: CheckSDRefDom
>> > ......................... datapoint passed test CheckSDRefDom
>> >
>> > Running enterprise tests on : datapoint.com
>> > Starting test: Intersite
>> > ......................... datapoint.com passed test Intersite
>> > Starting test: FsmoCheck
>> > ......................... datapoint.com passed test FsmoCheck
>> >

>>
>>
>>



Reply With Quote
Reply

  TechArena Community > Technical Support > Computer Help > Windows Server > Active Directory
Tags: , ,



Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "Errors when DCDiag is run - LsaPolicy operation failed with error"
Thread Thread Starter Forum Replies Last Post
dcdiag error failed test connectivity someone275 Active Directory 1 11-05-2011 04:03 AM
Operation failed with error 0x00003e3 Evoldo Windows Software 5 06-04-2011 07:43 AM
Internet IP error: "The operation failed as no adapter is in the state permissible for this operation" hindustnidude Networking & Security 3 10-09-2009 06:35 PM
dcdiag - advertising errors on newley promoted domain controller Andrew Story Active Directory 5 01-10-2008 05:42 PM
How to fix DCDIAG errors on windows server Robbin M Active Directory 1 22-03-2007 06:35 PM


All times are GMT +5.5. The time now is 02:54 PM.