Had this issue in using a SQL Server CLR Assembly.
Normally this issue arises if you have restored the database to a new server.
Check whether the owner has been assigned for the database.
Drop and Create the assembly and make to put the path of the assembly in plain text rather than scripting it from another environment as it would have been encoded and won't work on this server.
Technorati Tags: SQL Server,CLR