The KBA waffles on about SQL Server 2005 Backward Compatibility Components, which was not relevant to me. But following Method 2 in the article fixed the problem in no time.