<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Administering
»
The server principal "domain\sqlman" is not...
13 posts, Page 1 of 2
1
2
»»
The server principal "domain\sqlman" is not able to access the database "test_DBA" under the current security context
Rate Topic
Display Mode
Topic Options
Author
Message
Bhuvnesh
Bhuvnesh
Posted Tuesday, August 12, 2008 7:00 AM
SSCrazy
Group: General Forum Members
Last Login: Tuesday, March 26, 2013 8:41 AM
Points: 2,562,
Visits: 3,451
while executing a job it gives error
Executed as user: domain\SQLMan. The server principal "domain\sqlman" is not able to access the database "test_DBA" under the current security context. [SQLSTATE 08004] (Error 916). The step failed.
Please suggest
-------Bhuvnesh----------
While 1 = 1 (Learning SQL....)
Click to get fast response of your post
Post #550938
Lenny-319914
Lenny-319914
Posted Tuesday, August 12, 2008 7:03 AM
SSC Eights!
Group: General Forum Members
Last Login: Tuesday, October 23, 2012 11:34 AM
Points: 944,
Visits: 403
is domain\sqlman a user of that database? does it have a user account under the security tab in that database?
Post #550942
Wilfred van Dijk
Wilfred van Dijk
Posted Tuesday, August 12, 2008 7:23 AM
SSC Eights!
Group: General Forum Members
Last Login: Wednesday, March 06, 2013 12:56 AM
Points: 898,
Visits: 1,045
lazy solution: change job owner to SA
Wilfred
The best things in life are the simple things
Post #550969
Ken_R_Vickers
Ken_R_Vickers
Posted Tuesday, May 12, 2009 10:10 AM
Forum Newbie
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 8:29 AM
Points: 1,
Visits: 16
If you have SQL Server 2008 (100) Web Edition then in sp_add_jobstep do not supply @database_user_name or in the GUI supply a run as user as this will result in a spurious error indicating the user does not have permission!
You just have to run with SQL Agents permission set.
Post #715258
GabyYYZ
GabyYYZ
Posted Wednesday, May 13, 2009 7:50 AM
Right there with Babe
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 11:54 AM
Points: 795,
Visits: 1,981
Ken_R_Vickers (5/12/2009)
If you have SQL Server 2008 (100) Web Edition then in sp_add_jobstep do not supply @database_user_name or in the GUI supply a run as user as this will result in a spurious error indicating the user does not have permission!
You just have to run with SQL Agents permission set.
A possible workaround if you don't want to have the owner be sa is to have the user be a member of msdb and grant the the SQLAgentOperatorRole in msdb. See if that works.
But to be honest, either use sa or a dedicated service account with enough permissions. It's better if the job runs under that context.
Gaby
________________________________________________________________
"In theory, theory and practice are the same. In practice, they are not."
- Albert Einstein
Post #715996
TryException
TryException
Posted Saturday, July 04, 2009 4:06 PM
Forum Newbie
Group: General Forum Members
Last Login: Tuesday, July 21, 2009 9:59 AM
Points: 1,
Visits: 7
The solution is pretty simple:
http://www.kf7.co.uk/sql-server-principal-not-able-access-database.aspx
SQL Server Management Studio uses sql script to get a list of databases and related information. If you do not have enough rights to retrieve the related pieces of information then you may get this error.
Post #747269
billdunf
billdunf
Posted Tuesday, October 13, 2009 4:56 PM
Forum Newbie
Group: General Forum Members
Last Login: Sunday, January 17, 2010 9:51 PM
Points: 2,
Visits: 7
TryException (7/4/2009)
The solution is pretty simple:
http://www.kf7.co.uk/sql-server-principal-not-able-access-database.aspx
...
Isn't that solution only applicable to SQL Server 2008?
I can't see how to fix it in SQL Server 20065 Express
Post #802457
SQLRNNR
SQLRNNR
Posted Tuesday, October 13, 2009 5:22 PM
SSCoach
Group: General Forum Members
Last Login: Yesterday @ 6:30 PM
Points: 18,733,
Visits: 12,330
Are the sql services running for that instance?
Is the domain account locked or expired - or did the password change recently?
Jason
AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server 2008
SQL RNNR
Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #802460
billdunf
billdunf
Posted Tuesday, October 13, 2009 7:17 PM
Forum Newbie
Group: General Forum Members
Last Login: Sunday, January 17, 2010 9:51 PM
Points: 2,
Visits: 7
In my case the solution turned out to be permissions related.
I needed to grant CONNECT and CONNECT REPLICATED
and that was sufficient.
Post #802477
adia109
adia109
Posted Saturday, December 05, 2009 1:29 AM
Forum Newbie
Group: General Forum Members
Last Login: Sunday, December 06, 2009 2:46 PM
Points: 1,
Visits: 2
Ken_R_Vickers (5/12/2009)
If you have SQL Server 2008 (100) Web Edition then in sp_add_jobstep do not supply @database_user_name or in the GUI supply a run as user as this will result in a spurious error indicating the user does not have permission!
You just have to run with SQL Agents permission set.
It works! I have SQL 2008 Standard Edition. I don't supply that parameter, and the job run with this user NT AUTHORITY\SYSTEM
Post #829370
« Prev Topic
|
Next Topic »
13 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
