This has also worked for me. - granted it was for SP1 CU4
On reviewing the previous logs I could see that a patch done almost 1 year previous had been aborted, hence why the configurationstate was set to 3 and not 1.
Changed them to 1 and jobs a good n
_________________________________________________________________________________SQLGeordieWeb:- Jarrin ConsultancyBlog:- www.chrisjarrintaylor.co.ukTwitter:- @SQLGeordie