The server principal "domain\sqlman" is not able to access the database "test_DBA" under the current security context
-
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----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-) -
is domain\sqlman a user of that database? does it have a user account under the security tab in that database?
-
lazy solution: change job owner to SA
Wilfred
The best things in life are the simple things -
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.
-
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
-
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.
-
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
-
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, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events -
In my case the solution turned out to be permissions related.
I needed to grant CONNECT and CONNECT REPLICATED
and that was sufficient.
-
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
-
-
I found the solution to this problem.
use msdb
grant connect to guest
go
Aaron
Aaron
MCITP: Database Administrator, MCITP: Server Administrator, MCTS: Windows Server 2008 Active Directory – Configuration, MCTS: Windows Server 2008 Network Infrastructure – Configuration, MCTS: Windows Server 2008 Application Platform – Configuration, MCTS: SQL Server 2005, MCTS: Microsoft Exchange Server 2007 – Configuration, MCSE 2003, MCSA 2003, MCDBA, Security+, CCNA
https://www.mcpvirtualbusinesscard.com/VBCServer/AaronChristenson/interactivecard -
Thanks -- I had this problem too! The company I work for has things screwed down tight such that the public group can't connect to the db.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply