New answers tagged

2

IMO, the only correct handling of this problem would be to have only one VS project, building into one single WSP package. And also: one feature only. The feature that provisions files should be the one that deletes them at deactivation. It does not make sense to activate F01 and deactivate F02 to undo what F01 did! Furthermore, how F02 would be activated in ...


0

Faced simile issue and below is my situation. Your might be the same. I had 3 box in my farm one CA, and two WFE. When we browse CA we could not see one of our Web Application level feature but we see other Web Application feature. In our case WSP which was deploying invisible feature was not deployed globally. You will only see feature which is part of ...


0

SQL was incorrectly configured. Since I had no insight or permissions on the SQL server it was difficult to pin the issues on SQL. Once SQL was reconfigured, the issues disappeared. I did not reconfigure SQL and thus do not know specifically what was wrong.


2

I think the Powershell commandlets you are looking for are: Disable-SPFeature, which is the equivalent of going to the "Manage Site Features" page and clicking the "Deactivate" button. Disable-SPFeature has a Force parameter, and a URL parameter which: Specifies the URL of the Web application, site collection, or Web site to which the Feature is ...


1

I saw a similar behavior once when a feature became "orphan" following some error during a solution upgrade test in one of my development environments. Some of the info you give aren't really strict, so forgive me for my guessing, but here are some info that saved me back then. Turns out that the Uninstall-SPFeature -Identity <guid> command is the ...


0

If you want to disable Sandbox Solutions (I'm assuming that is what you mean by Sandbox), you can just stop the Sandbox service in Central Admin -> Manage Services on Server, and stop the Microsoft SharePoint Foundation Sandboxed Code Service.


1

Open the project folder You will find the "Feature" folder inside that. If you have any other .cs or .aspx files outside the folder, then it might be solution. If you don't have any thing outside of the "Feature" folder and you have files inside the "Feature" folder, then it is a FEATURE. Project can also contain the solution as well as the feature. ...


1

By looking at the Visual Studio solution (not to be confused with a SharePoint solution WSP), you can easily tell what you have: In the Visual Studio project (from the Solution Explorer of VS), if you see a "Features" folder with one or more sub-folders in it: you have a SharePoint project that builds into a SharePoint WSP package. That package contains ...



Top 50 recent answers are included