I have a farm solution with a custom feature that was working fine. I added 2 more features to test something ("TestFeature1" and "TestFeature2"), and deployed the solution. I then retracted and removed the solution from the farm and deleted the site collection. I removed "TestFeature1" and "TestFeature2" from the solution in Visual Studio, packaged the solution, then added it to the farm and deployed it. Then I created a new site collection.
In the new site collection, "TestFeature1" and "TestFeature2" do not show up in the features list (as expected). However when I try to enable the original feature, it throws an error: "An error occurred while processing the request on the server. The status code returned from the server was: 0".
When I check the SP logs, it is trying to deploy the 2 test features, which throws errors because they don't exist.
System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Template\Features\TestFeature1\feature.xml'.
I have tried:
Uninstall-SPFeature TestFeature1
AND
stsadm -o uninstallfeature -id [Guid of TestFeature1]
Both say that the feature doesn't exist. I've also searched through the project in visual studio for "TestFeature1" and also for the Guid of the feature, and there is no lingering remnants of the feature.
I can't figure this one out...