Event ID: 1000 Windows cannot access the registry information at \\mydomain\sysvol\...

  • Thread starter Thread starter Antonin
  • Start date Start date
A

Antonin

I have an Event ID: 1000 on server 2000 PDC, Active Directory
Windows cannot access the registry information at
\\health.on.net\sysvol\health.on.net\Policies\{31B2F340-016D-11D2_945F-00C04FB984F9}\Machine\registry.pol
with (51).

I rebuilt the server, restored backup and it was working fine one day. Now
the error is back again.

Please help.

Antonin
 
Usually event id 1000 will associate with another event together. See if the
followings help.

Cannot Access Group Policy Objects--Event ID 1000 and Event ID 1001 Logged
http://support.microsoft.com/kb/258296/EN-US/

Event ID 1000, 1001 Is Logged Every Five Minutes in the Application Event Log
http://support.microsoft.com/default.aspx?scid=kb;[LN];290647

Event ID 1000 is logged on Windows 2000 domain controllers
http://support.microsoft.com/?kbid=830062

SceCli Event ID 1001 and UserEnv Event ID 1000 When Dfs Client Is Disabled
http://support.microsoft.com/kb/259398/EN-US/

BR,
Denis
 
Hi Denis,

Thanks for your reply.

I have read all the articles and none applies to me.
I have only one network card and File and Printer Sharing on it enabled.
I have Dfs Client enabled.
I have all the correct permissions on the sysvol folder.

Is there anything to fix this?
 
Antonin said:
I have an Event ID: 1000 on server 2000 PDC, Active Directory
Windows cannot access the registry information at
\\health.on.net\sysvol\health.on.net\Policies\{31B2F340-016D-11D2_945F-00C04FB984F9}\Machine\registry.pol
with (51).

I rebuilt the server, restored backup and it was working fine one day. Now
the error is back again.

http://www.eventid.net/display.asp?eventid=1000&eventno=1109&source=Userenv&phase=1

<quote>
Error code 51 - "The remote computer is not available." - "The \\Active
Directory Domain Name\Sysvol share is a special share that requires the
distributed file system (Dfs) client to make a connection. If the Dfs
client is disabled, the error messages are generated. ". See the link to
Q259398.

Error code 51 - I had disabled file and printer sharing on a 2000 DC,
reenabling that fixed the problem.
</quote>


Check also other suggestion from this page - check Your services binding
in the advanced network card configuration, move file and sharing on the
first position. Do You have any other protocols then TCP/IP?
 
Hi Tomasz,

Thanks for your reply. I have only TCP/IP protocol. I have file sharing
enabled and the binding is on the top.
I rebuild the server again and restored the backup. The sysvol was
accessible, dcdiag returned no errors. Then I assigned an IP address to the
network connection. It was still working. I rebooted the computer and sysvol
is not accessible again.

Antonin
 
Back
Top