Tag Info

New answers tagged

2

The list instance was created on the site on which you activated the feature. Your list should be in a web-scoped feature. Site-scoped features are for site scoped things like master pages, content types and web parts. They will not cause web-scoped things like lists to become automatically provisioned on subwebs. This means every subsite you want the ...


0

If the Scope is "Site" it creates only at root site level, change it to "Web" and deploy it. Please deactivate, uninstall and retract completely before you deploy your changes.


0

If code is running too long the asp.net feature activation could be terminated. Try to edit web.config in 14 hive < location path="_layouts/ManageFeatures.aspx" > < system.web > < httpRuntime executionTimeout="3600" / > < /system.web> < /location > I just set the time for one hour it's should be enough.


1

Use the C# following code to modify the web.config: string content; string WebServiceServer = "example.com"; // <=== your host-name here using (TextReader tr = File.OpenText(bindingFilePath)) { content = String.Format(tr.ReadToEnd(), WebServiceServer); } SPWebConfigModification modification = new SPWebConfigModification("system.serviceModel", ...


0

Fixed the problem changing the template property in the list instance element.xml and in the list element.xml, as shown in the pictures below: The files In the list instance Element.xml I changed the TemplateType from 100 (general list type) to 1000 (a number that doesn't represent any default SharePoint template type). In the list Element.xml I also ...


0

There is no need to edit or run any sql database query or operation. the most simple way is to use powershell and the error is removed. As shown, the message reports a content database name (SharePoint_Content_Portal) and feature ID (8096285f-1463-42c7-82b7-f745e5bacf29), but not the sites or site collections where the feature exists. In addition to this, ...


0

I usually succeed using this script <# 1. To run the script - add your GUID on the last line of this script Example: [MissingFeature] feature:ID [8307a780-2546-f10b-551f-0e692d0fce39] 2. Add your SqlServer name and instance on the last line of this script. #> if ($ver.Version.Major -gt 1) {$host.Runspace.ThreadOptions = ...


0

This is a very handy tool in such scenarios: Feature Administration and Cleanup tool


0

Try below var feature = null; if(spSite.Features != null) { feature = spSite.Features.SingleOrDefault(f => (f.Definition != null && f.Definition.DisplayName != null && f.Definition.DisplayName.ToLower().Equals(strFeatureName)); }


1

I needed to configure service Application Associations "WorkFlow Service Application Proxy" Go to Appliaction Management - Manage web appliactions Select Web Appliaction Service Connections Check "WorkFlow Service Application" In this site have another solution that I really worked. ...


0

I have resolved it!! As powershell did not help me. I have nothing left other than manually digging database. So I have searched WSS_Content database and found those entries in WSS_Content.dbo.CustomActions table. Removing those fixed the issue. We have deleted entries whose FeatureId is 00000000-0000-0000-0000-000000000000 Not sure if this is the ...


1

Try adding: context.Response.AddHeader("content-disposition", "attachment;filename=" + file.Name);


0

You do NOT need and you should NOT call web.update(). This mean that you save this property to the database. To disable site collection feature, you do not need SPWeb instance also. If you have permissions to manage features of the site, you also do not need new SPSite object instance. Try to write you code like, this: if (SPContext.Current.Site != null) ...


1

In my solution I had a event receiver and some content type definition. I splitted it in two different solutions (one with event receiver and other with definitions) and now it is working. Actually I do not know why (I did not change code at all), sad story.


0

Try with Enable-SPFeature xxx -Force


-1

Kill the vssphost4.exe process, do an iisreset and try again.



Top 50 recent answers are included