I am getting the same error, and I have tried the response recommended in the KB article, but I am having the same problem.  I am running a strored procedure...