Tag Info

Hot answers tagged

2

For the sharepoint groups you getting 401, try below. Navigate to the sharepoint group settings page and set the property " Who can view the membership of the group?" to "Everyone".


1

The Farm Account, which is used for the SharePoint 2010/2013 Timer service and the Central Administration site, is highly privileged and should not be used for other services on any computers in the server farm. You need to Change the Server farm account used for other services to low privileged account. This error may vary as per the services running in ...


1

If you can browse other web applications on the server except the http://web01 then looks like something wrong with the IIS Bindings. Please make sure IIS Bindings for the web app in place If using the SSL, make sure SSL bindings & Certs attach to the web app. another possibility is AV causing the issue, try to disable it.


1

Site Owners don't necessarily have the permission to enumerate all SharePoint groups -- you should be able to enumerate all groups with a farm administrator account.


1

Try using web.Allowunsafeupdates = true; string uploadPathRoot = site2.ServerRelativeUrl + "/Lists/abc"; SPList list = web.GetList(uploadPathRoot); var fcp = new Microsoft.SharePoint.SPFileCollectionAddParameters(); fcp.Overwrite = true; web.AllowUnsafeUpdates = true; ...


1

Please try these steps Leave this page open in the browser for the app dependency table located about half way through the article: http://msdn.microsoft.com/en-ca/library/jj819804.aspx Find the app package, rename the .app file extension to .zip. Right click the .zip file and extract the contents. Open the AppManfiest.xml file in Notepad. Search for the ...


1

Try creating a website in Azure and publish the appweb file there. Then make sure that the app file is pointing to that site which will be .azurewebsites.net. Also make sure that the app has the relevent rights and permissions


1

It is not an SharePoint thing it is a ASP.Net validation thing, to protect against injection attacks. That is why you do not find anything specific for SharePoint. Regardless if it is SP or ASP.Net Web Forms the same still applies. Your Postback data needs to be valid (ASP.Net needs to know about it) The bad alternative is to set <%@ Page ...



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