I just got this error message also on one of my servers. It is also 2008 R2 with SP2, but has had SP2 for a while now.

Did you figure out the SPN and service sid issue? Can the service automatically create it's spn when running with a service sid. In my test environment it isn't able...