Well, I can report that the error has gone. I'm not sure which of the following steps taken previously 'resolved' the issue, but last night I re-re configured log shipping. I can only presume that the permissions changes worked but I needed to re-set up log shipping in order for them to take effect.