Tag Info

Hot answers tagged

5

Under the website properties in IIS, GOTO > Traffic > Filtering and disable Verify Normalisation. This setting is preventing your site from displaying pages with escaped characters in the URLs. [update] In later versions of IIS it is in the general tab of the website properties, and not under Traffic.


4

When I've ran C# within PowerShell, I've done the assembly bit differently (I'm in O365, so only use CSOM): $path = "path to folder containing dll's (e.g.,ISAPI folder in 15 Hive)" $assemblies = @( "$path\Microsoft.SharePoint.Client.dll", "$path\Microsoft.SharePoint.Client.Runtime.dll" "System.Core" ) $cSharp = @" using System; using ...


4

Please try deleting "Error Web Part" from web part maintenance page. This is your "LightningConductorWebPart" which is throwing error.


3

Did a complete re-installation with the following power shell script to Configure the App Domain: net start spadminv4 net start sptimerv4 Set-SPAppDomain "<app domain name>" Get-SPServiceInstance | where{$_.GetType().Name -eq "AppManagementServiceInstance" -or $_.GetType().Name -eq "SPSubscriptionSettingsServiceInstance"} | Start-SPServiceInstance ...


3

This is because you are passing the full url instead of relative url Replace http://dev-env/sites/site/subsite/ With subsite i.e elevatedWeb.Webs.Add(title, title, strDescription, nLCID, WebTemplate, uniquePerms, bConvertIfThere);


3

You might be using a wrong 'Web' object. It shouldn't be System.Web or Microsoft.Web. It should be from Microsoft.SharePoint.SPWeb namespace. So first of all you need to get an 'SPWeb' object from 'properties'. Depending on where you are activating the feature, it should be something like this: If you are activating a Web scoped feature: SPWeb web = ...


2

I solved this problem editing this file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\web.config


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


2

Are you sure it was a subsite and not the main web site of the Site collection? You can use Central Administration to check your Site Collection -> Application Management -> Site Collections -> View all site collections and maybe you will find some answers there. And you can also try an iisreset. Please let me know how it goes.


2

You may need to set "Update links on save" to false prior to adding your hyperlinks to the Excel spreadsheet. In Excel 2010: - uncheck "Update links on save" in Options > General > Web Options > Files tab In Excel 2013: - uncheck "Update links on save" in Options > Advanced > Web Options (under "General") > Files tab After changing the Excel setting, ...


2

Looking at your error that it's reporting: Go to the project: MyWebPart Go to the class: VisualWebPart1UserControl within that class you have a control that is called: FillFilterBoxes It is that control that is throwing the null value exception! The error clearly states 'Value cannot be null' so the default value needs not be null. What ...


2

Did you enable the OUtput Cache on the Site? Also could you please Confirm that Object Cache Configured for the web app properly. If Object Cache Configure then try below resolution. Disabled and re-enabled Publishing feature and Navigation feature for all sites using the powershell script which would loop through all subsites: Get-SPWeb -site ...


2

The problem is the URL format that you are providing to the net use command. Take a look at the PowerShell script here http://www.lieben.nu/numb3rs/?page_id=129 which automates mapping a drive letter. You will see the format of the parameter is like this: \\domain.sharepoint.com@SSL\DavWWWRoot\sites\codesite\example\Shared Documents If you would ...


2

This was exactly our issue. We had extended the Array.prototype and for whatever reason it caused the SP scripts to start failing. We already had another prototype extension that caused no issues. We ended up just moving it into a utility function instead.


2

Re-index feature has been introduced in SharePoint 2013.I don't think it is available in SharePoint 2010 . Please ensure the crawl account should have a "Full Read" property, using a Web Application policy.I think your crawl account do not have full control for those items. To ensure that crawl account have permissions to read those items log in using the ...


2

The way that visual web parts were implemented changed in SharePoint 2013. Previously, visual web parts could use an .ascx file located in the 14 hive, while in 2013 the .ascx file was embedded in the .dll and no file was deployed to the file system. This enabled visual web parts to be used in a sandboxed scenario. So your 2013 wsp is probably failing on ...


1

There would be many other reasons this is one of those. This is due to the refinement web part is not added on search page or settings are not configured properly. You can check the detailed steps to resolve the issue it this is the reason : http://expertsharepoint.blogspot.in/2014/03/we-dont-have-any-refiners-to-show-you.html


1

What you are encountering is a code access security issue (CAS). Basically SharePoint only trusts certain assemblies to perform certain "risky" operations and your assembly is not on the list. The way the list of assemblies that are allowed to do certain things is managed is through a CAS policy file which is located in the config folder of sharepoint. You ...


1

I found the solution, just simply opened my "problematic" field via "List" -> "Site settings" -> "OrderType", and than pressed "OK" (I didn't do any changes). Now I can access it via Powershell. Thanks to this post (it's about site columns but the solution is similar)!


1

You can find PowerShell samples here to get/set Choice fields: http://social.technet.microsoft.com/wiki/contents/articles/20831.sharepoint-a-complete-guide-to-getting-and-setting-fields-using-powershell.aspx#Set_and_Get_a_Choice_Field For example, you should be able to set your field value like this: $item["OrderType"] = ...


1

Some things to check: Ensure Managed Metadata Service / Connections are functioning without problems If recent changes were made to terms, these changes may impact your navigation. Consider rolling back changes temporarily so you can access your site's Navigation Settings. Ensure that sites/lists/pages etc. referenced by your site's navigation were not ...


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

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


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

Their are many reasons for this issue. You have to check the ULS logs for against that correlation id to get more info.if you have powershell access run the below command on one of the server to get complete trace. Merge-SPLogFile -correlation "7ef88eb0-47d5-4e0f-b5cf-177ebca4a6df" -Path "C:\Error.log" -StartTime "06/25/2014 03:35" - EndTime "06/25/2014 ...


1

Are you using Sandboxed Solution? try this which is a similar question on Stack Overflow and is answered: Sharepoint event receiver and linq to sharepoint


1

Please check site features. There is feature called "Workflow can use app permissions". Activate that. http://msdn.microsoft.com/en-us/library/office/jj822159(v=office.15).aspx


1

In my case this error occurred since non-default language was selected during root site provision. It seems Variation labels application page retrieves Variations List by its title and expects Variation Labels value. Solution Update Variations List title to Variation Labels. The below example demonstrates how to update Variations List title using CSOM. ...


1

you can try to fix variation label and here is the link how to do it: stsadm -o variationsfixuptool -url <absolute web URL> [-fix] [-scan] [-spawn] [-showrunningjobs] [-recurse] [-label <label to fix or spawn>] ...



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