After installing a 3rd party solution to my production server (yes we did test it w/o problems), my solutions gallery stoped having the abilty to activate ANY solutions.  From site templates to other 3rd party solutions.  The 3rd party (whom we paid a decent chunk of money to) admitted that this happend from time to time for "reasons they don't understand".  Uninstalling thier solutions has still left my site broken.

When I try to activate a solution I get the always helpful "An unexpected error has occured" (with the corrilation ID).  I've posted the ULS logs at the end of this message. 

I can't afford to open a ticket with microsoft and it does not look like the 3rd party is going to be of much help.  Anyone have any ideas of what my options are?

I have seen postings where people reinstall sharepoint over thier current install as a repair?  Build a brandnew site and then run restore-spsite?  I'm no DBA, but I do have a stack of content db backups as well?  Is there a way to fix the template files that seem to be corrupted (template\xml\wss.xsd)?

Thanks for any advice or insight,
Brian :-)

ULS LOG:

Name=Request (POST:https://sharepoint.mysite.com:443/_catalogs/solutions/Forms/Activate.aspx?Op=ACT&ID=45&Source=https%3A%2F%2Fsharepoint%2Emysite%2Ecom%2F%5Fcatalogs%2Fsolutions%2FForms%2FAllItems%2Easpx&RootFolder=%2F%5Fcatalogs%2Fsolutions&IsDlg=1)
Site=/
Leaving Monitored Scope (PostResolveRequestCacheHandler). Execution Time=9.38331547724641
Solution Deployment : Looking for 'ReceiverAssembly' attribute in manifest root node for solution 'Room Equipment Reservations.wsp'.
Solution Deployment : Looking for 'ReceiverClass' attribute in manifest root node for solution 'Room Equipment Reservations.wsp'.
Solution Deployment : Missing one or more of the following attributes from the root node in solution Room Equipment Reservations.wsp: assembly '', type ''.
Invalid SharePoint XSD: template\xml\wss.xsd (line 298 char 6)
Invalid SharePoint XSD: template\xml\wss.xsd (line 298 char 6)
System.Xml.Schema.XmlSchemaException: 'anyAttribute' must be the last child.    at Microsoft.SharePoint.Utilities.SPUtility.XsdValidationCallBack(Object sender, ValidationEventArgs evtargs)     at System.Xml.Schema.XmlSchemaSet.ParseSchema(String targetNamespace, XmlReader reader)     at System.Xml.Schema.XmlSchemaSet.Add(String targetNamespace, String schemaUri)     at Microsoft.SharePoint.Utilities.SPUtility.GetSharePointXmlSchemaSet()     at Microsoft.SharePoint.Utilities.SPUtility.XsdValidateXml(XmlTextReader xmlStreamReader, String friendlyName, String pathXsdFile, String tagExpectedRootNode, ValidationEventHandler xsdValEventHandler)     at Microsoft.SharePoint.Administration.SPSolutionPackage.SolutionFile.ValidateFeatureXmlFile(String rootTagElement)     at Microsoft.SharePoint.Administration.SPSolutionPackage.AddFeatureElements(XmlNode root, String strFeatureDirRelativeToCabFile, String strFeatureXmlFilename, Guid featureId)     at Microsoft.SharePoint.Administration.SPSolutionPackage.WspSolutionFeature.ProcessFeatureXml()     at Microsoft.SharePoint.Administration.SPSolutionPackage.InitSolutionFeatures(XmlNode root)     at Microsoft.SharePoint.Administration.SPSolutionPackage.ProcessSolutionManifest()     at Microsoft.SharePoint.Administration.SPSolutionPackage.Load()     at Microsoft.SharePoint.Administration.SPSolutionLanguagePack.CreateSolutionPackage(SPRequest request, String name, String signature, Byte[] fileBytes)     at Microsoft.SharePoint.SPUserSolutionCollection.<>c__DisplayClass1.<AddOrUpgrade>b__0()     at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)     at Microsoft.SharePoint.SPUserSolutionCollection.AddOrUpgrade(SPListItem item, SPUserSolution existingSolution)     at Microsoft.SharePoint.SPUserSolutionCollection.Add(Int32 solutionGalleryItemId)     at Microsoft.SharePoint.WebControls.SolutionItemButton.ActivateItem()     at Microsoft.SharePoint.WebControls.SPLinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)     at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Leaving Monitored Scope (Request (POST:https://sharepoint.mysite.com:443/_catalogs/solutions/Forms/Activate.aspx?Op=ACT&ID=45&Source=https%3A%2F%2Fsharepoint%2Emysite%2Ecom%2F%5Fcatalogs%2Fsolutions%2FForms%2FAllItems%2Easpx&RootFolder=%2F%5Fcatalogs%2Fsolutions&IsDlg=1)). Execution Time=368.344580107248

Server 2008R2 runningSharePoint Foundation 2010 SP1 and Server 2008R2 running SQL2008R2 SP1

 

 

It appears that SharePoint still thinks the 3rd party solution (wsp) is still active, but is missing files.  How did you retract your solution? 

You may either have to redeploy and activate the solution first and then remove it again. I suggest you do this using powershell. Below is a sample of how to do this:

This will uninstall the solution on all of your servers - you will get errors if it is already uninstalled which is fine.

 

Uninstall-SPSolution -Identity "Room Equipment Reservations.wsp"

 

This will install the solution, and assumes the solution assemblies live in the GAC:

Install-SPSolution -Identity "Room Equipment Reservations.wsp"  -GacDeployment -Force

This will install and activate the features (there may be more than one) - to get the names of the features if you do not know them look in the "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES" folder and look for features that begin like the wsp name above. You also will need the url for the site:

Install-SPFeature "[Name of the Feature]" -Force
Enable-SPFeature "[Name of the Feature]" -Url "[Url for the web site]" -Force  

Then to deactivate and uninstall each feature use these commands:

Disable-SPFeature "[Name of the Feature]" -Url "[Url for the web site]" -Force
Uninstall-SPFeature "[Name of the Feature]" -Force

Now uninstall the solution again:

 

Uninstall-SPSolution -Identity "Room Equipment Reservations.wsp"<br/>

 

I hope this helps.

 

I am having the same issue and applied a simple fix.

Open the file "wss.xsd" at below path
"C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML"

Find all "<xs:anyAttribute namespace="##other" processContents="lax" />" in the file and verify that it is the last child if not move it to the last position . see below piece of code.

    <xs:attribute name="PrependId" type="TRUEFALSE" />
    <xs:attribute name="DisplaceOnUpgrade" type="TRUEFALSE" />
    <xs:attribute name="UserSelectionMode" type="xs:string" />
    <xs:attribute name="UserSelectionScope" type="xs:int" />
    <xs:attribute name=NoCrawl type=TRUEFALSE />
    <xs:anyAttribute namespace="##other" processContents="lax" />   
  </xs:complexType>


In my case code was like -

    <xs:attribute name="PrependId" type="TRUEFALSE" />
    <xs:attribute name="DisplaceOnUpgrade" type="TRUEFALSE" />
    <xs:attribute name="UserSelectionMode" type="xs:string" />
    <xs:attribute name="UserSelectionScope" type="xs:int" />
    <xs:anyAttribute namespace="##other" processContents="lax" />   
    <xs:attribute name=NoCrawl type=TRUEFALSE />
  </xs:complexType>


Changing the position of anyAttribute resolved the issue :)