Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1306
  • Last Modified:

Windows cannot determine the user or computer name. (The remote procedure call failed. ). Group Policy processing aborted.

I have SQL server 2005 64 bit on Windows 2003 64 bit. in cluster environment. its the active server caues the problem.
SQL server performance is going down a lot.

Taskmanager --> Page file memory usage show 9.55 Gb almost full.

the problem started after installed the microsoft security patches for windows 2003 64 bit.

below is the one i found on Event viewer. lot of entries with this error.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date:  6/18/2008
Time:  5:08:16 PM
User:  NT AUTHORITY\SYSTEM
Computer: WTRSFCLUST19002
Description:
Windows cannot determine the user or computer name. (The remote procedure
call failed. ). Group Policy processing aborted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Its happening in Production environment. any help on this is greatly appreciated.

Thank you

0
Sarathib78
Asked:
Sarathib78
1 Solution
 
Sarathib78Author Commented:
yes. i already read it. nothing looks solution to my specific problem.


This server is a Active cluster -SQL server 2005 64 bit. and it holds a lot of data. have enough free space. about 40GB.
and the problem started happen after we applied the security patch.

Addtional information : this server is  "dedicated server" from a  3rd party company, behind the nokia firewall.
0
 
CloudHeroff7Commented:
I would Suggest Uninstalling the specific update untill you find an appropriate solution.
Not Alll Microsoft updates are golden, as with any update test it first and if it upset your servers stomach undo changes and wait for a later update. Goood Luck
0
 
ChiefITCommented:
You are number three.

A problematic CA and old data in the Active Directory PKI Container may also cause this problem on a Windows 2003 domain. Use PKIview.msc from the Windows 2003 Rescource kit to check the status of the CA.
1) Install rktools (rootkit tools), run the Microsoft Management Console, and add the standalone snap-in "Enterprise PKI".
2) Expand the console tree in the scope pane, click on your CA, and verify that all entries report OK.
0
 
Sarathib78Author Commented:
my Network admin found it as DNS problem with its domain server. and he fixed it.
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.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now