D
Daniel_A
Hi, i'm having problems with my server, i'm receiving a lot of 1030 and 1058
errors on the event viewer.
When i check support.microsoft.com i found article 314494 that talks about a
problem with DFS client. This is not my problem because we are not using
DFS.
Anybody have a clue of this one?
i copy the event messages 1030 and 1058:
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 2/8/2002
Time: 7:25:40 AM
User: NT AUTHORITY\SYSTEM
Computer: MYCOMPUTER
Description: Windows cannot access the file gpt.ini for GPO
CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=lcds,DC=l
ab
The file must be present at the location
\\lcds.lab\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}
(Access is denied) Group Policy processing aborted.
Event Type: Error
Event Source: SceCli
Event Category: None
Event ID: 1030
Date: 2/8/2002
Time: 7:30:46 AM
User: N/A
Computer: MYCOMPUTER
Description: Windows cannot query for the list of Group Policy objects. A
message that describes the reason for this was previously logged by the
policy engine.
Thanks!
Daniel A.
errors on the event viewer.
When i check support.microsoft.com i found article 314494 that talks about a
problem with DFS client. This is not my problem because we are not using
DFS.
Anybody have a clue of this one?
i copy the event messages 1030 and 1058:
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 2/8/2002
Time: 7:25:40 AM
User: NT AUTHORITY\SYSTEM
Computer: MYCOMPUTER
Description: Windows cannot access the file gpt.ini for GPO
CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=lcds,DC=l
ab
The file must be present at the location
\\lcds.lab\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}
(Access is denied) Group Policy processing aborted.
Event Type: Error
Event Source: SceCli
Event Category: None
Event ID: 1030
Date: 2/8/2002
Time: 7:30:46 AM
User: N/A
Computer: MYCOMPUTER
Description: Windows cannot query for the list of Group Policy objects. A
message that describes the reason for this was previously logged by the
policy engine.
Thanks!
Daniel A.