Tag Archives: SharePoint2016

Slow SharePoint improve performance without upgrading hardware

what you can do if your SharePoint is sometimes very slow.

E.g.: on the first start of a Site
Sometimes during the day a search query will take about a minute until you get results.....

Just look on that article: http://support.microsoft.com/kb/2625048

it will improve "feeled" performance (site response times) massive, if you're going to implement both solutions.

Disabling CRL Check is just necessary if the SP Server does not have internet connectivity, that means proxy settings must be configured for the server itself

http://technet.microsoft.com/de-de/library/bb430772(v=exchg.141).aspx, and your proxy must allow traffic from the server of course.

Advertisements
Advertisements
Advertisements

Monitor cache performance SharePoint 2016

SharePoint Server 2016 provides three types of caches that help improve the speed at which web pages load in the browser: the BLOB cache, the ASP.NET output cache, and the object cache.

The BLOB cache is a disk-based cache that stores binary large object files that are used by web pages to help the pages load quickly in the browser.

The ASP.NET output cache stores the rendered output of a page. It also stores different versions of the cached page, based on the permissions of the users who are requesting the page.

The object cache reduces the traffic between the web server and the SQL database by storing objects such as lists and libraries, site settings, and page layouts in memory on the front-end web server. As a result, the pages that require these items can be rendered quickly, increasing the speed with which pages are delivered to the client browser.

The monitors measure cache hits, cache misses, cache compactions, and cache flushes. The following list describes each of these performance monitors.

A cache hit occurs when the cache receives a request for an object whose data is already stored in the cache. A high number of cache hits indicates good performance and a good end-user experience.

A cache miss occurs when the cache receives a request for an object whose data is not already stored in the cache. A high number of cache misses might indicate poor performance and a slower end-user experience.

Cache compaction (also known as trimming), happens when a cache becomes full and additional requests for non-cached content are received. During compaction, the system identifies a subset of the contents in the cache to remove, and removes them. Typically these contents are not requested as frequently.

Compaction can consume a significant portion of the server’s resources. This can affect both server performance and the end-user experience. Therefore, compaction should be avoided. You can decrease the occurrence of compaction by increasing the size of the cache. Compaction usually happens if the cache size is decreased. Compaction of the object cache does not consume as many resources as the compaction of the BLOB cache.

A cache flush is when the cache is completely emptied. After the cache is flushed, the cache hit to cache miss ratio will be almost zero. Then, as users request content and the cache is filled up, that ratio increases and eventually reaches an optimal level. A consistently high number for this counter might indicate a problem with the farm, such as constantly changing library metadata schemas.

You can monitor the effectiveness of the cache settings to make sure that the end-users are getting the best experience possible. Optimum performance occurs when the ratio of cache hits to cache misses is high and when compactions and flushes only rarely occur. If the monitors do not indicate these conditions, you can improve performance by changing the cache settings.

The following sections provide specific information for monitoring each kind of cache.

Monitoring BLOB cache performance:

monitor-blob-cache

Note:
For the BLOB cache, a request is only counted as a cache miss if the user requests a file whose extension is configured to be cached. For example, if the cache is enabled to cache .jpg files only, and the cache gets a request for a .gif file, that request is not counted as a cache miss.

Monitoring ASP.NET output cache performance :

monitoring-asp-net-output-cache-performance

Note:
For the ASP.NET output cache, all pages are cached for a fixed duration that is independent of user actions. Therefore, there are flush-related monitoring events.

Monitoring object cache performance :

The object cache is used to store metadata about sites, libraries, lists, list items, and documents that are used by features such as site navigation and the Content Query Web Part.

This cache helps users when they browse to pages that use these features because the data that they require is stored or retrieved directly from the object cache instead of from the content database.

The object cache is stored in the RAM of each web server in the farm. Each web server maintains its own object cache.

You can monitor the effectiveness of the cache settings by using the performance monitors that are listed in the following table.

monitoring-object-cache-performance

Unable to render the data

Unable to render the data error bdc

Advertisements
Advertisements

Unable to render the data error bdc sharepoint 2016

Created an external list SharePoint 2016 using business data connectivity services, configured secure store target application and created external list in SharePoint.The external list displayed this error message with a correlation ID as "Unable to render the data. If the problem persists, contact your web server administrator."

