x

specified owner doesn't exist or you ain't got permission to use it!

Hi folks,

Currently I live in Shakingheadwitsend. I recognize this probably isn't a wholly SQL issue. But it is SQL that's kicking back on me.

New server, new install SQL2000. yes, its old, until the last two days its been quite reliable. Frustrating too, I've compared logins and user properties on other servers where the same scenarios runs without a hitch and see no differences -- or at least don't see the difference causing the trouble.

ASP app access db via vbscript. That's fine. Server access is via IUSR. The problem is in a stored procedure where a table is dropped and created/populated.

The owner of the table in question is 'webuser' (a standard user). the USP has code, to the effect of, 'Select firstname, lastname from Clients into webuser.BC2009300' and then grants 'GRANT select ON [webuser].[BC2009300] TO [public]' Not sure which of those is the culprit that causes the error: "Specified owner 'webuser' either does not exist or you do not have permission to use it (80040e14)." kicks in. Both IUSR and webuser are members of public

I can create, populate and grant the file using the usp in Query Analyzer no prob. file created, populated. Run it again, its dropped, created and populated. If I create it via QA and then run the USP via ASP I get a similar rights issue error on the 'drop table[webuser].[bc2009300]'

As I said at the top this might not be a 100% sql issue. It strikes me that IUSR_server has some conflict with communicating who it is to SQL as far as its rights to operate under the aegis of webuser.

Do you need more info? Any thoughts? direction? away from Shakingheadwitsend?

thanks Bryan

more ▼

asked Oct 27 '09 at 08:17 PM in Default

bryanC gravatar image

bryanC
11 1 1 1

(comments are locked)
10|1200 characters needed characters left

1 answer: sort voted first

If the query is static, simply remove the INTO webuser.BC2009300 line and delete the data from the table.

If the table name isn't static...

Check and make sure that the WebUser user exists, and that the user you are logging into the database with has the rights to create tables. You might want to setup the user which is running the stored as the dbo of the database just to make life easier.

more ▼

answered Oct 27 '09 at 08:59 PM

mrdenny gravatar image

mrdenny
908 3

(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

New code box

There's a new way to format code on the site - the red speech bubble logo will automatically format T-SQL for you. The original code box is still there for XML, etc. More details here.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.

Topics:

x472

asked: Oct 27 '09 at 08:17 PM

Seen: 848 times

Last Updated: Oct 27 '09 at 08:17 PM