1058 and 1030 App log errors for a specific user/admin

[guest]

I am seeing App log errors 1058 and 1030 for a specific user when that user logs in on an hourly basis. When I look at the GUID I see that the error refers to the Default Domain Policy. When looking at KB 888943 I checked the gPCFileSysPath of the System policy and it has the correct domain and path to the group policies. This error is only logged for the specific user ITadmin and no others. Why would a specific user log this error? I have since moved this specific who is also a domain admin to a different OU called everyone where all other users are located but this has not resolved this issue.

Here is an example of the error:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 12/21/2011
Time: 9:57:53 AM
User: RWP\itadmin
Computer: SERVERNEW
Description:
Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=rwp,DC=com. The file must be present at the location <\\rwp.com\sysvol\rwp.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Logon failure: unknown user name or bad password. ). Group Policy processing aborted.

What else can I check or change to prevent this error?

[guest]

According to your information, after doing some research, I found these errors may occur if the Winlogon process tries to process group policies before other components are running. To correct this problem, you can perform the below steps.



Steps 1

=======

obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 (http://support.microsoft.com/kb/889100 ) How to obtain the latest service pack for Windows Server 2003



Steps 2

=======

After you have applied the above service pack, follow these steps:



1. Click Start, click Run, type regedit in the Open box, and then click OK.

2. In Registry Editor, locate the following registry subkey:

a. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

3. If the WaitForNetwork entry is missing, you must add the entry. To do this, follow these steps:

a. Right-click the Winlogon subkey, click New, and then click Dword Value.

b. In the Value name box, type WaitForNetwork.

4. Right-click WaitForNetwork, and then click Modify.

5. In the Edit DWORD Value dialog box, in the Value Data box, type 1, and then click OK.

6. Close Registry Editor.

[guest]

Thanks. The registry is set to that value, after running a few gpdupdate /force the group policy is working again for that user. Must have been some bad cached information for that login, as it seems to be working again.



Server is running SP2.