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!

I’m posting this here as, despite using this all the time, I still find myself looking it up.

There are a couple of things you can do, in your Dev environment, to assist with debugging SharePoint and your custom solutions.

CustomErrors and SafeMode

This should only be used in a Dev environment, but you can disable the “friendly” error messages in SharePoint and replace them with full exceptions, and, if desirable, a stack trace.

You can edit the web.config for your application. Note: SharePoint has various web.configs spewed about the place, and for this to work, you need to edit the one located in

Using SharePoint Workflow (in fact, Nintex, but it applies to “standard” SharePoint workflow, after all, Nintex is just standard workflow with a few bells and whistles) on a document library and a workflow that is set to auto-start on document creation.

The symptoms were: if you add a document to the library, then the workflow fires, but it sits forever in a state of “starting”. However, if you manually start the workflow on the same document, then it runs absolutely fine.

If you try to deploy an SSRS report from Visual Studio to your SharePoint environment, where SSRS has been configured in Integrated Mode, using the built-in deployment mechanism, you may encounter a situation where you are endlessly prompted for login boxes, and no account details seem to help.

There is some useful info out there about what causes this - typically a mismatch where you’re using Kerberos authentication. There’s a good post and some resolution here.

When SharePoint goes bad: spurious error messages in the ULS logs that will lead you down a blind path. ULS logs were full of User Profile related errors, all saying moreorless this:

Exception occured while connecting to WCF endpoint: System.ServiceModel.Security.MessageSecurityException: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. —> System.ServiceModel.FaultException: An error occurred when verifying security for the message

Spent a while looking through the UPS app config, Profile DB and everything looked normal. The issue is actually a “generic” WCF error - whereby the system clocks on the App Server (1) and WFE server (2) were out of sync by about 6 minutes. Manually setting the clock on the slow one to the current time resolved the issue.