New answers tagged

0

I deployed a bunch of columns and deployed them using a feature. Afterwards I retracted that feature and created a new feature to deploy them with same ID (GUID) but different internal names. That caused me this error. I had to change all my IDs to fix this issue.


0

When you use a Sandbox Solution in your site collection, By default SharePoint set the Resource Quota 300 server resources. Same thing also applies to office 365. This capability is critical to maintaining the stability of the farm.Quotas for sandboxed solutions are measured in units of resource "points." Resource points are a calculated value that ...


0

I think the problem really comes from a resource quota being exceeding at the site collection level. Note that the error message mentions the "daily quota". So maybe you had several tries in the day, each resulting in increasing the resource counter (if you had unhandled errors for instance). So, the first suggestion it to try by increasing the quota for ...


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.


0

If you want to get Approval, Collect Feedback, and Collect Signatures Workflows in the list. Then you need to activate a Workflows Site Collection Feature. Follow below steps Navigate to your Site Collection Go to Site Settings Find the Site Collection Administration section, Under it click on Site collection features Scroll down at bottom, find and ...


0

Check in 'Manage Site Features' as well - double check all workflow related such as Workflow Task Content Type - to this point... I am not a big fan of the workflows in sharepoint that are included out of the box - they use tasks and become complicated / and not end user friendly. Prefer, instead, to use a sharepoint designer workflow that leverages ...



Top 50 recent answers are included