I know. Sharepoint 2010. It’s not even. I mean. Just.

Look let’s skip past any discussion about why this is happening in 2018, and just cover the issues, OK?

So. You’re installing SP2 on a Sharepoint 2010 Farm. This may well apply to any CU in fact. And it possibly applies to SP2013+ also - but at least one of these issues is allegedly caused by a CU that was rolled up in SP2.

Right, that’s enough foreplay.

What happens when you let machine learning type automated systems run your consumer communications.

Review sites need little in the way of introduction about their popularity or indeed importance to the fabric of the modern Internet. The majority of my online shopping is done on Amazon or eBay and the review / rating mechanisms on each of those (of both the product and the supplier) are invaluable in making a decision. Of course with any user-submitted content, as a consumer you need to know how to read a review - learning how to separate the fake / troll-y tat from the genuine is a bizarre new modern skill.

I’ll cut to the chase. A lot has been written about how to handle large lists and how to handle bulk deleting things. To summarise: getting all items and iterating one by one is *not* the way to do it.

The right way to do it is to use the ProcessBatchData method on the SPWeb object.

Have done this plenty of times in C# but this time I wanted to cut straight to Powershell. A quick Google later and I found Daniel Root’s boiler plate. It properly handles checked out files as well, and deletes folders. Ideal!

We needed an ’emergency’ night due to an issue with a part of our ‘main’ holiday booking. Found this on Booking.com and the photos and location looked good and near to the port in St Malo so decided to take a punt.

Top tip #1 though - book direct with them - not through a third party. It was nearly 60euro more expensive through Booking. Apparently rules have changed recently where the venue had to match the 3rd party price and this no longer applies - so the venue can now charge what they like and it seems the 3rd parties haven’t caught up.

As an aside to my other post on SSRS in SharePoint integrated mode, this is a niggly little issue I encountered.

If you find yourself needing to edit a published report and, for whatever reason can’t go back to source to make the change, then a reasonable option is to download a copy of the report from SharePoint and then open it up in your Visual Studio of choice and make the edits. RDL files are pretty great at encapsulating everything they need to run within a single file (they are just XML files, after all) so this is a workable approach.

Visual Studio is a good option for designing SSRS reports. Now, that is. But years ago we had a different toolset. One of those around the 2009/2010 time was ‘Business Intelligence Developer Studio’. This was effecting a Visual Studio shell that had report templates for the various SQL Business Intelligence suite (e.g., SSIS, SSRS, SSAS.) and was installed from the main SQL Server installer. This then morphed in to SQL Server Data Tools which was available as a standalone package.

Q: Does SharePoint 2013 work on SQL Server 2016?
A: No and no.

#mvp (minimum viable post.)

(* Except, it actually does work - it’s just not officially supported by Microsoft.)

Continuing the theme of obscure SharePoint gotchas you’re unlikely to encounter (unless, I assume, you’re reading this) here’s another. One environment was experiencing an issue whereby the SharePoint Tracing Service was constantly getting set to disabled. No amount of editing it in services.msc to set it to Automatic would ‘take’ - that is, you could enable it and start it and it would work - but then at some miscellaneous point later it would mysteriously revert to being disabled.

We were on a long weekend (2 adults, 2 young kids) from a neighbouring island. Looking for a little somewhere to hide and relax for a few days. We might normally have considered somewhere more - what we would thought would be - ‘upmarket’ - but given the prices decided to take a ‘risk’ on this - a so-called 3* property. About the only thing was a must for us was an indoor pool and this does limit your choices somewhat.

I recently had some fun and games trying to fix a broken SharePoint Search Service Application. Although I’m not entirely what caused the issue (other than, you know, SharePoint) although it may be to do with changing the Farm Passphrase but one way or another it was, fooked.

I opted to just delete it and create a new one. This didn’t go well. A new application was created, but it, also, was dead.

As many people have found, Central Admin and Remove-SPServiceApplication have a habit of doing entirely nothing when it comes to remove broken Search Applications.