Win2003 with XP's: GetUserNameEx failed with 14.

[John Doe]

We have a strange problem, which we can't solve. We have tried to
look different documents and newsgroups but we haven't find anything
useful. Any ideas would be greatly appreciated.


PROBLEM

We have about 50 computers in our organisation. All computers have
been updated to XP. We have also two Windows Server 2003's which are
domain controllers.

Everything works fine, but now and then (about after 6-10 days) some
XP get following error:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 6/7/2004
Time: 13:12:33 PM
User: NT AUTHORITY\SYSTEM
Computer: MYCOMP
Description:
Windows cannot determine the user or computer name. (Not
enough storage is available to complete this operation. ).
Group Policy processing aborted.

or

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 6/2/2004
Time: 11:34:23 PM
User: NT AUTHORITY\SYSTEM
Computer: MYCOMP
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."

After that those computers can't access any services in domain. Those
errors keep coming, but after boot everything works fine for awhile.

This happens to every computer different times.

This is a cut from one problem XPs UserEnv.log:


USERENV(1fc.1e0) 16:37:26:143 ProcessGPOs:
USERENV(1fc.1e0) 16:37:26:143 ProcessGPOs:
USERENV(1fc.1e0) 16:37:26:153 ProcessGPOs: Starting computer Group
Policy (Background) processing...
USERENV(1fc.1e0) 16:37:26:163 ProcessGPOs:
USERENV(1fc.1e0) 16:37:26:163 ProcessGPOs:
USERENV(1fc.1e0) 16:37:26:173 EnterCriticalPolicySection: Machine
critical section has been claimed. Handle = 0x8a4
USERENV(1fc.1e0) 16:37:26:183 ProcessGPOs: Machine role is 2.
USERENV(1fc.1e0) 16:37:26:193 PingComputer: Adapter speed 10000000 bps
USERENV(1fc.1e0) 16:37:26:224 PingComputer: First time: 25
USERENV(1fc.1e0) 16:37:26:464 PingComputer: Second time: 223
USERENV(1fc.1e0) 16:37:26:494 PingComputer: First time: 23
USERENV(1fc.1e0) 16:37:26:714 PingComputer: Second time: 219
USERENV(1fc.1e0) 16:37:26:754 PingComputer: First time: 22
USERENV(1fc.1e0) 16:37:26:974 PingComputer: Second time: 218
USERENV(1fc.1e0) 16:37:26:984 PingComputer: Transfer rate: 163 Kbps
Loop count: 3
USERENV(1fc.1e0) 16:37:26:995 ProcessGPOs: A slow link was detected.
USERENV(1fc.1e0) 16:37:30:589 ProcessGPOs: network name is 10.12.23.0
USERENV(1fc.1e0) 16:37:30:879 MyGetUserName: GetUserNameEx failed with
14.
USERENV(1fc.1e0) 16:37:30:889 MyGetUserName: Retrying call to
GetUserNameEx in 1/2 second.
USERENV(1fc.1e0) 16:37:31:580 MyGetUserName: GetUserNameEx failed with
14.
USERENV(1fc.1e0) 16:37:31:590 MyGetUserName: Retrying call to
GetUserNameEx in 1/2 second.
USERENV(1fc.1e0) 16:37:32:241 MyGetUserName: GetUserNameEx failed with
14.
USERENV(1fc.1e0) 16:37:32:251 MyGetUserName: Retrying call to
GetUserNameEx in 1/2 second.
USERENV(1fc.1e0) 16:37:32:912 MyGetUserName: GetUserNameEx failed with
14.
USERENV(1fc.1e0) 16:37:32:922 ProcessGPOs: MyGetUserName failed with 14.
USERENV(1fc.1e0) 16:37:32:922 ProcessGPOs: No WMI logging done in this
policy cycle.
USERENV(1fc.1e0) 16:37:32:932 ProcessGPOs: Processing failed with error
14.
USERENV(1fc.1e0) 16:37:32:942 LeaveCriticalPolicySection: Critical
section 0x8a4 has been released.
USERENV(1fc.1e0) 16:37:32:942 ProcessGPOs: Computer Group Policy has
been applied.
USERENV(1fc.1e0) 16:37:32:952 ProcessGPOs: Leaving with 0.
USERENV(1fc.1e0) 16:37:32:962 EnterCriticalPolicySection: Machine
critical section has been claimed. Handle = 0x8a4
USERENV(1fc.1e0) 16:37:32:992 LeaveCriticalPolicySection: Critical
section 0x8a4 has been released.
USERENV(1fc.1e0) 16:37:33:002 GPOThread: Next refresh will happen in 92
minutes

If you want, we can send you whole log.

We have tried to solve this problem with help of KB263693, but it
didn't help.

Any ideas please??

 

[femsteenkamp]

Hi

I have the sneaky suspicion that you have a application or something o
the machines that has a memory leak. This application then consumes al
resources.

At the time the user needs to log on the memmory cannot be allocate
for the logon process and the error is logged.

this should explain that after a reboot everything works fine for
time.

check in task manager ( View --> Select Columns --> Memmory usage an
memmory usage delta) and see if something looks suspect.

hope this helps a bit


-
femsteenkam