InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 19 May 2013 11:40:14 GMT20http://www.sqlservercentral.com/Forums/Topic550938-146-1.aspxThanks -- 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.Wed, 16 Mar 2011 13:33:30 GMTHoly Onehttp://www.sqlservercentral.com/Forums/Topic550938-146-1.aspxI found the solution to this problem.use msdbgrant connect to guestgoAaronMon, 24 May 2010 07:57:10 GMTAaron.Christenson.ctrhttp://www.sqlservercentral.com/Forums/Topic550938-146-1.aspxHi Bhuvnesh,Did any of the suggestions help you to solve your problem?Sat, 05 Dec 2009 06:35:16 GMTIgnacio A. Salom Rangelhttp://www.sqlservercentral.com/Forums/Topic550938-146-1.aspx[quote][b]Ken_R_Vickers (5/12/2009)[/b][hr]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.[/quote]It works! I have SQL 2008 Standard Edition. I don't supply that parameter, and the job run with this user NT AUTHORITY\SYSTEMSat, 05 Dec 2009 01:29:11 GMTadia109http://www.sqlservercentral.com/Forums/Topic550938-146-1.aspxIn my case the solution turned out to be permissions related.I needed to grant CONNECT and CONNECT REPLICATEDand that was sufficient. Tue, 13 Oct 2009 19:17:34 GMTbilldunfhttp://www.sqlservercentral.com/Forums/Topic550938-146-1.aspxAre the sql services running for that instance?Is the domain account locked or expired - or did the password change recently?Tue, 13 Oct 2009 17:22:27 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic550938-146-1.aspx[quote][b]TryException (7/4/2009)[/b][hr]The solution is pretty simple:[url=http://www.kf7.co.uk/sql-server-principal-not-able-access-database.aspx]http://www.kf7.co.uk/sql-server-principal-not-able-access-database.aspx[/url]...[/quote]Isn't that solution only applicable to SQL Server 2008?I can't see how to fix it in SQL Server 20065 ExpressTue, 13 Oct 2009 16:56:10 GMTbilldunfhttp://www.sqlservercentral.com/Forums/Topic550938-146-1.aspxThe solution is pretty simple:[url=http://www.kf7.co.uk/sql-server-principal-not-able-access-database.aspx]http://www.kf7.co.uk/sql-server-principal-not-able-access-database.aspx[/url]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.Sat, 04 Jul 2009 16:06:50 GMTTryExceptionhttp://www.sqlservercentral.com/Forums/Topic550938-146-1.aspx[quote][b]Ken_R_Vickers (5/12/2009)[/b][hr]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.[/quote]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.Wed, 13 May 2009 07:50:58 GMTGabyYYZhttp://www.sqlservercentral.com/Forums/Topic550938-146-1.aspxIf 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.Tue, 12 May 2009 10:10:54 GMTKen_R_Vickershttp://www.sqlservercentral.com/Forums/Topic550938-146-1.aspxlazy solution: change job owner to SATue, 12 Aug 2008 07:23:31 GMTWilfred van Dijkhttp://www.sqlservercentral.com/Forums/Topic550938-146-1.aspxis domain\sqlman a user of that database? does it have a user account under the security tab in that database?Tue, 12 Aug 2008 07:03:20 GMTLenny-319914http://www.sqlservercentral.com/Forums/Topic550938-146-1.aspxwhile 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 suggestTue, 12 Aug 2008 07:00:03 GMTBhuvnesh