Hot answers tagged

3

No it doesn't. The i:0#.w| part is an internal signature for SharePoint that identifies the authentication type as claims rather than the soon to be deprecated classic authentication. Update Usually this isn’t a problem, but if you have the object cache accounts without the initial claims signature all users will get access denied to the object cache (...


3

You can use both namespaces, you just have to set up a way of disambiguating which WebPart class you are referring to when you refer to it. One way of doing that would be to include the entire namespace when you refer to the WebPart class, i.e.: public partial class VisualWebPart1 : System.Web.UI.WebControls.WebParts.WebPart Another option, and the first ...


2

Yes, it does matter. Especially in the Object Cache Configuration( Super User & Super Reader).If your webapplication configured as claims based authentication then this is import piece. Make Sure your Account in Web Application Properties( Via PowerShell) have the same format i.e cliams|domain\username, as they are in the Web Application's Policy( from ...


2

To avoid these errors, I created a new SharePoint document folder, and named it something similar. Then use the explorer view to copy over the files and folders then delete the original one and rename the new one to the same name as the original one.


1

Follow these steps: Navigate to C:\inetpub\wwroot\wss\Virtual Directories\your web app's virtual directory here. You can also open IIS Expand Sites Right click on your SharePoint site Choose explore proceed to step 2 Copy and paste the web.config file (making a backup) Open web.config using notepad Search for “CallStack” , set this equal to true Search ...



Only top voted, non community-wiki answers of a minimum length are eligible