Error when adding new DC

[Johan]

Hello!

I've got a 2003 native domain setup with 2 DCs and everything is working
fine.. Not a single error/warning in the event logs.

Today I tried to add another DC to the domain, but after reboot I got the
Event ID 1097 followed by 1030 caused by the Userenv.

The problem is documentet on microsoft's site but the sollution provided
does not solve my the problem. (Check to see if NetLogon is running on all
DCs and is set to automatic). I've found other solutions suggesting it is a
time setup problem... Re-synched (It was already synched) the time using net
time /set, without success.

Anyone got any suggestions on how to solve this?





The errors:
(http://support.microsoft.com/default.aspx?scid=kb;en-us;832215)
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: date
Time: time
Type: Error
User: NT AUTHORITY\SYSTEM
Computer: servername
Description: Windows cannot query for the list of Group Policy objects.
Check the event log for possible messages previously logged by the policy
engine that describes the reason for this.

Event Source: Userenv
Event Category: None
Event ID: 1097
Date: date
Time: time
Type: Error
User: NT AUTHORITY\SYSTEM
Computer: servername
Description: Windows cannot find the machine account. The Local Security
Authority cannot be contacted.

 

[Cary Shultz [A.D. MVP]]

Johan,

Take a look at the following two links to see if they help you:

http://www.eventid.net/display.asp?eventid=1030&source=
http://www.eventid.net/display.asp?eventid=1097&source=

HTH,

Cary

 

[Johan]

Thanks for the tip, however it didn't solve my problem.
It suggests that the DFS clients isn't running and I should check the
registry, but it's applicable to WinXP only.. 2003 doesn't even have that
key.
The other link suggested the timesynch, which I had already tried.

Any other tips/sugestions would be greatly appreciated!

Regards,
Johan

 

[Jordan]

If the message occurs only during startup and you see a 1704 logged
subsequently, these error could be safely ignored.
It's caused by services startup timing issue. (Not sure as to why it occurs
only on specific machines).