SharePoint 2010 / 2013: Clearing the Configuration Cache
This is a summary of the actions:

  • Stop the “SharePoint 2010 Timer” service.
  • Delete all the XML files in the config cache. There are loads of XML files that can be found in the folder “C:\ProgramData\Microsoft\SharePoint\Config\”. Note there seems to only ever be one folder under Config which has a GUID. There are other folders which map onto this folder, but this one seems to be on every environment whereas the other locations may be found in different places on some environments. Therefore deleting the files from this folder should work in all environments.
  • Edit the “cache.ini” file in the same folder that contained the XML files, setting the content to “1″ (without the double-quotes). This indicates that all cache settings need to be refreshed. Eventually this value gets automatically updated to another number when the cache is repopulated.
  • Start the “SharePoint 2010 Timer” service.

SharePoint 2013: Distributed Cache Cluster
Vorbedingungen:
  • Firewall: AppFabric Caching Service (Inbound/Outbound) aktiviert
  • Firewall: Regel "ICMP rule for Distributed Cash" (Inbound) erstellt. In the Customize ICMP Settings dialog box, do one of the following:
    • To allow all ICMP network traffic, click All ICMP types, and then click OK.
    • To select one of the predefined ICMP types, click Specific ICMP types, and then select each type in the list that you want to allow. Click OK.
    • To select an ICMP type that does not appear in the list, click Specific ICMP types, select the Type number from the list, select the Code number from the list, click Add, and then select the newly created entry from the list. Click OK
  • Remote Registry muss zugängig sein durch die Firewall zwischen den Distributed Cache Hosts (Windows Service)
  • FQDN –Auflöseprobleme in der Config DB: Der zweite Host muss den DNS-Namen des Ersten auflösen können
Danach auf dem zweiten Node folgende Dinge durchführen:
  • $instanceName ="SPDistributedCacheService Name=AppFabricCachingService"
    $serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername}
    $serviceInstance.Unprovision()
  • But above command failed saying "cacheHostInfo is null"
    $serviceInstance.delete()
    # Cleared Sharepoint Timer cache.
    # Then Ran : Add-SPDistributedCacheServiceInstance

Traceinformationen sammeln mit IntelliTraceCollector
http://msdn.microsoft.com/en-us/library/vstudio/hh398365.aspx

Vorbedingungen:
  • Die Eigenschaft "Load User Profil" muss für den Anwendungs.AppPool auf true stehen
  • Der Account des Anwendungs.AppPool muss auf dem Trace-Verzeichnis schreibend berechtigt sein
  • Import-Module "C:\IntelliTraceCollector\Microsoft.VisualStudio.IntelliTrace.PowerShell.dll"
  • Start-IntelliTraceCollection "Anwendungs.AppPool" C:\IntelliTraceCollector\collection_plan.ASP.NET.default.xml C:\IntelliTraceCollector\trace
  • Stop-IntelliTraceCollection "Anwendungs.AppPool"

Stateservice per PS anlegen
$serviceApp = New-SPStateServiceApplication -Name "Name State Service"
New-SPStateServiceDatabase -Name "Name State Service DB" -ServiceApplication $serviceApp
New-SPStateServiceApplicationProxy -Name "DName State Service Proxy" -ServiceApplication $serviceApp -DefaultProxyGroup

Url's
URLBezeichnung
/_layouts/15/closeconnection.aspx?loginasanotheruser=trueBenutzerwechsel
/?Contents=1Zeigt alle WebParts an
/_catalogs/users/detail.aspxUserInformationList
_layouts/15/Dataport/SharePoint/Claims/Providers/domainlocals/Claims.aspxClaims
/_windows/default.aspx?ReturnUrl=%2f_layouts%2f15%2fAuthenticate.aspx%3fSource%3d%252F%255Fwindows&Source=%2F_windowsBei ADFS Authentifizierung als WindowsUser anmelden