Uncategorized | Bugra Postaci's Blog

SharePoint IRM – Azure RMS not installed issue

11/06/2019

Recently we have faced an issue to installing Azure RMS Connector version 2.1 on SharePoint 2013 server.

“The required Active Directory Rights Management Service Client (MSIPC.DLL) is not installed, IRM will not work until the client is installed.”

The problem here SharePoint unable to load the module where it is the MSIPC.DLL and returns winerror 126 (0x7e) .

When we investigate the problem we have faced 2 issues.

The DLL location read from registery where the key data has an extra “\” at the end of it.
HKLM_\SOFTWARE\MICROSOFT\MSIPC\CurrentVersion\InstallLocation:
C:\program files\active directory Rights Management Services Client 2.1\ -< HERE
We change it as:
C:\program files\active directory Rights Management Services Client 2.1
Related VC++ Runtime Redistributable package (where msipc.dll have a dependency) is not installed in the server. When we installed VC++ 2012 redistributable issue has been resolved.
https://www.microsoft.com/en-us/download/details.aspx?id=30679

Filed under SharePoint 2013, Uncategorized Tagged with 0x7e, Azure, IRM, MSIPC.DLL, RMS

Update-SPSolution fails for SharePoint 2016

12/03/2019

We have a nasty problem specific for SharePoint 2016 with Update-SPSolution command-let and currently we don’t have a permenant fix for it.

Basically the problem only happens if you run Update-SPSolution (for a specific wsp file) twice or more inside one OwsTimer Cycle period (Default is 24 hours). Timer service recycle timer job is responsible to reset owstimer process. (a.k.a. job-timer-recycle) .The default schedule is Daily at 6:00 AM. We are calling this 24 hours period “OwsTimer Cycle”.

You may face something similar exception below:

Solution Updates fails.

Some of the files failed to copy during deployment of the solution
<server>:c:\windows\temp\solution-<Guid> folder the <solutionname>.wsp could not be created because the contents could not be found under id <guid> in the configuration database.

The workaround of this problem:
When ever you need to run Update-SPSolution commad-let “more than once” for “a single solution file” in one “timer service cycle” duration; you need to reset OWSTimer on all servers (“net stop sptimerv4” then “net start sptimerv4”) between each Update-SPSolution execution (for same wsp file)

Filed under SharePoint 2016, Uncategorized Tagged with Update-SPSolution

About SharePoint with 16+ Cores

19/06/2018 Leave a comment

Well, If you update .Net 4.7.2 or higer it is OK, otherwise it is a bad idea.

More speficially,
ReaderWriterLockSlim with reentrant have design limitation which can lead serious performance down for previous .Net versions. And Sharepoint pretty much depended on this thread syncronization object. Specially Blob Cache and ObjectCache wraps and using them. More CPU causes more thread contention, excesive locking thats brings slowness.

Example callstacks:
SPReaderWriterLock named [BlobCache] waited 43992 milliseconds to acquire lock. Call stack:
at Microsoft.Office.Server.Utilities.SPReaderWriterLock.AcquireLock(Boolean readerLock, Boolean upgradable, Boolean throwException)
at Microsoft.Office.Server.Utilities.SPReaderWriterLock.AcquireLock(Boolean readerLock, Boolean upgradable)

System_Core_ni!System.Threading.ReaderWriterLockSlim.EnterMyLockSpin()
System_Core_ni!System.Threading.ReaderWriterLockSlim.TryEnterWriteLock(Int32)
Microsoft_Office_Server!Microsoft.Office.Server.Utilities.SPReaderWriterLock.AcquireLock(Boolean, Boolean)
Microsoft_Office_Server!Microsoft.Office.Server.ObjectCache.SPCache+MossObjectCache.UpdateUsageMap(System.String, UInt32, UInt32)
Here are some threads about the problem.
https://github.com/dotnet/coreclr/pull/13243
https://github.com/dotnet/coreclr/pull/13495

These issues has been fixed with .Net Framework 4.7.2 version!.

Pls check .NET Framework 4.7.2 Release Notes
https://github.com/Microsoft/dotnet/blob/master/releases/net472/dotnet472-changes.md

Again don’t think about 64cpus makes more performance. It depends of the software boundaries/limitations and several other things..
My suggestion, scale up with multiple machines. It is more cheaper and stable. ! Not with excessive hardwares. (8 cores are fine 🙂 )

If you have that monster machines, don’t worry you can use it with HyperV and scale up VMs.

Filed under SharePoint 2013, SharePoint 2016, Uncategorized Tagged with 16+, 4.7.2, BlobCache, Cores, CPU, EnterMyLockSpin, NET, ObjectCache, ReaderWriterLockSlim, SPReaderWriterLock, UpdateUsageMap

Clean draft versions via PowerShell

10/01/2018 Leave a comment

SharePoint versionining is very cool feature, but in time or setting incorrect version limitations can cause performance issues. When this happen you may want to get rid off older draft versions.

Following script is cleans for older draft versions in a library while keeping all major versions. Also you can keep defined number of last major items drafts available.
Note: This script doesn’t delete any major item.

#USAGE:
# .\CleanDraftVersions.ps1 -siteUrl <Site Url> -webName <webName> -listName <ListName> -versionsToKeep <Number> -delete=<$true|$false>
#PARAMETERS
# -siteUrl : Url of the Site Collection
# -webName : Specific subsite (leave empty for root web)
# -listName : Specific ListName
# -versionsToKeep: Number of major item’s drafts will be preserved (including current version)
# -delete : $false (default) for reporting only ,$true for deleting.
# Highligts: Red will be deleted , Yellow will be preserved , Green current Item .

#EXAMPLE
# .\CleanDraftVersions.ps1 -siteUrl “http://contoso.com” -webName “” -listName “Pages” -versionsToKeep 10 -delete $false
Download:
https://github.com/bpostaci/CleanDraftVersions/blob/master/CleanDraftVersions/CleanDraftVersions.ps1

Filed under Uncategorized