Configure ULS log and Usage and Health log location

by Marco Rietveld 23. oktober 2014 13:30

Diagnostic logging can use large amounts of drive space and writing to the logs can affect drive performance.
Also logging can quickly fill the system disk, potentially bringing the entire system to a crashing halt.
Therefore, it is recommended to configure logging to write to a different drive.

By default, logging is configured to write logs to the drive and partition where SharePoint 2013 is installed.

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS

SharePoint 2013 does not limit the amount of disk space that diagnostic logging can use.
To prevent SharePoint to fill the disk with log files, especially when using verbose-level events, it is recommended to set a maximum disk space usage.
Also a new log file is created every 30 minutes. When the space that is available to the log file is used, the oldest logs are removed and new logging data information is recorded.

Changing the SharePoint 2013 log settings can be done using PowerShell or Central Admin.

Use the following PowerShell commands to change the settings:

Diagnostics log(ULS)

Setting the log location to D:\SPlogs\ULS and set the number of days to keep the log files to 60 with a maximum disk space of 100GB

Use the following command to change the settings:

set-SPDiagnosticConfig -LogLocation D:\SPLogs\ULS -DaysToKeepLogs 60 -LogMaxDiskSpaceUsageEnabled -LogDiskSpaceUsageGB 100

Usage and Health log

Setting the log location to D:\SPLogs\Health and leave other settings default.

Use the following command to change the log location:

set-SPUsageService –UsageLogLocation “D:\splog\Health”

 

ULS Viewer

The ULS Viewer can be used to view the logs using in a user-friendly interface. 
ULS Viewer can filter, sort, highlight and append logs to help locate data that is relevant to an issue.
SharePoint 2013 uses correlation IDs, that are identifiers associated with every request and are displayed with error messages.
By filtering the correlation ID it is possible to identify the request that caused the error.

ULS Viewer download
http://www.microsoft.com/en-us/download/details.aspx?id=44020

Tags: | |

how to configure the default open behavior for Office documents in SharePoint 2013

by Marco Rietveld 22. juli 2014 13:06

Clicking on a document in a SharePoint 2013 document library, the document opens in a client application or in the browser. This depends on the setup of Office Web Apps and the settings of the OpenInClient feature per library or site collection.

When SharePoint 2013  is configured to use Office Web apps (OWA), Word, PowerPoint, excel and OneNote files are opened in the browser. Even though PDF files are not part of Office when OWA is configured, PDF files are also opened in the browser.

The default behavior can be changed for the SharePoint 2013 Farm per file type, Site Collections or Document Libraries.

Changing the default opening behavior for the SharePoint 2013 Farm can be done using New-SPWOPIBinding or Set-SPWOPIBinding commands.

Set default behavior for a Site Collection

Browse to a SharePoint site collection to configure the default open behavior and navigate to Site settings, Select Site Collection Features in Site Collection Administration section.

image

To open documents in the client application, activate the feature "Open Documents in Client Application by Default feature".

image

 

Set default behavior for a Site Collection using Powershell

The Open Documents in Client Application by Default feature can be Enabled or Disabled by using the Powershell.

To enable the feature:

Enable-SPFeature 8A4B8DE2-6FD8-41e9-923C-C7C3C00F8295 -url <SiteCollURL>.

Get-SPSite -limit ALL |foreach{ Enable-SPFeature 8A4B8DE2-6FD8-41e9-923C-C7C3C00F8295 -url $_.URL } 

To disable the feature:

Disable-SPFeature 8A4B8DE2-6FD8-41e9-923C-C7C3C00F8295 -url <SiteCollectionURL>

Get-SPSite -limit ALL |foreach{ Disable-SPFeature 8A4B8DE2-6FD8-41e9-923C-C7C3C00F8295 -url $_.URL }

 

Set the default behavior for document library

Browse to a SharePoint document library and select Library tab on the ribbon and select Library Settings.

image

Select Advanced Settings in Document Library settings.

image

In Advanced Settings go to the Opening Documents in the Browser section choose the default behavior. 
To open documents in the client application, select Open in the client application.
To open in web browser, select Open in the browser.
The default setting is “Use the server default”.

image

Tags: |

FIX: Deleted Timer Job - User Profile Incremental Synchronization

by Marco Rietveld 19. maart 2014 15:12

When trying to stop a user profile import (it had the status stopping for a few hours) the User Profile Incremental Synchronization job was mistakenly deleted. (Don’t ask how)
During the search for a solution how to get the timer job recreated SharePoint came up with a solution on its own. There is a health rule to check if the User Profile timer jobs are available and not been mistakenly deleted. This job runs hourly and because the timer job was deleted it displayed a notification in Central Admin

image

Clicking on “View these issues” displays a detailed notification.

image

