AD problem in Server 2003, Userenv Event ID 1053 problem
 




IT Certification FAQ

 
|
Home
|
Microsoft
|
CISCO
|
CompTIA
|
Exam/Study FAQ
|
Employment FAQ
| Links  | Forums  |
Book Reviews


FAQFAQ  SearchSearch  MemberlistMemberlist  UsergroupsUsergroups  RegisterRegister  ProfileProfile  Log in to check your private messagesPrivate messages  Log inLog in

AD problem in Server 2003, Userenv Event ID 1053 problem

 
Post new topic   Reply to topic    Forum Index -> microsoft.public.windows.server.active_directory
Author Message
dtremain
Guest





PostPosted: Sat May 13, 2006 6:40 am    Post subject: AD problem in Server 2003, Userenv Event ID 1053 problem Reply with quote

I need some help with a problem that I’m starting to see at a few different
client networks. I’m seeing in the application logs that I’m encountering a
Userenv error, and I can’t seem to come to a resolution to the problem. Both
start with the following error that seems to take place every 5 minutes –

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 5/2/2006
Time: 11:02:33 PM
User: NT AUTHORITY\SYSTEM
Computer: SIBLINGSERVER
Description:
Windows cannot determine the user or computer name. (Not enough storage is
available to complete this operation. ). Group Policy processing aborted.

With all of the research I’ve done I find that there could be a problem with
DNS, but in both places I’ve rebuilt the local DNS, and though it solved the
errors that were showing in the DNS logs it hasn’t stopped the problem from
appearing in the App log. I know for sure that there is plenty of room on
the server to complete the operation.

When all of this starts the printing goes down – seems all of the other
functions of the network seem to be fine and running good – but to cure the
issue the server needs to be rebooted, and in both locations the problem
starts within 2 days.

Is this maybe a problem that is appearing in MS Server 2003 with others
also? I can’t seem to find a solution to the problem, as others seem to have
had the problem in the past but with no definitive resolution.

I’ve read that reconstructing AD might solve this problem but is seems like
a lot of work for a silly little error. Is there maybe a hotfix for this
problem?

Any help would be greatly appreciated.
Back to top
wickydog
Guest





PostPosted: Sat May 13, 2006 8:26 am    Post subject: RE: AD problem in Server 2003, Userenv Event ID 1053 problem Reply with quote

Seems that your AD server is out of capacity. Could you check how much disk
space it still have?

"dtremain" wrote:

Quote:
I need some help with a problem that I’m starting to see at a few different
client networks. I’m seeing in the application logs that I’m encountering a
Userenv error, and I can’t seem to come to a resolution to the problem. Both
start with the following error that seems to take place every 5 minutes –

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 5/2/2006
Time: 11:02:33 PM
User: NT AUTHORITY\SYSTEM
Computer: SIBLINGSERVER
Description:
Windows cannot determine the user or computer name. (Not enough storage is
available to complete this operation. ). Group Policy processing aborted.

With all of the research I’ve done I find that there could be a problem with
DNS, but in both places I’ve rebuilt the local DNS, and though it solved the
errors that were showing in the DNS logs it hasn’t stopped the problem from
appearing in the App log. I know for sure that there is plenty of room on
the server to complete the operation.

When all of this starts the printing goes down – seems all of the other
functions of the network seem to be fine and running good – but to cure the
issue the server needs to be rebooted, and in both locations the problem
starts within 2 days.

Is this maybe a problem that is appearing in MS Server 2003 with others
also? I can’t seem to find a solution to the problem, as others seem to have
had the problem in the past but with no definitive resolution.

I’ve read that reconstructing AD might solve this problem but is seems like
a lot of work for a silly little error. Is there maybe a hotfix for this
problem?

Any help would be greatly appreciated.
Back to top
dtremain
Guest





PostPosted: Sat May 13, 2006 8:38 am    Post subject: RE: AD problem in Server 2003, Userenv Event ID 1053 problem Reply with quote

On one server I have 57.4 gig left on the C partition and on the other I have
over 30 gig. Like I said, I know for sure there is more than enough space to
complete the operations. There is just no possible way I am out of space.

