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

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » The specified schema name "dbo" either does...

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

Rate Topic

Display Mode

Topic Options

Author

Message

nirav284

Posted Wednesday, June 04, 2008 10:36 AM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, July 17, 2008 11:36 PM
Points: 8, Visits: 71

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?

Post #511562

Susantha Bathige

Posted Wednesday, June 04, 2008 10:58 AM

Valued Member

Group: General Forum Members
Last Login: Monday, May 27, 2013 5:53 AM
Points: 52, Visits: 256

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

Post #511578

nirav284

Posted Wednesday, June 04, 2008 11:06 AM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, July 17, 2008 11:36 PM
Points: 8, Visits: 71

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??

Post #511583

Susantha Bathige

Posted Wednesday, June 04, 2008 11:17 AM

Valued Member

Group: General Forum Members
Last Login: Monday, May 27, 2013 5:53 AM
Points: 52, Visits: 256

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

Post #511596

Susantha Bathige

Posted Wednesday, June 04, 2008 1:27 PM

Valued Member

Group: General Forum Members
Last Login: Monday, May 27, 2013 5:53 AM
Points: 52, Visits: 256

The GRANT statement should be as follows;

GRANT EXECUTE ON TO db_execute

Susantha

Post #511728

nirav284

Posted Wednesday, June 04, 2008 1:36 PM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, July 17, 2008 11:36 PM
Points: 8, Visits: 71

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

Post #511738

Raghuram (AJ)

Posted Wednesday, June 04, 2008 3:17 PM

SSC-Addicted

Group: General Forum Members
Last Login: Friday, June 15, 2012 7:53 PM
Points: 494, Visits: 299

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

Post #511819

Michael Niemand

Posted Thursday, September 11, 2008 6:12 AM

Valued Member

Group: General Forum Members
Last Login: Thursday, December 13, 2012 12:51 AM
Points: 55, Visits: 160

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

Post #567649

Michael Niemand

Posted Thursday, September 11, 2008 6:16 AM

Valued Member

Group: General Forum Members
Last Login: Thursday, December 13, 2012 12:51 AM
Points: 55, Visits: 160

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.

Post #567653

« Prev Topic | Next Topic »

Permissions