unable-to-render-the-data-if-the-problem-persists-contact-your-web-server-administrator

ULS Log viewer found this message in the logs:

Error while executing web part: Microsoft.BusinessData.Infrastructure.BdcException: The shim execution failed unexpectedly - Unable to obtain the application proxy for the context.. ---> Microsoft.Office.SecureStoreService.Server.SecureStoreServiceException: Unable to obtain the application proxy for the context.

Solution:

The web application is not associated with the secure store service application.

  1. Go to SharePoint Central Administration site
  2. Navigate to Application management >> Click on Configure service application associations under Service Applications.
  3. Select the web application in which your site exist, Check the "Application proxy group" column >> Make sure the BDC and secure store service applications check boxes checked.

service-application-association-sharepoint-2016

Advertisements
Advertisements

SharePoint 2016 Help Collection

In this article, we will discuss ,how to use PowerShell cmdlets for managing Help Collections SharePoint.

SharePoint help collection is not configured with SharePoint Configuration, This needs to manually configured.SharePoint Help Files(.Cab) installed on the hive folder with SharePoint Installation but not configured by default. In order to configure it we have to run the PowerShell commands.

when users click on the Help button  on their site collection, they get the following error

help

” Unfortunately, Help Seems to be broken,There aren’t any help collections in the current language for the site you’re using.”

unfortunately-help-seems-to-be-broken

Even if go to Site settings > Site administration > Help Settings will get this

home-error

Clearly Help collection is broken and now it is SharePoint Admins responsibility to fix the broken Help Collection.

S0lution :

In order to fix the broken help collection, following activities needs to be done.

Check the CAB files exist
Get the Current Help File Status
Install the Help File(s)
Testing

Check Help Files :

Logon the SharePoint Server and browse to the hive folder.

Go to “C:\program Files\Common Files\microsoft shared\web server extensions\16\HCCab

In this folder, make sure you see cab files for 14 & 15.

cab-file

If you have multiple language packs then check each language folder i.e English is 1033

  • Log on the server with farm admin account
  • Open PowerShell windows (Run as Administrator)
  • Run the Get-sphelpcollection command

get-sphelp

you can see nothing return even command completed successfully

Install Help files :

install all the available help,run the command with all options

  • Log on the server with farm admin account
  • Open PowerShell (Run as Administrator) and run Install-SPHelpCollection – All

install-sphelp

This command will install the help files available in the hive folder.
Wait for 5 minutes to completely install it, if you have multiple language packs install then even wait little more.
Now run Get-SpHelpCollection and you will get something like this.

get-sphelp2

Test it at both locations via site settings as well as from the browsing the Site collection.

Go to Site collection > Site settings > help Settings and you will see this option

home

Now if you click on the “?” (help button) on the top suite bar, you will get this pop up

central-admin-help

Uninstall :

As we noticed, we have 2010 help files also installed, we have to uninstall one by one.

  • Log on the server with farm admin account
  • Open PowerShell ( Run as administrator) and run this command
  • Uninstall-SpHelpCollection –Name “OSSEndUser.1033.12”

uninstall-help

Conclusion :

In this session we learned how to fix the broken Help Collection.

Keep reading and learning.

Content databases contain orphaned Apps 1920x1080

Content databases contain orphaned Apps SharePoint 2013

Advertisements
Advertisements

Content databases contain orphaned Apps

SharePoint Health Analyzer rule “Content databases contain orphaned Apps.”

Some situation content database may become corrupted. The corrupted database may contain orphaned apps. Orphaned apps are not accessible, which causes unnecessary resource and license consumption and may result in failures in SharePoint upgrade.

Solution

Remove app for SharePoint instances from a SharePoint 2013 site.

A user must have the Manage Web site permission to remove an app for SharePoint. By default, this permission is only available to users with the Full Control permission level or who are in the site Owners group.

To remove an app from a SharePoint site

  • Verify that the user account that is performing this procedure is a member of the Site owners group.
  • On the site, on the Settings menu, click View Site Contents.
  • In the Apps section, point to the app that you want to remove, click “…”, and then click Remove.
  • Click OK to confirm that you want to remove the app.

To remove an app by using Windows PowerShell

