If this is the case, which it probably is, you can just reschedule the
package to get it to work. But as Sue indicated, before you do this change
you SQL Server registration properties to log you in with Windows
authentication.

Rand
This posting is provided "as is" with no warranties and confers no rights.

The only problem with that is that they lose the job history
which is what a few posters with similar issues where trying
to avoid. And rescheduling hundreds of packages wouldn't be
that quick of a task - especially with the default time
issue that shows up if he were to run through the Schedule
Package functionality of the package.

-Sue

On Tue, 20 Apr 2004 17:35:25 GMT, rboyd (AT) onlinemicrosoft (DOT) com
(Rand Boyd [MSFT]) wrote:

In message <s8oa80hqmo1s53k70s2j9cdibcpp6rp2cb (AT) 4ax (DOT) com>, Sue Hoegemeier
<Sue_H (AT) nomail (DOT) please> writes
Assuming the jobs where all created by the right-click schedule package
option, then you could write some SQL to generate some update code. Run
in "Results in Text" mode then paste generated code into a new window -
e.g.

SELECT 'EXEC msdb.dbo.sp_update_jobstep @step_name=''' + step_name +
''',
@command=''DTSRUN /S "(local)" /N "' + step_name + '" /E'
FROM dbo.sysjobsteps
WHERE command LIKE 'DTSRUN %'

(Untested!)

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

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org