The Requested Operation Could Not Be Run on the Server

Being a Systems Administrator, I often am having to move files, for one reason or another, from server to server or workstation to workstation. This is often a mundane task that can be accomplished by mapping a drive or navigating to the source/destination via UNC path.

We had recently stood up a Windows Server 2008 R2 server in order to begin transferring our file server off of Novell onto the Windows Platform. This was our first server to have the latest version of of the Windows OS and the migration could not have went smoother.

For a couple of months we had been hosting users home directories and department directories on this server. One day, while logged onto the 2008 R2 server, the need came up for me to transfer files from an older Windows Server 2003 box. But something went wrong. I discovered that my Windows Server 2008 R2 server was unable to communicate with Windows Server 2003 or Windows XP even though these operating systems could see this box.

Having thought this was just a communication problem with the domain, I removed it from Active Directory.  Big mistake.  Once it was off of the domain and I could no longer communicate with Server 2003 boxes, I could notr add it to the Domain since our Domain Controllers are also Windows Server 2003 boxes.

I immediately began moving the contents of this server over to another function Windows Server 2008 R2 server using Robocopy.  This simple command line tool saved my job since I was able to quickly move the contents and their permissions over.  I soon had my contingency plan in place so I could work on restoring service to my bad server.

ERROR

When attempting to perform Group Policy and Active Directory commands on the server a message box would display the following message:

“The requested operation could not be run on the server”

The System Event Log contained the following error messages:

Log Name: System
Source: Microsoft-Windows-DNS-Client
Event ID: 1006
Task Category: None
Level: Warning
User: LOCAL SERVICE
Computer: server.domain
Description:
The client was unable to validate the following as active DNS server(s) that can service this client. The server(s) may be temporarily unavailable, or may be incorrectly configured. DNS IP Address

Log Name: System
Source: Microsoft-Windows-GroupPolicy
Event ID: 1058
Task Category: None
Level: Error
User: SYSTEM
Computer: server.domain
Description:
The processing of Group Policy failed. Windows attempted to read the file \\domain\sysvol\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.

Log Name: System
Source: LsaSrv
Event ID: 40961
Task Category: None
Level: Warning
User: SYSTEM
Computer: server.domain
Description:
The Security System could not establish a secured connection with the server ldap/servername/domain. No authentication protocol was available.

Log Name: System
Source: Microsoft-Windows-GroupPolicy
Event ID: 1006
Task Category: None
Level: Error
User: SYSTEM
Computer: server.domain
Description:
The processing of Group Policy failed. Windows could not authenticate to the Active Directory service on a domain controller. (LDAP Bind function call failed). Look in the details tab for error code and description.

CAUSE
Upon looking into the registry, I discovered values were missing from the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation key. Once we copied the key from a working server, the server then began registering error 0x800704cf when attempting to access domain controller. After researching this new error, I found that File and Print Sharing Services on the NIC were corrupt.

SOLUTION
I performed the following steps to resolve this issue:

  1. Copied HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation from another Windows Server 2008 R2 box.
  2. Rebooted the Server.
  3. The server then began registering error 0x800704cf when attempting to access the domain
  4. Uninstalled File and Print Sharing Service from the Network Interface Cards.
  5. Rebooted the server
  6. Installed File and Print Sharing Service on the Network Interface Cards.

This was quite the difficult problem to troubeshoot since the Event IDs and error messages I was receiving were leading me in the wrong direction from the solution.  I do have to admit that I alone did not resolve this issue, but had the assistance of Microsoft Support over email.  Even though, they had no answer to what was causing it, they did lead me to copy the registry key from one server to another which ultimately lead the correct error message to surface.

I hope I never experience this particular issue again.  But I plan on keeping this information close by so it is never forgotten.

Advertisements
This entry was posted in Windows Server and tagged , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s