The specified schema name "dbo" either does not exist or

Question

Post reply

The specified schema name "dbo" either does not exist or

nirav284

SSC-Addicted

Points: 488
More actions
June 4, 2008 at 10:36 am

#125538

we have created a database role named db_execute and
we have granted permission to this role on bunch of SPs
so members of that role can execute those SPs.
one of the (user)account is a member of this role
when I execute that SP in backend from this account it runs fine but
when developers call it from front end with same account they gets this error
Unexpected Database error -
ErrorNamespace: DB.SqlServer
ErrorNumber:2760
The specified schema name "dbo" either does not exist or you do not have permission to use it.
Whats should be the work around??Where should I check now?

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Susantha Bathige Ten Centuries Points: 1040 More actions · Answer 1

Make following things;

1.The particular users are belongs to the db_execute role.

2.The sprocs are given the EXECUTE permission for db_execute role. You can use the below script to see list of procs which do not have EXECUTE permission granted.

SELECT * FROM sysobjects a

LEFT JOIN syspermissions b

ON a.id=b.id

WHERE a.xtype='P'

AND b.id IS NULL

Susantha

nirav284 SSC-Addicted Points: 488 More actions · Answer 2

Thanks for the reply but yes the particular user belongs to that role

and I did run that script already and I can see some 10 SPs but

they are not really taking part in the picture

so we didnt give any permission to them

also if I can run a trace will that help me in permission things??

Susantha Bathige Ten Centuries Points: 1040 More actions · Answer 3

If you use the script under the correct DB it should return all the sps which do not have EXECUTE permission.

If you know the trouble making sp, use the below statement to give permission.

GRANT EXECUTE ON TO db_execute

Susantha

Susantha Bathige Ten Centuries Points: 1040 More actions · Answer 4

The GRANT statement should be as follows;

GRANT EXECUTE ON TO db_execute

Susantha

nirav284 SSC-Addicted Points: 488 More actions · Answer 5

I appreciate your reply but I already supp;ied Grnt execute on those SPs which I am calling or application calls..

So looks like its something else

Raghuram (AJ) Ten Centuries Points: 1214 More actions · Answer 6

You may re-veriry how the front end is obtaining connection to the database. Indeed, the ideal way would be Windows Authentication and the logins you include as a part of the role are WINDOWS logins of the users.

The vision must be followed by the venture. It is not enough to stare up the steps - we must step up the stairs. - Vance Havner

Michael Niemand Ten Centuries Points: 1149 More actions · Answer 7

I have a similar problem.

I try to create a view from our database application, which fails with the error mentioned in the first posting (the user has the CREATE VIEW-permission).

Funny thing is, that if I log onto Management Studio with the same user and run the same statement, it works. :blink:

Michael Niemand Ten Centuries Points: 1149 More actions · Answer 8

Ok, I should have checked all the tabs I opened before posting here. Found a solution:

I ran

GRANT ALTER ON SCHEMA::dbo TO RoleName

and it worked.