What happens when you try any of the other tables? I would suggest looking at the ownership of the tables (and database) too. Is sa the owner of the database?
Main Topics
Browse All TopicsBelow is a stored procedure I created as SysAdmin (User 'sa') to be able to truncate selected tables with an user that has not the permission to do this by default. It worked until today. What have happend? Can someone help?
If I execute the query:
EXEC [sp_cu_TruncateTable] 'FingerWeg'
I am getting the error:
Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Try this. It is for 2005 but may still be applicable in 2008.
http://support.microsoft.c
Lee
Business Accounts
Answer for Membership
by: lsavidgePosted on 2009-08-04 at 03:32:06ID: 25012074
One thing to note that probably is not the cause of the issue. Do not name your stored procedures with sp_ as the prefix. sp_ sp's are the system stored procedures. Ones that are prefixed with xp_ are extended stored procedures. I'll look at the error in a sec.
Lee