If you could just fix SharePoint... That would be great.

Solving yet another “Microsoft.SharePoint.Client.ServerException: Unknown Error”

There are a thousand possible things that can throw a “Microsoft.SharePoint.Client.ServerException”, but fewer things, that are ambiguous enough to be called “Unknown error”. This post describes one fairly usual fix for this issue! But let’s get back to the beginning for a second – you get what and when now?…Continue reading Solving yet another “Microsoft.SharePoint.Client.ServerException: Unknown Error”

Get-Command -Module AzureRM.Profile. You're seeing it correctly - it doesn't have a Logout-AzureRmAccount, Disconnect-AzureRmAccount, Remove-AzureRmAccount or even Remove-AzureRmContext commandlets! That's a lot of fun :)

Oh no! PowerShell cached my Azure credentials and I messed up wrong customer’s environment!

Whoops. This could happen to anyone since the Azure PowerShell (approximately) version 6.3.0 will cache your credentials between sessions without warning you. It’s really easy to run your commands with cached accounts and end up executing your scripts against the wrong environment. In less serious cases, this means that you’ll end up…Continue reading Oh no! PowerShell cached my Azure credentials and I messed up wrong customer’s environment!

If you could just fix SharePoint... That would be great.

Fixing “-2147024891, System.UnauthorizedAccessException” when accessing SharePoint SOAP Web Services

This article explains how to fix error 2147024891 (or sometimes -2147024891), “System.UnauthorizedAccessException” when accessing functionality in SharePoint that’s built on top of SOAP Web Services. In a sense, we’re delving into some legacy stuff – Microsoft has still kept SOAP-based SharePoint Web Services included in the product, since a lot…Continue reading Fixing “-2147024891, System.UnauthorizedAccessException” when accessing SharePoint SOAP Web Services