The secret to the solution showed up when clicking on the link of the health notification.

image

Some health analyzer rules have an option called “Repair Automatically”. Clicking the “Repair Automatically” button will recreate the deleted timer job.

image

To be sure if the job was recreated check the job definitions under Monitoring and the User Profile Incremental Synchronization job should be there.

Tags: | |

Move the search index location in SharePoint 2013

by Marco Rietveld 18. september 2013 14:09

During the installation of SharePoint 2013 there is an option to change the search index location. The default location is C:\Program Files\Microsoft Office Servers\15.0\Data. It is possible to change the search index location to a dedicated volume after the installation using PowerShell.

Managing the search topology in SharePoint 2013 can be done only via PowerShell. Here is an article about the procedure: http://technet.microsoft.com/en-us/library/jj219705(v=office.15).aspx

Changing the search index location can be done by following the next steps:

  • Get the current search topology
  • Clone the current search topology
  • Modify the cloned Search topology
    (add a new index component with new search index location)
  • Activate the cloned search topology
  • Remove the old search topology
  • remove old index component
    (This means clone, modify, activate search topology and remove the old search topology)

Get the current Search topology

$ssa = Get-SPEnterpriseSearchServiceApplication "Search Service Application"
$instance=Get-SPEnterpriseSearchServiceInstance -Local
$current=Get-SPEnterpriseSearchTopology -SearchApplication $ssa

 

Clone the current Search topology

$clone=New-SPEnterpriseSearchTopology -Clone -SearchApplication $ssa -SearchTopology $current

 

Modify the cloned Search topology

This will add a second index component with a new index location.

New-SPEnterpriseSearchIndexComponent -SearchTopology $clone -IndexPartition 0 -SearchServiceInstance $instance -RootDirectory "E:\NewIndexLocation"

 

Activate the cloned Search topology

Set-SPEnterpriseSearchTopology -Identity $clone

 

Remove the old Search topology

Remove-SPEnterpriseSearchTopology -Identity $current

The next step, remove the old index component, should be done when the new index component is ready.
This can be checked from Central Admin on the Search Administration page, view the status of the search topology or use PowerShell Get-SPEnterpriseSearchStatus. The new index component must be Active.

 

Remove the old index component

This must be done by get, clone, modify, activate the new search topology and remove the old search topology

$current=Get-SPEnterpriseSearchTopology -SearchApplication $ssa
$clone=New-SPEnterpriseSearchTopology -Clone -SearchApplication $ssa -SearchTopology $current
$comp=Get-SPEnterpriseSearchComponent -SearchTopology $clone | ? {$_.Name -eq "IndexComponent1"}
Remove-SPEnterpriseSearchComponent -Identity $comp -SearchTopology $clone
Set-SPEnterpriseSearchTopology -Identity $clone
Remove-SPEnterpriseSearchTopology -Identity $current

Tags: | |

Augustus 2013 Cumulative updates voor SharePoint 2013 beschikbaar

by Marco Rietveld 15. augustus 2013 11:33
De cumulative updates van Augustus 2013 voor SharePoint 2013 zijn beschikbaar.
De Maart 2013 PU moet geïnstalleerd zijn voordat de Cumulative Update geïnstalleerd kan worden.
De Full Server Packages kunnen hier gedownload worden:

Voor SharePoint 2013 server is het voldoende om de SharePoint Server 2013CU te installeren, deze bevat ook de SharePoint Foundation 2013 CU.

Na de installatie, start de SharePoint Products and Technologies Configuration Wizard. Dit moet worden uitgevoerd op iedere SharePoint server in de SharePoint Farm.

De Microsoft KB Artikelen:

  • KB 2817517 - SharePoint Foundation 2013 August 2013 CU
  • KB 2817616 - SharePoint Server 2013 August 2013 CU
  • KB 2817615 - SharePoint Server 2013 with Project Server August 2013 CU
  • KB 2817521 - Office Web Apps Server 2013 August 2013 CU

Tags: |

Juni 2013 Cumulative updates voor SharePoint 2013 beschikbaar

by Marco Rietveld 9. juli 2013 12:16
De cumulative updates van Juni 2013 voor SharePoint 2013 zijn beschikbaar.
De Maart 2013 PU moet geïnstalleerd zijn voordat de Cumulative Update geinstalleerd kan worden.
De Full Server Packages kunnen hier gedownload worden:

Voor SharePoint 2013 server is het voldoende om de SharePoint Server 2013CU te installeren, deze bevat ook de SharePoint Foundation 2013 CU.

Na de installatie, start de SharePoint Products and Technologies Configuration Wizard. Dit moet worden uitgevoerd op iedere SharePoint server in de SharePoint Farm.

