Re: permission problem?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 03/08/04 

Date: Mon, 8 Mar 2004 21:08:53 +0100

SQL Agent has an errorlog file, which you for instance can get to from EM,
Management, Right-click Agent.

I suggest you read in Books Online about permissions. Search for "level
token" and you will only get one hot, describing security needed to be in
place for the service accounts. 

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"js" <js@someone@hotmail.com> wrote in message
news:%23V1beiUBEHA.1380@TK2MSFTNGP10.phx.gbl...
> Thanks Tibor.
> There is no errorlog. only a messagebox pupup.
> Error5: Access is denied.
> The user is belong to a Power User group. Still need more permissions for
> agent servie to run?
>
> Can I do this instead:
> Reable "permit" access to BUILTIN\Administraotrs, So the local system
> account won't block.
> and deny access for individual admin instead: domain\admin1,
domain\admin2.
>
>
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote
in
> message news:u8qw4XUBEHA.3748@tk2msftngp13.phx.gbl...
> > What error messages do you have in the SQL Server Agent errorlog?
Perhaps
> it
> > is quite simply a matter of Agent doesn't have permissions on the
registry
> > keys or directories/files that it needs.
> > No, you don't have to be logged in interactively in order for your Agent
> > jobs to run.
> >
> > -- 
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> >
> >
> > "js" <js@hotmail.com> wrote in message
> > news:eBBqWMUBEHA.2440@TK2MSFTNGP12.phx.gbl...
> > > Thanks Tibor.
> > >
> > > I defined a user "BackupUser" as Power Users group. and  add SQL
> sysadmin
> > > permission to it. In order to test, I need to relogin to window as
> > > "BackupUser".
> > > I'm able to to login to SQL.
> > > But when I try to start the SQL Agent service. still got an error:
> > > Service msg box:
> > > Could not start the SQLSERVERAGENT service on Local Computer.
> > > Error5: Access is denied.
> > >
> > > How to fix this one?
> > >
> > > Another question is: If I don't login to windows(interact mode), the
sql
> > > jobs are able to run?
> > >
> > > Thanks again.
> > >
> > >
> > >
> > >
> > >
> > > "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com>
wrote
> > in
> > > message news:%23lAmNuTBEHA.1548@TK2MSFTNGP12.phx.gbl...
> > > > The windows account that Agent uses need to be able to login to SQL
> > > Server.
> > > > You removed the Administrators account from SQL Server, and couldn't
> > > login,
> > > > which indicates that the service account for Agent is Administrator
> (or
> > > some
> > > > other Windows account which is member of the Administrators group).
So
> > far
> > > > no surprise.
> > > >
> > > > The windows group Power Users are not added as logins to SQL Server
by
> > the
> > > > installation program. Make sure that the service account for Agent
has
> a
> > > > login in SQL Server and that login has sysadmin permissions in SQL
> > Server.
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Outlook for MAPI on SBS
    ... I wound up looking at another thread here on installing SQL 2005 which I ... I have noticed something interesting here in SBS ... agent from the SBS Monitoring Agent to the 2005 agent instance. ... Is there an easy way to set up notifications from SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook for MAPI on SBS
    ... I wound up looking at another thread here on installing SQL 2005 which I ... particularly 2005 on SBS. ... agent from the SBS Monitoring Agent to the 2005 agent instance. ... Is there an easy way to set up notifications from SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Setting DCOMCNFG LaunchPermission registry value for everyone group back to "special access"
    ... trying to push content from one SQL server to a cluster server. ... Also this replication ... got TimeOut exipred messages when the agent ran - the specific error message ... SQL Server Agent could not access the replication agent. ...
    (microsoft.public.sqlserver.replication)
  • Setting DCOMCNFG LaunchPermission registry value for everyone group back to "special access"
    ... trying to push content from one SQL server to a cluster server. ... Also this replication ... got TimeOut exipred messages when the agent ran - the specific error message ... SQL Server Agent could not access the replication agent. ...
    (microsoft.public.sqlserver.connect)
  • Setting DCOMCNFG LaunchPermission registry value for everyone group back to "special access"
    ... trying to push content from one SQL server to a cluster server. ... Also this replication ... got TimeOut exipred messages when the agent ran - the specific error message ... SQL Server Agent could not access the replication agent. ...
    (microsoft.public.sqlserver.clustering)