Hidden command stsadm-o deleteconfigurationobject-id {GUID}

Problem description

==============

Recently, a problem occurs: An infopath form template is always in the installing status after being uploaded, and a new error is uploaded. The interface cannot be deleted, and the stsadm removeformtemplate cannot be deleted, activate also reports an error.

 

At the DB level (the target is Config DB), try to find the form-related objects and find the form type (Microsoft. office. infoPath. server. administration. formTemplate) Many related objects are missing. the types of these objects include:

A. SPSolution

B. SPPersistedFile

C. SPFeatureDefinition

D. Microsoft. Office. InfoPath. Server. Administration. PersistedString

 

The tool used here is shared with you previously

 

We are worried about how we can get rid of this form object in the wrong state. Everyone knows what serious consequences do we dare to manually modify the sharepoint database.

A friend suggested that there was a hidden stsadm command called deleteconfigurationobject, which may be applicable.

After a series of tests, I found that this command is suitable for my scenario. I deleted the problematic form object and uploaded the form template again to solve the problem.

Note that this command is hidden because it is very dangerous. Because there are many data entries in the SharePoint database that reference each other, killing an object will inevitably destroy some associations.

Therefore, before running this command, back up all the databases.

In this case, the problem is recovered.

References

================

The uninitialized ented "deleteconfigurationobject" parameter

Http://weblogs.asp.net/bsimser/archive/2009/07/06/the-undocumented-deleteconfigurationobject-parameter.aspx