I have had this error and have been able to resolve it by closing and reopening Visual Studio and/or restarting the blackpearl service on the blackpearl server.
I have a blog post which has some additional tips on debugging failed deployments with cryptic error messages which you should check out if the above doesn't work for you.
http://www.k2thought.com/?p=8
Though the post doesn't focus on your particular error, the steps recommending (creating a deployment package/running the k2 service in console mode) are usually the best method for tracking down deployment issues.
Colin
K2 Insider
K2 Blog:
K2 Thought