Could not load type 'Microsoft.SharePoint.Administration.DesignPackageType'

Submitted by Vladilen on Sun, 11/03/2019 - 20:10

Recently I tried to update module "Microsoft.Online.SharePoint.PowerShell". It was updated OK, but:

Get-Module Microsoft.Online.SharePoint.PowerShell -ListAvailable | ft -a

gave me two modules So I tried to uninstall module with older version "16.0.8525.1200" and import module with newer version. It failed with error: "The version '###' of module '16.0.8525.1200' is currently in use. Retry the operation after closing the applications.

Chef error: VERSION OF THE COOKBOOK COULD NOT BE LOCATED ON THE CHEF-SERVER

Submitted by Vladilen on Sat, 06/01/2019 - 19:14

Chef error:

DETAILS: THE RESULT OF [ CHECKOUT/TEST#1 ] WAS A FAILURE. VERSION '0.1.00XX' OF THE 'your_cookbook_name' COOKBOOK COULD NOT BE LOCATED ON THE [ your.chef.server ] CHEF-SERVER. PLEASE CONSULT THE ACTIVITY-LOG FOR FURTHER DETAILS.

Actually means "you cannot use version number with leading zeroes". I.e., e.g. instead of version number '0.1.0013'  try '0.1.13'

SharePoint powershell automation, DSC and DevOps

Submitted by Vladilen on Wed, 05/08/2019 - 01:07

Automation is not the same as DSC and DevOps.

Automation is about changing existing process - to enable it start and work automatically, without human attendance, i.e. faster and more stable. The good example is site collection provisioning. 

DevOps is an idea to manage infrastructure configuration via code with well-known and proved developers practices - ADLC, version control etc. 

UPA to UIL sync

Submitted by Vladilen on Thu, 04/25/2019 - 18:06

[Microsoft.Office.Server.UserProfiles.WSSProfileSynch]::ScheduleSiteForFullSynchronization()

[Microsoft.Office.Server.UserProfiles.WSSProfileSynch]::ClearSyncDataForContentDatabase()

 

immediate alerts timer job stuck

Submitted by Vladilen on Tue, 03/26/2019 - 03:01

Problem:

Outgoing emails are not sending from one particular site, "immediate alerts" timer job stuck on some specific database, owstimer.exe consumes high memory on one SharePoint server.

You can restart SharePoint timer service (SPTimerV4), but after some time the same happens again. If you have courage to wait enough - you can see 100% CPU load and WFE server not responding.