Not that I know of. Do you have the specific error?
Just a thought. If you haven't already done this you might try making a backup copy and opening the package up in the 2012 tools. It will want to upgrade it. Upgrade it and see if that fixes your problem. I know that the packages are not completely compatible between versions of Visual Studio so it isn't a big leap to think that you have to have an upgraded version to run correctly from a 2012 job.
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]