De Microsoft KB Artikelen:

  • KB 2817346 - SharePoint Foundation 2013 June 2013 CU
  • KB 2817414 - SharePoint Server 2013 June 2013 CU
  • KB 2817415 - SharePoint Server 2013 with Project Server June 2013 CU
  • KB 2817350 - Office Web Apps Server 2013 June 2013 CU

Tags: |

BCS Database running in compatibility range

by Marco Rietveld 9. juli 2013 08:22
 

Na de installatie van de Maart 2013 Update kan het zijn dat er een Health analyzer warning verschijnt.

"Databases running in compatibility range, upgrade recommended.”​

De database die deze melding veroorzaakt is de BCS database.

Een content database kan individueel worden geupdate via powershell, dit is niet het geval met o.a. de BCS database.
De BCS database kan met een provision operation geupdate worden naar de juiste versie.

Het volgende Powershell command voert een provision operation uit op de BCS database:

(Get-SPDatabase | ?{$_.type -eq“Microsoft.SharePoint.BusinessData.SharedService.BdcServiceDatabase”}).Provision()

Het kan zijn dat de BCS Service Application een error geeft in Central Admin.
zorg er dan voor dat de applicatie pool account "SPDataAccess" heeft op de BCS Database:

Tags:

Oktober 2012 Cumulative updates voor SharePoint 2010 beschikbaar

by Marco Rietveld 18. november 2012 11:17

De cumulative updates van Oktober 2012 voor SharePoint 2010 zijn beschikbaar.
Deze update is een Post SP1 update, dit betekend dat Service Pack 1 voor SharePoint 2010 geïnstalleerd moet zijn voordat deze CU geïnstalleerd kan worden

De Cumulative updates kunnen hier gedownload worden:

Voor SharePoint 2010 server is het voldoende om de SharePoint Server 2010 CU te installeren, deze bevat ook de SharePoint Foundation 2010 CU.

Na de installatie, start de SharePoint Products and Technologies Configuration Wizard. Dit moet worden uitgevoerd op iedere SharePoint server in de SharePoint Farm.

De Microsoft KB Artikelen:

  • KB 2687566 - SharePoint Foundation 2010
  • KB 2687564 - SharePoint Server 2010
  • KB 2687565 - SharePoint Server 2010 with Project Server

Test de updates altijd eerst in een testomgeving voordat deze op een productieomgeving worden geïnstalleerd.

Tags: | |

De SharePoint 2010 Administration service failed to start

by Marco Rietveld 2. november 2012 09:03

Na het installeren van een SharePoint Cumulative Update en een reboot van de server gaf de SharePoint Configuration Wizard een error.

In het eventlog stond tevens de melding:

The SharePoint 2010 Administration service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Error: 1053

Dit gebeurt wanneer een SharePoint server geen internet toegang heeft en KB 2677070 is geinstalleerd.
De reden van de foutmelding is dat er geen update van de certificate trust list kan worden gedownload.

Omdat na het installeren van KB2677070 een reboot niet noodzakelijk is komt de fout pas naar boven na de eerst volgende reboot van de server.

In dit geval werd er gebruik gemaakt van een proxy server en was winhttp niet geconfigureerd.
Winhttp kan als volgt geconfigureerd worden:

  • Open een command prompt
  • Netsh
  • Winhttp
  • show proxy

Wanneer er geen proxy is ingesteld kan dit op 2 manieren worden. ingesteld.

  • netsh winhttp>set proxy 10.10.10.1:8080 "<local>"

Of wanneer er in Internet Explorer een proxy server staat ingesteld kan deze setting worden overgenomen.

  • import proxy source=ie

Tags: |

Augustus Cumulative updates voor SharePoint 2010 beschikbaar

by Marco Rietveld 10. september 2012 12:43
De cumulative updates van Augustus 2012 voor SharePoint 2010 zijn beschikbaar.
Deze update is een Post SP1 update, dit betekend dat Service Pack 1 voor SharePoint 2010 geïnstalleerd moet zijn voordat deze CU geïnstalleerd kan worden

De Cumulative updates kunnen hier gedownload worden:

Voor SharePoint 2010 server is het voldoende om de SharePoint Server 2010 CU te installeren, deze bevat ook de SharePoint Foundation 2010 CU.

Na de installatie, start de SharePoint Products and Technologies Configuration Wizard. Dit moet worden uitgevoerd op iedere SharePoint server in de SharePoint Farm.

De Microsoft KB Artikelen:

  • KB 2687355 - SharePoint Foundation 2010
  • KB 2687353 - SharePoint Server 2010
  • KB 2687354 - SharePoint Server 2010 with Project Server

Test de updates altijd eerst in een testomgeving voordat deze op een productieomgeving worden geïnstalleerd.

Tags: | |

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2014 SharePoint Geek