Thanks for posting that Chris. I just had that problem with the SQL 2008 32-bit Developer edition.

It threw the same error when trying to un-disable it through SQL Server...