Hurrah! Long gone are the days of frantically worrying whether or not your flashy new website is going to display nicely in IE5 and Netscape (‘Nutscrape’ Lolz) and the heady days of Firefox (you know, before it became total bloatware.) HTML5, CSS3.0, frameworks like Bootstrap and even - would you believe it - some form of agreement amongst the browser manufacturers on what should work irrespective of what you’re viewing it in means that a lot of the old challenges are gone.

Below follows some notes on an issue I recently encountered and spent best part of a day troubleshooting. This was occurring in a small SharePoint environment but I suspect it could occur in any environment which has some sort of distributed call to a SQL Server.

TL;DR - it was the Dell KACE Agent. See the end of the article for more.

In this case though, there was a SharePoint application server, and a SharePoint WFE that every half hour was showing an error in their event logs with EventID 3351. I noticed the errors were staggered - i.e. one server was at 15 and 45 minutes past the hour and the other was at approx 20 and 50 minutes past the hour.

Ah, the danger of the Internet. I hit this problem - trying to update a field built-in to a content type (the Title field) so that it was hidden from the UI. Easy I thought, get the SPWeb, get the SPContentType, find the field (ct.Fields[“Title”]), set it to hidden and update it. Nope.

Exception: This functionality is unavailable for fields not associated with a list

Engaging my brain / memory resolved this, but not before I encountered numerous “helpful” posts on the web about how what I was trying to do was not possible. One such example here, which categorically stated…

This is a fun one. In some of our Visual Studio solutions we use the period character - “.” - for project naming which broadly reflects the namespaces in use.

However, this causes issues for Visual Studio namely in the ability to rename features. So when you create a feature, it will adopt a default name of Feature1 and it’s not possible to rename it directly from within the solution.

Fortunately, there’s a nifty workaround that does appear to work, without having to redo your solution/project structure and naming convention. Found via this post:

Little reminder about something that has just kept me busy for the last hour or so - internal field names in SharePoint lists have a max length of 32 characters. SharePoint treats this a little bizarrely - it will create the column but then truncate the internal field name. Thus is you’re doing this programmatically - and then depending on the column existing with that particular field name, things will fall over. You’ll probably see an error like

I own the Brita Elemaris water jug. Very happy with it as it’s slimline and fits neatly in the fridge. Could be a bit bigger, but hey, couldn’t most things.

The mini LCD readout on the top is pretty useful for knowing when to change the filter. I actually run it through twice, but nevertheless it’s good to know when it’s time to change. The readout is supposed to last 5 years and is not user serviceable. Well, I’m sad to report that it won’t last 5 years but fortunately it is is user serviceable. I’m sure they only tell you it’s not serviceable to get you to buy a new one, and although the jug is pretty cheap nowadays, I didn’t feel like splashing out £15 to replace a £2 battery.

This post will help you to get gnucash running with MySQL on OS X 10.10.

Background

I do the bookkeeping and accounts for a variety of small NFPs or charitable organisations. I recently moved my bookkeeping for these from a combination of Sharepoint (seriously) and SSRS and Excel in to Gnucash. I had been looking for a decent free app for a while and whilst there are some interesting cloud options (in fact there are a million options) I stumbled across Gnucash - a nice looking open source, cross-platform tool that would work on my Mac (without X11) and decided to go for it.

I continue to do some work in SharePoint 2010 which means I continue to trip over weird issues.

Issue 1: Error creating content type. A duplicate content type was found.

Matt covers this issue:

If you’ve gotten this error and come to this site looking for answers, chances are it isn’t simply because the name you’re trying to give a new content type is already in use. On the contrary, you are probably sitting there saying that you know without a doubt the name you are entering is not in use, and you have probably even pounded a random value out on your keyboard just to prove the point.

Read more

This event log error will occur in Sharepoint 2010 or SharePoint 2013 environments with SQL Server 2012 and SSRS in integrated mode. You will see either

“SQL Server Reporting Services Shared Service cannot load the SQLPDW extension. (Application: [service app name]. CorrelationId: etc.)”

or

“SQL Server Reporting Services Shared Service cannot load the TERADATA extension. (Application: [service app name]. CorrelationId: etc.)”

This link explains some of the reasoning behind it.

This error occurs because the Teradata extension is registered in the Reporting Services configuration file by default, but the Teradata assemblies are not shipped with SQL Server 2008 or as part of the .NET Framework. If the error message does not bother you, you can ignore the error when it is logged.

Read more

There are a huge number of articles out there discussing how to create (semi-) dynamic list views or filters based on some volatile property like current time. For instance: “Show me all documents that were created today” or “Show me all documents that were created more than 7 days ago” or “Show me all in tasks due in the next three days”. The solution to this is some combination of a list view filter, or calculated column, and the use of a property like [Today]. (Note: There are a couple of key caveats to do with this.)

A limitation of this, however, is that the time portion of a datetime is ignored. So when I wanted to “show all documents created in the last 10 minutes” - I couldn’t. There were a few workarounds - various combinations of calculated columns, using SharePoint Designer and so on were available - but I was determined to find a solution that didn’t require any of this!