Tag Info

Hot answers tagged

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

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

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

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

$siteUrl = "http://ukreddy:3456/" $siteCollection = Get-SPSite $siteUrl Enable-SPFeature "PublishingSite" -Url $siteCollection.Url -force Enable-SPFeature "PublishingWeb" -Url $siteCollection.Url -force http://ukreddysharepoint2010.blogspot.co.uk/2014/05/error-systemargumentexception-value.html Sharepoint was failing to activate the feature PublishingWeb. ...


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

You need to: Create a Secure Store Service Generate a new key Create a Target Application specific to Visio Copy the Target Application ID Paste it in the Visio Graphics Service Global Settings Source: http://daniecsp.blogspot.com/2012/11/sp-2010-unattended-service-account.html


1

Do you have anything else using the Secure Terms Store? If you don't then the easiest solution is to remove both the Secure Store Service and Visio Services Application then recreate the Secure Store and set it up with a key. once you've done that successfully, recreate the Visio Services and input your unattended service account credentials.


1

The event handler you mention is not a part of Standard SharePoint. All assemblies in SP 2010 have version 14. Moreover there's no TaskAlert assembly in standard SP. You may use following SQL command in your SP content database to try find the list where is registered: select * from AllLists where tp_ID in(SELECT distinct HostId FROM ...


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 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. Also this one.


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