Verify that you have the following memberships:

  • securityadmin fixed server role on the SQL Server instance.
  • db_owner fixed database role on all databases that are to be updated.
  • Administrators group on the server on which you are running the Windows PowerShell cmdlets.
  • Site Owners group on the site collection to which you want to install the app.

An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 15 Products cmdlets. On the Start screen, click SharePoint 2013 Management Shell, type the following commands, and press ENTER after each one:

$instances = Get-SPAppInstance -Web
#Gets all apps installed to the subsite you specify.

$instance = $instances | where {$_.Title -eq ”}
#Sets the $instance variable to the app with the title you supply.

Uninstall-SPAppInstance -Identity $instance
#Uninstalls the app from the subsite.

At the question “Are you sure you want to perform this action?”,
type Y to uninstall the app.

Advertisements
Advertisements

Locate and remove app instances in all locations

An app for SharePoint in the App Catalog is available for users to install.Users can install apps for SharePoint on many sites. Below two Windows PowerShell scripts can be used to find all locations for a specific app and then uninstall all instances from every location.

First script to locate all instances of a specific app in a SharePoint environment. Then use the second script to uninstall all instances of the app from the SharePoint environment.

To locate specific apps by using Windows PowerShell (save as script and run script)

Verify that you have the following memberships:

  • securityadmin fixed server role on the SQL Server instance.
  • db_owner fixed database role on all databases that are to be updated.
  • Administrators group on the server on which you are running Windows PowerShell cmdlets.

An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets

save the below script as “Get-AppInstances.ps1”

This Windows PowerShell script gets all app instances from your SharePoint 2013 farm for a specified App ID on a specified web application. You specify the App ID and the web application URL and the script will remove all of the instances of the App for all webs in that web application.

param(
[Parameter(Mandatory=$true)] [Guid] $productId,
[Parameter(Mandatory=$true)] [String] $webAppUrl
)

function GetAllInstances($productId = $null, $webAppUrl = $null)
{
$outAppName = "";
$sites = Get-SPSite -WebApplication $webAppUrl
$outWebs = @()
foreach($site in $sites){
if($site.AdministrationSiteType -ne "None"){
continue;
}
$webs = Get-SPWeb -site $site
foreach($web in $webs) {
$appinstances = Get-SPAppInstance -Web $web
foreach($instance in $appinstances) {
if($productId -eq $instance.App.ProductId) {
if ($outAppName -eq "") {
$outAppName = $instance.Title;
}
$outWebs += $web;
}
}
}
}
return ($outAppName,$outWebs)
}
Write-Host "This script will search all the sites in the webAppUrl for installed instances of the App."
$confirm = Read-Host "This can take a while. Proceed? (y/n)"
if($confirm -ne "y"){
Exit
}

$global:appName = $null;
$global:webs = $null;

{
$returnvalue = GetAllInstances -productId $productId -webAppUrl $webAppUrl;
$global:appName = $returnvalue[0];
$global:webs = $returnvalue[1];
}
);

$count = $global:webs.Count;
if($count -gt 0){
Write-Host "App Name:" $global:appName;
Write-Host "Product Id: $productId";
Write-Host "Number of instances: $count";
Write-Host "";
Write-Host "Urls:";

foreach($web in $global:webs) {
Write-Host $web.Url;
}
}
else {
Write-Host "No instances of the App with Product Id $productId found.";
}
return;
  • Now Open “SharePoint 2013 Management Shell”
  • Change to the directory where you saved the file.
  • At the Windows PowerShell command prompt, type the following command: 
./ Get-AppInstances.ps1 -productId -webAppUrl

To uninstall specific apps from all locations by using Windows PowerShell (save as script and run script)

Verify that you have the following memberships :

  • securityadmin fixed server role on the SQL Server instance.
  • db_owner fixed database role on all databases that are to be updated.
  • Administrators group on the server on which you are running Windows PowerShell cmdlets.

An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets

save the below script as “Remove-App.ps1”

This Windows PowerShell script removes all app instances from your SharePoint 2013 farm for a specified App ID on a specified web application. You specify the App ID and the web application URL and the script will remove all of the instances of the App for all webs in that web application.

Advertisements
Advertisements
param(
[Parameter(Mandatory=$true)] [Guid] $productId,
[Parameter(Mandatory=$true)] [String] $webAppUrl
)

