Job Ownership: No object was found with the name "[sa]"....

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 Administration » Job Ownership: No object was found with the...

Job Ownership: No object was found with the name "[sa]"....

Rate Topic

Display Mode

Topic Options

Author

Message

Stamey

Posted Friday, November 06, 2009 8:41 AM

SSC Veteran

Group: General Forum Members
Last Login: Thursday, April 11, 2013 11:44 AM
Points: 222, Visits: 866

When I create a job it typically creates the job with my account as the owner, e.g. domain\login. The jobs fail regularly because SQL Server is unable to determine if my login ID has server access. This is stupid, and another typical problem I have run into for years. Anyway, since this occurs often, when I create a job I change the owner to SA so that SQL Server will run it without complaint. I have noticed lately though, that if I change this in SQL 2008, and select "sa" from the list of users, I get the message "No object was found with the name "[sa]", but objects with names containing "[sa]" were found. Select one or more names from this list of click Cancel to re-enter the name."

It presents a list of users, of which none contain the string "[sa]", except, low and behold, "[sa]". See attached image.

This seems to be the dumbest thing I have ever seen SQL Server do.

Anyone else ever run into this?

Thanks,
Chris

Learning something new on every visit to SSC. Hoping to pass it on to someone else.

Post Attachments

SQLError.JPG (10 views, 30.90 KB)

Post #814963

Grant Fritchey

Posted Sunday, November 08, 2009 10:32 AM

SSChampion

Group: General Forum Members
Last Login: Today @ 12:48 PM
Points: 13,381, Visits: 25,169

That is odd behavior. Have you disabled or modified the SA account in some way?

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software

Post #815585

Steve Jones - SSC Editor

Posted Sunday, November 08, 2009 11:47 AM

SSC-Dedicated

Group: Administrators
Last Login: Today @ 12:49 PM
Points: 31,432, Visits: 13,742

Could someone have renamed "sa" with a character in there? Something unprintable.

If not, can you pick this "sa" and will it work? Can you enter [sa] in the box?

Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help

Post #815587

P Jones

Posted Monday, November 09, 2009 5:49 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, May 20, 2013 7:35 AM
Points: 515, Visits: 1,016

I can get this in SQLServer 2005 (with various different servers) if I go to a job in my Management Studio (version 9.00.4035.00), right click and select properties and click the ... box for Owner. Type sa in the object names to select and click OK. Gives message as above and list of so-called matching objects to select from - none match except sa of course!
Selecting Check Names gives the same result but I note that the result set for these two is limited to sys admins whilst selecting Browse button gives every user. This makes me wonder if it is also filtering on server role (sySAdmin) as well as name - I don't have any procesSAdmins.

Post #815758

Steve Jones - SSC Editor

Posted Monday, November 09, 2009 8:30 AM

SSC-Dedicated

Group: Administrators
Last Login: Today @ 12:49 PM
Points: 31,432, Visits: 13,742

Very strange. I think that someone has messed with the SA account somehow. I haven't seen this reported anywhere.

You could do one of two things. Either you can create another account and set credentials there, use it only for this.

Or call MS.

Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help

Post #815823

Stamey

Posted Monday, November 09, 2009 8:40 AM

SSC Veteran

Group: General Forum Members
Last Login: Thursday, April 11, 2013 11:44 AM
Points: 222, Visits: 866

I am not aware of any changes to the SA account. The standard for it here is assign it a 50+ character complex PW and forget about it. No one actually logs in with it unless there is an emergency.

Thanks,
Chris

Learning something new on every visit to SSC. Hoping to pass it on to someone else.

Post #815829

Ron Perron

Posted Wednesday, January 11, 2012 4:18 PM

Forum Newbie

Group: General Forum Members
Last Login: Saturday, January 28, 2012 6:33 AM
Points: 7, Visits: 23

The same issue surfaced in my environment with SQL 2008 after restoring a database taken from SQL 2000. I already tried the ALTER USER WITH LOGIN command to attempt ro repair the suspect orphaned user but this did nothing to eliminate this problem. I'm not sure though if I have the correct syntax. Soory ot a DBA. Incidentally, this dilemma happens with every user I try to change Job Owners not just 'sa'.

Anyone figure this one out yet?

Post #1234455

Ron Perron

Posted Tuesday, January 24, 2012 3:05 PM

Forum Newbie

Group: General Forum Members
Last Login: Saturday, January 28, 2012 6:33 AM
Points: 7, Visits: 23

Looks as though the SQL User Interface is messed up. I opened a Support Case with Microsoft. They confirmed a coding problem and subsequently filed two Bugs for UI changes in the Select Login dialog box.

In short, this appears to be normal behaviour....for now... Wink

Post #1241245

« Prev Topic | Next Topic »

Permissions