We have also encountered this problem.  Our work-around was to create credentials for a dummy user with dbo access.  This provided the access for users to run stored procedures behind...