Were you able to find a work around to this issue?

I also have encountered a similar error while i was planning to upgrade from Sql 2008 to Sql 2012. Any...