Hot answers tagged

14

for simplicity I will state the obvious! user is not authenticated and resource requires authentication this tells me there is somthing wrong going on with the hand shaking (your certificate is not sent or is wrong), as its a microsoft product the best place is to look at msdn. to make it clear please read this: The following step is optional. ...


6

Finally, I got the solution after lots of googling and brain-stroming. I am not able to solve the REST API - 403 error issue but I got work around for this. I have created Web APIs in MVC project for all SharePoint operations that I wanted to do using REST API. Create Filter for getting SharePoint context in Web API for SharePoint operations. 3 easy Steps:...


5

I had the same behavior on my site. (SP2010 Enterprise using Windows auth (NTLM)). The way I solved it is to create a _layouts deployment project to deploy my custom401.aspx (will come back to it). Updated my webapplication with: $urlWebApplication = "http://myApp" $pathPage401 = "/_layouts/myproject/custom401.aspx" #Change 401 page for webapp Set-...


4

Please find a similar issue reported in msdn with FBA authentication and Opera browser. As the post suggests, Opera browser is not on the supported browser list for SharePoint. Chrome isn't on the list either, although that one normally works. Opera has always had issues with SharePoint and it isn't fixed in 2010. Here's the list of approved browsers. ...


3

If you wish to use the file system to serve content up outside of SharePoint, you will have to replicate the content to all the front ends yourself. In your case, create a regular virtual directory in IIS for the web application serving your SharePoint content on each server and make sure this path isn't used by SharePoint as it'll intercept the request.


3

I had a similar problem. After I created my Web Application I received a strange error, But my Web Application was created, so I continued creating a Site Collection on it but received "403 forbidden" in the end. These instructions helped me: http://support.microsoft.com/kb/2543306 After I raised the timeout parameters in the IIS I recreated the WebApp ...


2

I had similar problems. Instead of using ClientContext or TokenHelper, I switched to the new SharePointContext which you can read about here: http://blogs.msdn.com/b/kaevans/archive/2013/09/24/introducing-sharepointcontext-for-provider-hosted-sharepoint-apps.aspx Once I made this switch, my 401 and 403 problems disappeared. The new SharePointContext uses ...


2

We ran into the same issue on a page with a managed metadata field which was loading ScriptForWebTaggingUI.js. This script (along with several others) changes the __REQUESTDIGEST value on header of Sys.Net.WebRequestManager - for more details see: https://officespdev.uservoice.com/forums/224641-general/suggestions/7025290-bug-with-jsom-when-working-with-...


2

It looks like you're trying to connect to SharePoint Online (sharepoint.com). You have to use FedAuth instead of Ntlm to authenticate against SharePoint Online. See Vadim Gremyachev's great answer at https://stackoverflow.com/questions/35187724/remote-authentication-in-sharepoint-online tl;dr: Vadim has published a sample project for REST authentication ...


1

You have to configure Alternate Access Mapping to support https://www.mysharepoint.com to map to https://server_wfe_1. If you don't do this SharePoint will not correctly map the incoming URL to a query and then write the outbound URL correctly. SharePoint search matches the inbound request to the AAM Zone and then determines how to return the result URLs via ...


1

Error 403 occurs because of the failure of security validation in the page. You need to include Form-Digest Value in the REST API. Refer the code below. var _formDigest=getFormDigest(); var url = "http://<site>" + "/_api/lists/getByTitle('MyLib')/rootfolder/folders/add('MyFolder')"; $.ajax({ url: url, type: "POST", xhrFields: { ...


1

An alternative method would be to host the videos on an external cloud based system like Vimeo, and then link to them on your site. You can embed these videos directly on your pages, or provide links to them.


1

I think I figured out why SharePoint sends 403 error code. SharePoint runs often under the client credentials. But those credentials doesn't work when accessing a network share because Kerberos delegation is not properly enabled and configured. I'm not going to go with Kerberos, It's painful and the virtual directory approach is a kludge as Greg pointed out. ...


1

It seems to be related to permission, therefore, initially would indicate that you will likely need to include your credentials with the client context, as the user will need access to the respective list. using System; using System.Net; using Microsoft.SharePoint.Client; using SP = Microsoft.SharePoint.Client; namespace SharepointConnection { class ...


1

1)Share point server takes user from Active directory. So check the user permission in Active Directory of the windows server. If user is not in active directory than share point is not allowing user to enter in site.I can say there some thing fussy between Active directory and share point web application authentication local server group. 2) Check Local ...


1

Check the lock state of the site collection. If it is ReadOnly/NoAccess, first restore to normal mode. You may refer the below command Set-SPSite -Identity "<SiteCollection url>" -LockState "Unlock" For additional details, reference link


1

Try setting ctx.Credentials before. Other than that, double check your user/pwd/domain using (ClientContext ctx = new ClientContext(url)) { ctx.Credentials = new NetworkCredential("MyUserName", "pass", "domain"); Web web = ctx.Web; ctx.Load(web); ctx.ExecuteQuery(); //Still 403's }


1

The application pool acoount had no permission on the DB. Adding the permission solved my problem.


1

Since the use of NetworkCredentials does not work with adfs I found another solution here. It basicly forces SharePoint to go the Windows authentication way. Some infos here. Anyway just add credentials and force SharePoint do what you want. ctx.Credentials = System.Net.CredentialCache.DefaultNetworkCredentials; ctx.ExecutingWebRequest += new EventHandler&...


1

This suggestion fixed both the managed metadata type columns values are not displayed and the 403 errors. http://sharepoint-talk.blogspot.com/2011/07/metadata-column-not-visible-for-users.html Thank you Amol


1

Is there a TMG / Forefront or similar between user and Sharepoint? We had a lot of such strange issues which boiled down to TMG config.


1

I have found a work around. I deployed my custom WCF to IIS instead of deploying it into SharePoint (ISAPI). I had to make the WCF service public (to be able to call it cross-domain) by adding this code into the WCF's web.config: <system.webServer> <httpProtocol> <customHeaders> <add name="Access-Control-Allow-...


1

403 Forbidden Errors are usually Authentication Error's. You mentioned you are logged in as System account, that might not be the case then. First try checking ULS Logs and see what happened on that specific event. Also Please Take a look at this article this might help. http://support.microsoft.com/kb/2543306 In some instances stsadm -o ...


1

It is expected behavior to receive a 403 when browsing to the PSI directory.. probably to prevent just anyone listing files on the server. You must use the full URL (as you noticed): http://server/ProjectServer/_vti_bin/PSI/Project.asmx If your webpart cannot access the web service, it is because of a different problem. I've had success using new ...


1

As you are trying to upload files through code, did you try to use the RunWithElevatedPrivileges method ? Below is a link which will give you more information on the method. http://msdn.microsoft.com/en-us/library/bb466220(office.12).aspx You can do something like this: SPSite siteColl = SPContext.Current.Site; SPWeb site = SPContext.Current.Web; ...


1

As it turned out, problem was caused by faulty ASP.net profile provider. Extended web application didn't have profile provider configured properly (actually it didn't have configured default profile provider - see here)


1

I had this problem in SharePoint 2007 a couple of times. What helped me was to go to the template folder in the 14 Hive and replace the permissions on all child elements in the file system. It never happens in any productive environment but on development Servers and only for development environments i would recommend this procedure. After that everything ...


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