A custom operation that you create for the Stsadm.exe utility in SharePoint Server 2010 or in SharePoint Foundation 2010 is not enumerated

Article translations Article translations
Article ID: 979507 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

In Microsoft SharePoint Server 2010 or in Microsoft SharePoint Foundation 2010, you create a custom operation for the Stsadm.exe utility by using the method that is described in the following MSDN Web site:
How to extend the Stsadm utility
When you run the Stsadm.exe utility without any parameters to enumerate all the operations, the custom operation is not enumerated. This problem occurs after you perform one of the following actions:
  • You deploy an extension built for Microsoft Office SharePoint Server 2007 to a SharePoint Server 2010 farm.
  • You perform an in-place upgrade in a SharePoint Server 2007 environment in which you have deployed an extension.

CAUSE

This problem occurs because the XML registration file of the custom operation is not copied automatically to the %ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG directory.

WORKAROUND

To work around this problem, manually copy the XML registration file of the custom operation to the %ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG directory.

Properties

Article ID: 979507 - Last Review: September 12, 2011 - Revision: 4.0
APPLIES TO
  • Microsoft SharePoint Server 2010
  • Microsoft SharePoint Foundation 2010
Keywords: 
kbtshoot kbexpertiseadvanced kbsurveynew kbprb KB979507

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com