SharePoint Fraggel

Problem You have added an "assigned a task" action to your SharePoint 2013 Workflow. The associated workflow task list has broken inheritance with custom permissions. When you start your workflow and the task is assigned and you get a  KeyNotFoundException. Fix the problem Don't break the inherit of permission on the associated workflow task list.

You have an existing SAN certificat installed in yor IIS and you want to add a domain name to the certificate. Problem When you install the updated certificate in the IIS the new domain name doesn't appear in the certificate when you are viewing the certificate from the Security report (the lock) next to the address bar in the browser. Fix the problem Check if the "Print Spooler" and "Windows Remote Management" Services are started or not. Delete the old certificate from the IIS Import the new certificate to the IIS Run IISRESET /stop Run net stop http Run net start http Run IISRESET /start Verify that the "Print Spooler" and "Windows Remote Management" Services are started or stoped depending on the result in step 1.

Problem You get the error, "Cannot find an SPWeb object with Id or Url" , when trying to get the RootWeb of the SPSite object when you register a new app with the Register-SPAppPrincipal PowerShell cmdl. Register-SPAppPrincipal -NameIdentifier $appPrincipalIdentifier -Site $site.RootWeb -DisplayName 'ProviderHostedApp' The cause could be The user who is running the script is NOT a farm administrator. Fix the problem Add the user to the farm administrator group

In order to publish a SharePoint App (Provider Hosted in my case) to a sitecollection it must be based on a developer site template or an App Catalog site template. If you run into "Sideloading of apps is not enabled on this site" error when trying to publish the app the Developer feature is most likely not activated. The Developer feature is hidden so you have to activate it throug PowerShell. Run the following script to activate the feature. Enable-SPFeature e374875e-06b6-11e0-b0fa-57f5dfd72085 –url http://sharepoint.contoso.com

When you are using Windows Explorer View in SharePoint you can't MOVE a file from one site to another if it's not directly below the root site, but you can copy the file. See the different scenarios below. Working Scenario Moving files between libraries within the same site. For example: "http://sharepointsite/sites/site1/site2/library1" (source) "http://sharepointsite/sites/site1/site2/library2" (destination) Moving files between libraries across different sites as long as they are directly below the root site. For example: "http://sharepointsite/site1/library1 (source) "http://sharepointsite/site2/library2 (destination) Non-working Scenario Moving files between libraries in sub-sites that are more than 1 level below the root site. For example: "http://sharepointsite/sites/site1/site1/library1" (source) "http://sharepointsite/sites/site1/site2/library2" (destination)

As far as I know the page (/_admin/search/searchconfigwizardtopologyconfig.aspx) where you can add, remove, or modify components of the topology of the Search Service Application e.g. the index location in SP 2010 is no longer available. So if you would like to get your Search Index Location then you could use the following PowerShell script. $searchSrvInst = Get-SPEnterpriseSearchServiceInstance $searchSrvInst.Components

Open the PowerShell ISE and create a profile by running the following code: if (!(test-path $profile.AllUsersAllHosts)) { new-item -type file -path $profile.AllUsersAllHosts-force } Open the newly created profile with the following command: psEdit $profile.AllUsersAllHosts The profile will be open in the PowerShell ISE. Add the following code to the profile: (If the profile for some reason doesn't open then you can get it here: C:\Windows\System32\WindowsPowerShell\v1.0\profile.ps1) if ((Get-PSSnapIn -Name Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue) -eq $null ) { Add-PSSnapIn -Name Microsoft.SharePoint.PowerShell } Save the profile. Next time you open the PowerShell ISE you will have all the Microsoft.SharePoint.PowerShell commandlets.