Solved

\\Server\SYSVOL share exists, but \\domain.local\sysvol is gone - GPO and Other Issues

Posted on 2008-10-30
4
2,126 Views
Last Modified: 2012-08-14
I discovered that I'm getting this after some problems last week with my SBS 2003 Server (Exchange SP2 corrupted the machine, had to reinstall Exchange and then reapply SP2).

Server is SBS 2003 with SP2 on it.

The dreaded 1058 error:
--------------------------------------------------
Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1058
Date:            10/30/2008
Time:            12:10:27 PM
User:            NT AUTHORITY\SYSTEM
Computer:      SERVER
Description:
Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=WML,DC=local. The file must be present at the location <\\domain.local\sysvol\domain.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied. ). Group Policy processing aborted.
---------------------

When I attempt to go to Start, run, "\\domain.local", I get:
\\domain.local is not accessible. ... Network path was not found.

I have restated NTFRS DFS to no avail.  

DNS seems good, including good and correct ping of "domain.local"

How can I recreate the \\domain.local share so I can republish the SYSVOL share?
0
Comment
Question by:Dynatics
  • 2
  • 2
4 Comments
 
LVL 8

Expert Comment

by:PaperTiger
ID: 22842872
0
 

Author Comment

by:Dynatics
ID: 22843134
No joy, paper tiger - the issue isn't that my policies are missing - the listed gpt.ini file *does* exist at \\server\sysvol.

The issue is that the domain-named share access point "\\domain.local" does not exist, so the sysvol share is not available using that UNC path (\\domain.local\sysvol).

0
 
LVL 8

Assisted Solution

by:PaperTiger
PaperTiger earned 50 total points
ID: 22843328
read the last post.
0
 

Accepted Solution

by:
Dynatics earned 0 total points
ID: 22843657
Clients started having some other issues, so I had to reboot the server and - magic - the FRS share corrected itself.

\\domain.local is now available.
0

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now