Cannot find the object “XXX” because it does not exist or you do not have permission
https://stackoverflow.com/questions/1601562
-
05-07-2019 - |
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
RussianQuestion
I'm getting the following error when calling a stored procedure:
Cannot find the object "XXX" because it does not exist or you do not have permission.
I've checked the database and the SP is there with the correct permissions yet I'm still getting the error.
Any suggestions?
Solution 2
Ok, here's what happened. There was a special character before the end of the SP so it was incomplete yet still valid, somehow.
So I could see the SP and see the permissions on it but I could not run it. So to solve the issue I had to copy the text out of SQL Management Studio and paste it into Notepad, then remove the special character, then copy and paste it back into SQL Management Studio and run the alter script.
Very strange how the character got there!
OTHER TIPS
I discovered that I had left off the "GO" word after "END" in my stored proc. Altering the Proc and adding back GO fixed this issue for me.
Similar to marked answer: The final line of my stored procedure was a line which granted permission to the stored procedure to run as the appropriate user - probably added there when I generated a script.
Removing that (or perhaps a hidden character attached) managed to fix it.
"XXX" was the name of the stored procedure I called, successfully (it made the desired change) but which gave me this error.
I meet this issue too. In my case, I granted execution permission just after creating stored procedure. And there is no 'GO' between the two statements. I added GO, and it works.
The account that you are using when calling the stored procedure must not be the same account that you are using to check it. Make sure that the account that you are using to execute the sproc has access to the object.
As well as other answers about schema/security etc:
- do you have a DENY on it somewhere?
- case sensitive object names and using "wrong" name?
- wrong database context? eg OtherDB.dbo.Myproc
Using the 'GO' fixed the issue for me as well. This was driving me crazy, after multiple drops and checking permissions for users and schema, this is what finally helped.
In Microsoft SQL server, selected the object in the object explorer that you want to work with, right-clicking it, then doing 'Script [object] as' can give you the script you need to perform an operation successfully without getting this error
Always use the dbo. (or other schema) prefix both when creating and when accessing objects.
I wrote about this very topic recently:
Even after adding 'GO' issue did not fixed for me. Then removed UPDATE STATISTICS [Table_name] statement Then my issue was fixed.
