help with service account permissions

i decided to see if i could better secure one of my test servers so
here's what i did.
created two local nt accounts (one for the sqlserver service and one for
agent) that are not local admins.
through enterprise manager i changed the agent and server to run using
the appropriate account.
both the server and agent start, but aren't working properly.
i get the following errors in the sqlagent error log
[LOG] The data portion of event 17052 from MSSQLSERVER is invalid
i get the following error every time i try to start a job
error 22022 :sqlserveragent is not currently running so it cannot be
notified of this action.
the agent is running (i even see the account that runs the agent is
connected to msdb).
i see no errors in the sqlserver log, but i do see the following errors
in the nt application log.
You do not have sufficient operating system permission to open the
sqlserveragent status event.
i checked the user rights for both local nt accounts and they have the
following granted to them
act as part of o/s
bypass traverse checking
lock pages in memory
log on as a batch job
log on as a service
replace a process level token
kb 283811 says they also need the "increase quotas" permission, but that
doesn't sound like the cause of the errors.
i haven't checked all the registry permissions those two accounts need,
but that doesn't sound like the cause of the error either.
any ideas?i forgot to mention this is sql2000 sp3, win2k latest updates.
also, i went back and added both nt accounts to local admin group and
everything is working properly again.
chxxx wrote:
> i decided to see if i could better secure one of my test servers so
> here's what i did.
> created two local nt accounts (one for the sqlserver service and one for
> agent) that are not local admins.
> through enterprise manager i changed the agent and server to run using
> the appropriate account.
> both the server and agent start, but aren't working properly.
> i get the following errors in the sqlagent error log
> [LOG] The data portion of event 17052 from MSSQLSERVER is invalid
> i get the following error every time i try to start a job
> error 22022 :sqlserveragent is not currently running so it cannot be
> notified of this action.
> the agent is running (i even see the account that runs the agent is
> connected to msdb).
> i see no errors in the sqlserver log, but i do see the following errors
> in the nt application log.
> You do not have sufficient operating system permission to open the
> sqlserveragent status event.
> i checked the user rights for both local nt accounts and they have the
> following granted to them
> act as part of o/s
> bypass traverse checking
> lock pages in memory
> log on as a batch job
> log on as a service
> replace a process level token
> kb 283811 says they also need the "increase quotas" permission, but that
> doesn't sound like the cause of the errors.
> i haven't checked all the registry permissions those two accounts need,
> but that doesn't sound like the cause of the error either.
> any ideas?

Help with linked servers

Hello,
I have two servers db1 and db2. I have created a linked server in db2 to
point to db1. It works great from the server db2 via query analyzer. I can
do a select * from db1.dbname.dbo.tablename. However I get the message
"Server: Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection."
when I try the run the same query from a XP Pro box which is not hosting one
of the db servers. The dbservers are running w2k3 and it's sql2k. Thanks in
advance.
JakeYou do not have Kerberos delegation configured properly. Check out the
following KB article for the details.
http://support.microsoft.com/default.aspx?scid=kb;en-us;319723
Sincerely,
Anthony Thomas
"Jake" <rondican@.hotmail.com> wrote in message
news:OUSaF$2yEHA.3908@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have two servers db1 and db2. I have created a linked server in db2
to
> point to db1. It works great from the server db2 via query analyzer. I can
> do a select * from db1.dbname.dbo.tablename. However I get the message
> "Server: Msg 18452, Level 14, State 1, Line 1
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection."
> when I try the run the same query from a XP Pro box which is not hosting
one
> of the db servers. The dbservers are running w2k3 and it's sql2k. Thanks
in
> advance.
> Jake
>

Help with Linked Servers

Hi Everyone,

I am developing a reporting database server that will use multiple data sources to construct its query (SQL Server 2005, Oracle 9i, and DB2). I successfully linked all 3 databases to my SQL Server 2005 and I am ready to create the report queries. I would like to know what is the best method to do this. Should I refer to the linked servers by four part naming or use a OPENQUERY query. When using a OPENQUERY, you cannot specify parameters to pass to the linked server which makes me question its performance. Can someone please suggest the best way to do this?

Thank you in advance

-Sam

The 'best' method is most likely the four part naming. It allows you to create more robust queries.

OPENQUERY is best used when the remote server is rarely used and for security (or other) reasons, having a 'linked server' is not appropriate. If the remote server is frequently used, then, by all means, add it as a linked server and use the four part names.

Help with linked servers

Hello,
I have two servers db1 and db2. I have created a linked server in db2 to
point to db1. It works great from the server db2 via query analyzer. I can
do a select * from db1.dbname.dbo.tablename. However I get the message
"Server: Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection."
when I try the run the same query from a XP Pro box which is not hosting one
of the db servers. The dbservers are running w2k3 and it's sql2k. Thanks in
advance.
Jake
You do not have Kerberos delegation configured properly. Check out the
following KB article for the details.
http://support.microsoft.com/default...b;en-us;319723
Sincerely,
Anthony Thomas

"Jake" <rondican@.hotmail.com> wrote in message
news:OUSaF$2yEHA.3908@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have two servers db1 and db2. I have created a linked server in db2
to
> point to db1. It works great from the server db2 via query analyzer. I can
> do a select * from db1.dbname.dbo.tablename. However I get the message
> "Server: Msg 18452, Level 14, State 1, Line 1
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection."
> when I try the run the same query from a XP Pro box which is not hosting
one
> of the db servers. The dbservers are running w2k3 and it's sql2k. Thanks
in
> advance.
> Jake
>

Help with linked servers

Hello,
I have two servers db1 and db2. I have created a linked server in DB2 to
point to db1. It works great from the server DB2 via query analyzer. I can
do a select * from db1.dbname.dbo.tablename. However I get the message
"Server: Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection."
when I try the run the same query from a XP Pro box which is not hosting one
of the db servers. The dbservers are running w2k3 and it's sql2k. Thanks in
advance.
JakeYou do not have Kerberos delegation configured properly. Check out the
following KB article for the details.
http://support.microsoft.com/defaul...kb;en-us;319723
Sincerely,
Anthony Thomas
"Jake" <rondican@.hotmail.com> wrote in message
news:OUSaF$2yEHA.3908@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have two servers db1 and db2. I have created a linked server in db2
to
> point to db1. It works great from the server DB2 via query analyzer. I can
> do a select * from db1.dbname.dbo.tablename. However I get the message
> "Server: Msg 18452, Level 14, State 1, Line 1
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection."
> when I try the run the same query from a XP Pro box which is not hosting
one
> of the db servers. The dbservers are running w2k3 and it's sql2k. Thanks
in
> advance.
> Jake
>