Also don't forget to check out what user account owns the stored procedures and the security role attached to that login. I have had many instances in the past...