Posts

Restoring Content Databases between Farms

Have you ever faced scenario where you would like to restore content database between production/test/dev. Here you are the steps: 1- Take SQL backup. 2- Copy backup to the other farm. 3- Attach to the SQL server. 4- from Central admin in the farm you would like to restore to go to application management then content database and select the correct web application. 5- detach the old Database and attach the copied one. Is it ready? Not yet as when you do that the sites will come with the path that was created in the previous farm i.e. contoso.com but in this farm you want it to be contoso-tst.com so how you fix it? run the following commands for each site to modify URL $site = Get-SPSite -Identity  htt p://consoto.com $site.Rename(" http s://consoto-tst.com") The site is now ready. 

OWA Office web App-Troubleshooting

You will need to check claims service is running PowerShell to  provision: $h = Get-SPServiceHostconfig $h.Provision() $services = Get-SPServiceApplication foreach ($service in $services) { $service.provision(); write-host $ service.name } In OWA server some important commands to set verbose logs and to turn it off: Set-OfficeWebAppsFarm -LogVerbosity "High" Restart-Service WACSM Set-OfficeWebAppsFarm -LogVerbosity "" Restart-Service WACSM

Where to troubleshoot User Profile Sync

ForeFront Identity Manager Client ForeFront Identity Manager client is provided by Microsoft to monitor the User Profile Synchronization that takes place in the Synchronization Server. It is located at the below location as “miisclient” application : C:\Program Files\Microsoft Office Servers\15.0\Synchronization Service\UIShell\ then open Miisclient

Adjust the Search SharePoint Performance level

-Set-SPEnterpriseSearchService -PerformanceLevel PartlyReduced On all search app servers -Open NodeRunner process configuration file below in Notepad C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config. Update  <nodeRunnerSettings memoryLimitMegabytes=”0 ″ /> . This is the configuration to limit NodeRunner process memory usage, replace  0  to 500 or 1000 -Restart  SharePoint Search Host Controller  service

Merge ULS logs

Commands to generate ULS logs during troubleshooting Set-SPLogLevel -TraceSeverity VerboseEx -Identity *Search*:* New-SPLogFile $starttime = get-date //do the operations $enddate = get-date Clear-SPLogLevel -Identity *Search*:* Merge-SPLogFile -Path e:\Crawllog.log -StartTime $starttime -EndTime $enddate Merge-SPLogFile -Path e:\zellber1.log -StartTime "04/30/2018 9:00" -EndTime "04/30/2018 18:00" Clear-SPLogLevel 

Adjust Distributed Cache and STS

https://www.habaneroconsulting.com/stories/insights/2013/sharepoint-2013-distributed-cache-bug#.VC7331fdb3U https://blogs.msdn.microsoft.com/sambetts/2015/10/20/why-sharepoint-check-permissions-can-give-wrong-results-for-ad-groups/ Modified sts external token instead of 1 day to 2 hours $cs = [Microsoft.SharePoint.Administration.SPWebService]::ContentService $cs.TokenTimeout = New-TimeSpan -Hours 2 $cs.Update() Added    <appSettings><add key="backgroundGC" value="true"/></appSettings> in the distributed DistributedCacheService.exe.config Then I will need to set the following: Get-SPDistributedCacheClientSetting   -ContainerType   DistributedLogonTokenCache $DLTC   =  Get-SPDistributedCacheClientSetting   -ContainerType   DistributedLogonTokenCache $DLTC.maxBufferPoolSize =  "1073741824" $DLTC.maxBufferSize =  "33554432" $DLTC.requestTimeout =  "3000" $DLTC.channelOpenTim

Usage and Popularity Trends Report not showing correct numbers

Recently came into issue that popularity trends showing zero while users are accessing documents so I have that there is a parameter called TailTrimming as mentioned in this reference blog   https://blogs.technet.microsoft.com/tothesharepoint/2014/01/23/view-and-configure-usage-analytics-reports-in-sharepoint-server-2013/ For example, for the Views usage event the TailTrimming parameter is by default set to 3. This means that the usage analytics reports will be updated for an item when the item has been viewed a minimum three times within the last 24 hours. For example, if the item Fabrikam Laptop16 M6000 has been viewed twice within the last 24 hours, these two views won’t show up in the usage analytics reports. If within the next 24 hours the Fabrikam Laptop16 M6000 item is viewed 4 times, the usage analytics report will be updated with 4 views. to adjust it needs to run the following commands $SSP = Get-SPEnterpriseSearchServiceApplicationProxy $tenantConfig = $SSP.GetAn