Hi
I have a SQL Server 2005 cluster with 2 nodes. All SQL Service account are
running in context of a domain account. Currently I have some issues with
running some legacy dts packages. When I try to run the packages as a
scheduled job, they fail but the run perfectly when I log on as the sql
service that SQL Server agent is running under and start the jobs manually.
I'm currently trying to find out if there are any errors in the
configuration with user rights on the server nodes.
One thing I've noticed it that I'm missing the following local security
groups on the cluster nodes:
SQLServer2005MSSQLUser$ComputerName$MSSQLSERVER
SQLServer2005SQLAgentUser$ComputerName$MSSQLSERVER

I've found some references to the same problem that I'm currently having
with execution of dts packages and one resultion is to add the account that
sqlserver agent is running under into these local security groups. But the
fact that these groups are missing, is that something that is correct on a
cluster setup?

/MRW

You should have been asked three domain groups when you set up the cluster.
These are granted the cluster-wide rights for the SQL service accounts (SQL,
Agent, and Full-Text). Those groups should have the rights, not the actual
accounts.

I would check access rights for the SQL Agent to the executable files. If
the DTS packages are located on a nework share, make sure and use UNC names
and not mapped drive letters. The services may not know about the letters.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"MRWildiac" <MRWildiac (AT) discussions (DOT) microsoft.com> wrote