"wickydog" wrote:

Quote:
Seems that your AD server is out of capacity. Could you check how much disk
space it still have?

"dtremain" wrote:

I need some help with a problem that I’m starting to see at a few different
client networks. I’m seeing in the application logs that I’m encountering a
Userenv error, and I can’t seem to come to a resolution to the problem. Both
start with the following error that seems to take place every 5 minutes –

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 5/2/2006
Time: 11:02:33 PM
User: NT AUTHORITY\SYSTEM
Computer: SIBLINGSERVER
Description:
Windows cannot determine the user or computer name. (Not enough storage is
available to complete this operation. ). Group Policy processing aborted.

With all of the research I’ve done I find that there could be a problem with
DNS, but in both places I’ve rebuilt the local DNS, and though it solved the
errors that were showing in the DNS logs it hasn’t stopped the problem from
appearing in the App log. I know for sure that there is plenty of room on
the server to complete the operation.

When all of this starts the printing goes down – seems all of the other
functions of the network seem to be fine and running good – but to cure the
issue the server needs to be rebooted, and in both locations the problem
starts within 2 days.

Is this maybe a problem that is appearing in MS Server 2003 with others
also? I can’t seem to find a solution to the problem, as others seem to have
had the problem in the past but with no definitive resolution.

I’ve read that reconstructing AD might solve this problem but is seems like
a lot of work for a silly little error. Is there maybe a hotfix for this
problem?

Any help would be greatly appreciated.
Back to top
wickydog
Guest





PostPosted: Sun May 14, 2006 9:47 am    Post subject: RE: AD problem in Server 2003, Userenv Event ID 1053 problem Reply with quote

What is the patches level of Windows 2003? Check it out:

http://support.microsoft.com/default.aspx?scid=kb;en-us;883271
http://support.microsoft.com/?kbid=839880

Thanks and Regards
Jacky





"dtremain" wrote:

Quote:
On one server I have 57.4 gig left on the C partition and on the other I have
over 30 gig. Like I said, I know for sure there is more than enough space to
complete the operations. There is just no possible way I am out of space.

"wickydog" wrote:

Seems that your AD server is out of capacity. Could you check how much disk
space it still have?

"dtremain" wrote:

I need some help with a problem that I’m starting to see at a few different
client networks. I’m seeing in the application logs that I’m encountering a
Userenv error, and I can’t seem to come to a resolution to the problem. Both
start with the following error that seems to take place every 5 minutes –

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 5/2/2006
Time: 11:02:33 PM
User: NT AUTHORITY\SYSTEM
Computer: SIBLINGSERVER
Description:
Windows cannot determine the user or computer name. (Not enough storage is
available to complete this operation. ). Group Policy processing aborted.

With all of the research I’ve done I find that there could be a problem with
DNS, but in both places I’ve rebuilt the local DNS, and though it solved the
errors that were showing in the DNS logs it hasn’t stopped the problem from
appearing in the App log. I know for sure that there is plenty of room on
the server to complete the operation.

When all of this starts the printing goes down – seems all of the other
functions of the network seem to be fine and running good – but to cure the
issue the server needs to be rebooted, and in both locations the problem
starts within 2 days.

Is this maybe a problem that is appearing in MS Server 2003 with others
also? I can’t seem to find a solution to the problem, as others seem to have
had the problem in the past but with no definitive resolution.

I’ve read that reconstructing AD might solve this problem but is seems like
a lot of work for a silly little error. Is there maybe a hotfix for this
problem?

Any help would be greatly appreciated.
Back to top
Display posts from previous:   
Post new topic   Reply to topic    Forum Index -> microsoft.public.windows.server.active_directory All times are GMT
Page 1 of 1

 

Copyright © 2002-2006 Web-S-Sense Pty. Ltd. All rights reserved.

Powered by phpBB
Advertising | Policies/Disclaimers | Contact us | Link to us


Featured Sites: Free Antivirus and Antispyware Info | Free PC Support | MCSE Directory