Failed to open the Group Policy Object and can't access sysvol from domain?

Discussion in 'Windows Small Business Server' started by Asaf, Apr 11, 2008.

  1. Asaf

    Asaf Guest


    I have a problem that in Event log Userenv error appear one with ID 1030 and
    one with ID 1058.

    Also when trying to access \\mydomain.local\sysvol I get the error "The
    network path was not found" where I can access the sysvol when typing

    When trying also to run dcpol.msc I get the error "Failed to open the Group
    Policy Object. You may not have appropriate rights".

    My server is a fresh SBS 2003 install with all latest service packs and
    patches from windows update.

    I have looked the internet for solution but can't find one.

    Thanks for any help,
    Asaf, Apr 11, 2008
    1. Advertisements

  2. Asaf

    Matabra Guest


    Looks like a problem with NTFrs or DFS or even DNS as you shoudl be able to
    access the sysvol from the \\mydomain.local. This is where GPO's look aswell
    which explains the error.

    Are there any errors in the event logs for those that might explain it?


    Matabra, Apr 11, 2008
    1. Advertisements

  3. Asaf

    Asaf Guest

    Hi Matt,

    Error descripation is:

    Event Type: Error
    Event Source: Userenv
    Event Category: None
    Event ID: 1058
    Date: 11/04/2008
    Time: 14:19:01
    Computer: SERVER1
    Windows cannot access the file gpt.ini for GPO
    The file must be present at the location
    (Windows cannot find the network path. Verify that the network path is
    correct and the destination computer is not busy or turned off. If Windows
    still cannot find the network path, contact your network administrator. ).
    Group Policy processing aborted.

    Asaf, Apr 11, 2008
  4. Asafa,

    Search Google for this:
    event id 1030

    You will get a ton of hits that i many cases seems to be suiteble.
    Henrik \(Hear\), Apr 11, 2008
  5. Asaf

    Asaf Guest

    Hi Henrik,

    I did search for it in Google but didn't found any solution for that

    Asaf, Apr 11, 2008
  6. Asaf

    Jim Behning Guest

    So probable resolution is Microsoft article 887303 step 2 regedit a few smb
    settings without rebooting the server. I knew I suffered this before. It has
    been years and Microsoft PSS helped me fix it. After making those edits I can
    access shares without a password problem. Now I am off to open up Group
    Policy to fix SMB signing.
    Jim Behning, Apr 11, 2008
  7. Asaf

    bboklewski Guest

    I have the same issue and in the past another company MS fixed this issue with the SMB signing as well. I am supporting an old 2003 DC server and I am having the same issue and SMB does seem to have fixed the issue, been at it for about 24 hours trying to get this resolved.
    bboklewski, Apr 22, 2014
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.