The problem was because the timer service cached the previous dlls. You have to restart timer service on all servers in the farm before starting any new deployment.
Sharepoint 2010
--------------------------------
net stop SPTimerV4
net start SPTimerV4
Sharepoint 2007
----------------------------------
net stop SPTimerV3
net start SPTimerV3
Sharepoint 2010
--------------------------------
net stop SPTimerV4
net start SPTimerV4
Sharepoint 2007
----------------------------------
net stop SPTimerV3
net start SPTimerV3
Restarting timer service did not work for me, i still received the error; but then i was able to deploy the solution using -force after the first failed attempt.. which means it must be caching somewhere.
ReplyDeleteTimer job assemblies get cached so every time we deploy we need to change the assembly version or restart the timer service to see latest code changes.
Delete