I'm stumped. I know this is probably something very
simple but I just don't see it.
(Running SQL 7 sp4 on W2K Server)

For simplicity, I created a job with just a Microsoft OLE
DB Provider for SQL Server (tried using both NT Auth and
SQL Auth). I am able to Execute Package fine even though
it really does nothing. But when I try to Schedule
Package, I get the error - "Microsoft SQL-DMO (ODBC SQL
Server Driver)...Login failed for user (null)...not
trusted...". I checked my SQL Server Agent and the
Service Start up Account is a DOMAIN ADMIN. The SQL
Server Agent Connection is set to Use Windows NT Auth.
Under Computer Management the local user SQLAgentCmdExec
is a Member of the Administrator group. Also added that
user to SQL Logins. The packages owner is the same DOMAIN
ADMIN as above. The server uses the same user to login.
What am I missing?

thanks,
george

In article <063001c33fde$61400120$a001280a (AT) phx (DOT) gbl>, george
<gdellinger (AT) turborater (DOT) com> writes
FYI - The package owner is irrelevant, it is the job owner that is
important. This determines if you execute the CmdExec step under the
security context of the SQLServerAgent service account or the
SQLAgentCmdExec account.

I am unclear where the error is coming from, is it from inside the
package, or is it from DTSRUN when trying to load the package from
either SQL Server or Meta Data storage. The security used by DTSRUN to
connect to SQL Server to read the package data has no bearing on
connections inside the package itself.

If it is the package can you turn on the package log file and post it
here, or just the relevant bits and a bit either side.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

I was unable to right click on the package and
choose "Schedule Package" without getting the error. I
have put the database on a new server since then. I am
also planning on replicating back to the old one.

But I renamed the old SQL 7 server to a new name (went
through the whole reboot, cd setup, reboot, dropserver and
addserver) and it allows me to right click and choose
the "Schedule Package" now. Not sure if during the SQL 7
CD upgrade to update tables and registries corrected the
problem or not. One wierd thing I noticed before the
renaming was the OWNER on the GENERAL tab was BLANK? It
still is blank. Not sure how this could be...But I plan
on wiping this server and rebuilding before replicating.

thanks