Re: Error 22022 when running SQLservices under different accounts

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

From: JD (joeydba_at_yahoo.com)
Date: 12/14/04 

Date: Tue, 14 Dec 2004 14:33:26 -0600

Well, why not have a Domain account created, with the require privs, and
then use this account as the 'log on' account for both services? This is
what we do and it works just fine for us. BTW, ours is not a high level
account. We use this approach because it is what we need for a SQL service
to work across our domains. This allows us to dump the databases directly to
a store box.

HTH

"User" <User@discussions.microsoft.com> wrote in message
news:4C91E01A-5969-4347-BDEB-8008D4B14EEE@microsoft.com...
> Brian is right. I am having the exact same problem. For whatever reason
I
> cannot use two different accounts to run the sql server and the sql
service
> agent. The same two error messages continue to appear in my event log:
> Event ID: 17052 You do not have sufficient operating system permission
to
> opent he SQLServerAgent status event.
> Event ID: 322
> The data portion of event 17052 from MSSQLSERVER is invalid
>
> I noticed that these messages appear even when I double click a job to
check
> its properties in the "Jobs" folder. DOES ANYBODY ELSE HAVE ANY USEFUL
> ADVICE ON HOW TO RESOLVE THIS ISSUE??!!!???
>
>
>
> "Brian Klausen" wrote:
>
> > "Ananth Padmanabham [MSFT]" <ananthp@online.microsoft.com> wrote in
> > message news:u%234rJEWrEHA.3312@cpmsftngxa06.phx.gbl...
> > > If you are using the SQL Enterprise Manager (SEM) to change the
> > service
> > > startup accounts to use a non-admin account, then all should work
> > fine. But
> > > if you suspect that SEM is not setting some relevant file permissions
> > or
> > > registry permissiosn etc for your non-admin account, then you may
> > want to
> > > review this KB article for a complete list of permissions/rights which
> > are
> > > required for your Windows account:
> > >
> > > How to change the SQL Server or SQL Server Agent Service account
> > without
> > > using SQL Enterprise Manager in SQL Server 2000 (283811)
> > > http://support.microsoft.com/default.aspx?scid=KB;EN-US;283811
> >
> > I'm experiencing the EXACT same problem on various boxes - tried the
> > above several times - doesn't help.
> >
> > What helps the best so far, is running SQL Agent and SQL Server on the
> > same low priviledged account - this will enable you to run in a low
> > priviledged environment. But separate accounts won't work, even though
> > you configure them to the same settings. To run separate accounts, you
> > how to run with high privilege (local admin or similar), which sorta
> > defies the purpose.
> >
> > MS should really look into this - I see lots of posts about it - always
> > the same reply - but it just doesn't help.
> >
> > My configuration is:
> > W2K3 Standard - in a domain.
> > Service accounts are local accounts.
> > SQL Server 2000 installed, immidiately updated to SP3a + the cumulative
> > patch pack.
> >
> > Best regards
> > Brian Klausen
> >
> >
> >

Relevant Pages

  • RE: local admin account password
    ... Subject: local admin account password ... > 4) Only use domain accounts so delete the local ones. ... > The DB file would be encrypted with EFS so only the limited user SQL ... > backup user can make a zip backup of the DB whenever it gets changed ...
    (Focus-Microsoft)
  • RE: local admin account password
    ... Say you have more then 1000 systems, how do you handle the local admin ... Only use domain accounts so delete the local ones. ... The DB file would be encrypted with EFS so only the limited user SQL ... There would be basically two stored procs, ...
    (Focus-Microsoft)
  • RE: "login failed for user ..." appears in event viewer repeatedly
    ... OK, did I hear you right, you've determined that the attacks are coming from ... holes to that segment and/or box to just the SQL ports. ... I looked closer at the SQL accounts. ... I used SQL profiler to audit logins and login failures. ...
    (microsoft.public.sqlserver.security)
  • Re: Server or Service Accounts complete lockdown?
    ... SQL Enterprise Manager? ... I wonder if I need to somehow create accounts in each SQL DB to allow ... Heres the strange bit - I have full access but dev team are prompted to ... used by the web application for SQL database access. ...
    (microsoft.public.security)
  • Re: testing vulnerable web application.
    ... You should be able to just open up your logs and look for things that are out of the ordinary. ... Keep your database and all but double check it to make sure there really aren't accounts and what not that should not be there. ... We assumed the attacker was using some sort of SQL injection to alter the DB records or possibly he can craft a SQL query in a way that will create an admin account to use to simply log in and alter the records and then delete his username...NO rogue admin accounts have ever been found. ... You have an option to go with a managed service or an enterprise software. ...
    (Pen-Test)