Event 1053 Userenv error

Hello - we have a server that was recently DCPROMO demoted from a DC, down to a member server, and has successfully been reconnected and rejoined to the same domain on our network.  We have several applications on the machine that are working, except for one application that runs unattended jobs in Windows 2003 Server, that appears to have trouble now.  I don't see any errors related to the application jobs, however, but am having to run these job tasks manually to get them done.  The main error I see is this one below:

Event Id 1053 Userenv  User=NT AUTHORITY\SYSTEM
Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

I don't know if this is the cause of the jobs not running correctly, but it definitely is a new error.
Damian_GardnerAsked:
Who is Participating?
 
ChiefITCommented:
You are going to have to control your Windows Firewall to allow for Domain Operations. For this specific error, you have to enable "file and print sharing" .
0
 
Life1430Sr EngineerCommented:
check DNS setting on that machine You should have removed the IP of demoted DC from DNS search order of client systems
0
 
Sushil SonawaneCommented:
Please refer below article this might help you out.


(http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/9cfb6806-f009-4a82-b03c-bb7b68b27071)



1. At the command prompt, type netdiag. If any error is received, please fix it first.
 
2. Verify that the domain controller can be contacted through Domain Name System (DNS), try to access \\mydomain.com\sysvol\mydomain.com, where mydomain.com is the fully qualified DNS name of your domain.

 
 
3. Verify that you can access the domain controller by using tools such as the Active Directory Users and Computers snap-in.
 
 
 
4. At the command prompt, type gpupdate and then check Event Viewer to see if the Userenv 1053 event is logged again.
0
 
Damian_GardnerAuthor Commented:
Thanks to all for your suggestions.  It turned out that the application needed to have the Windows task jobs recreated to fix the jobs problem, and then the User event error went away after running Sysprep, and rejoining the domain.  Thank you for your efforts.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.