Automation errors when using method level security for db violations

[MudMan2000]

I've had a large COM+ application in production for years now, and have been using COM+ security at the component level without incident. New requirements have raised the need for a more granular security matrix, so we have moved to method level security. The security itself works great; however, for ANY error raised from the SQL Server database (PK violation, required field, etc) we now get "Automation error" for the error description coming out of our COM+ component. If we remove authorization checking at the package level, OR if we move back to component level security, we get the proper error message from the database.

Has anyone encountered this?
Thanks!!!!