Tag Info

New answers tagged

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 ...


0

my advice is check the page with ?contents=1. eventually close and delete all unused webparts, or just remove them all and leave just the view and start over


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.


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

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.


0

Have you tried re-creating everything from scratch (i.e. don't use list templates)? How about adding servername and 127.0.0.1 in your hosts file?


0

Here is step you need to configure the Outbound SMTP Server with powershell Add-PSSnapin Microsoft.SharePoint.PowerShell $SMTPSvr = 'mail.contoso.com' $FromAddr = 'noreply@contoso.com' $ReplyAddr = 'noreply@contoso.com' $Charset = 65001 $CAWebApp = Get-SPWebApplication -IncludeCentralAdministration | Where { $_.IsAdministrationWebApplication } ...


0

try to reset IIS on the server. if that fix the problem then fine Other wise reboot the all server in the farm. check this blog for more detail: http://www.c-sharpcorner.com/UploadFile/sagarp/sharepoint-error-occurred-in-deployment-step-recycle-iis-a/ also this one: ...


0

You have the workflow set to start on change, and something in that workflow changes that list item. This would create a loop which SharePoint does not allow. See if your logic allows you to use only "start on creation" instead. If not, you can work around this by bouncing workflows between two lists.


0

couple of things to make sure: First off, have a “User Profile Service Application” running!!!! – that was my mistake, i did not have one. On the site collection you need to activate the “..Publishing Feature” for both, the “Website features” and the “Site Collection Features”. If you intend to use it on a “sub website” – same here, activate the ...


0

When I added the X-RequestDigest header to the JavasScript Proxy to the REST Service it all fell into place. (add {"X-RequestDigest": $("#__REQUESTDIGEST").val()} to the headers send


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; ...


0

some suggestions: make sure all resources are checked in and published clear the browser cache completely before testing keep dev console open and check for script errors use jquery.noconflict leverage document.ready vs window.onload check behaviour in different browsers, machines, and user accounts good luck


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


0

You needed to configure the Azure website with the client id and client secret. As explained to the following blog


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 ...


0

Did you customize your Master Page? if yes then change master page to default then try again. check this http://social.msdn.microsoft.com/forums/sharepoint/en-US/f1887795-f2d6-4653-8cb4-a0ebd95f89fa/enable-disable-publishingpagestatusindicator-on-a-sharepoint2010-document-library What error you are getting in the browser? You may try to deactivate and re ...


0

In order to fix this error, I performed an IIS reset using command prompt: Open command prompt as administrator; type: iisreset /noforce; retry loading the page. This fixed the error for me.



Top 50 recent answers are included