Errors when DCDiag is run - LsaPolicy operation failed with error

Errors when DCDiag is run - LsaPolicy operation failed with error

Post by TWlzZGVwd » Thu, 16 Feb 2006 00:51:28


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 Eve
 
 
 

Errors when DCDiag is run - LsaPolicy operation failed with error

Post by Paul Bergs » Thu, 16 Feb 2006 12:38:06

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/details.aspx?familyid=43CB658E-8553-4DE7-811A-562563EB5EBF&displaylang=en

Ultrasound
http://www.microsoft.com/downloads/details.aspx?familyid=61acb9b9-c354-4f98-a823-24cc0da73b50&displaylang=en

Intrasite troubleshooting
http://support.microsoft.com/default.aspx?scid=kb;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" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...