function RemoveInstances($productId = $null, $webAppUrl = $null)
{
$outAppName = "";
$sites = Get-SPSite -WebApplication $webAppUrl
$outWebs = @()
foreach($site in $sites){
if($site.AdministrationSiteType -ne "None"){
continue;
}
$webs = Get-SPWeb -site $site
foreach($web in $webs) {
$appinstances = Get-SPAppInstance -Web $web
foreach($instance in $appinstances) {
if($productId -eq $instance.App.ProductId) {
if ($outAppName -eq "") {
$outAppName = $instance.Title;
}
$outWebs += $web;
Write-Host "Uninstalling from" $web.Url;
Uninstall-SPAppInstance -Identity $instance -confirm:$false
}
}
}
}
return ($outAppName,$outWebs)
}

$confirm = Read-Host "This will uninstall all instances of the App and is irreversible. Proceed? (y/n)"
if($confirm -ne "y"){
Exit
}

$global:appName = $null;
$global:webs = $null;

{
$returnvalue = RemoveInstances -productId $productId -webAppUrl $webAppUrl;
$global:appName = $returnvalue[0];
$global:webs = $returnvalue[1];
}
);

$count = $global:webs.Count;
if($count -gt 0){
Write-Host "All the instances of the following App have been uninstalled:";
Write-Host "App Name:" $global:appName;
Write-Host "Product Id: $productId";
Write-Host "Number of instances: $count";
Write-Host "";
Write-Host "Urls:";

foreach($web in $global:webs) {
Write-Host $web.Url;
}
}
else {
Write-Host "No instances of the App with Product Id $productId found.";
}
return;
  • Open SharePoint 2013 Management Shell
  • Change to the directory where you saved the file.
  • At the Windows PowerShell command prompt, type the following command:
./ Remove-App.ps1 -productId -webAppUrl

If the issue still persists like as below

“If you have an orphaned app in the initialized state on a site and you delete the site, Health Analyzer reports that there's an error and the auto-fix doesn't work.”

Apply CU November 2016 which will 100% resolve the issue

SharePoint Server 2013 (KB3127933)
SharePoint Foundation 2013 (KB3127930)

Advertisements
Advertisements
New APP created once "Project Functionality" feature is activated.

Activate site Features create APP in Site Contents SharePoint2016

Today I successfully installed SharePoint Server 2016 on-premises overcoming few errors related to prerequisite as per my previous posts.

You can see below previous posts :

  1. Windows Server Appfabric: Installation error SharePoint 2016
  2. Cannot connect to database master at SQL Server at server_name. The database might not exist, or the current user does not have permission to connect to it Error SharePoint 2016
  3. Failed to create configuration database. An exception of type Microsoft.SharePoint.Upgrade. SPUpgrade Exception was thrown. Additional exception information: One or more types failed to load. Please refer to the upgrade log for more details Error SharePoint 2016
  4. Program can’t start because api-ms-win-crt-heap-l1-1-0.dll is missing SharePoint2016
  5. Unable to install Microsoft Information Protection and control Client 2.1 error SharePoint 2016

Here I am very excited to let you know the “SharePoint APP” created in “Site Contents” by activating the “site feature“.

you may take it very easy but its not as simple as to resolve issues sometimes, that time it will help you a lot.

a. “Default APP” once site is created, before activating any feature.

Default APP in Site Contents with no feature activate

Default APP in Site Contents with no feature activate, once site is created

b. New APPs  added in Site Contents  after “Publishing Feature” is activated

New APPs added in Site Contents after

New APPs added in Site Contents after “Publishing Feature” is activated

c. New APPs  added in Site Contents  after “Content Organizer” feature is activated.

New APPs added in Site Contents after

New APPs added in Site Contents after “Content Organizer” feature is activated.

d. New APPs  added in Site Contents  after “Community Site” feature is activated.

Site-Contents-Community-Site-Feature-activate

Site-Contents-Community-Site-Feature-activate

e. New APPs  added in Site Contents  after “Site Feed” feature is activated.

New APPs added in Site Contents after

New APPs added in Site Contents after “Site Feed” feature is activated.

f. New APPs  added in Site Contents  after “Project Functionality” feature is activated.

New APP created once

New APP created once “Project Functionality” feature is activated.

amazon     amazonsp2016  amazonsp2016_2