Re: New Schedule DTSX Job Fails to execute

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Mo,
some time ago I'd been having a hell too, trying to execute a
scheduled pkg.

So at last I managed in it and now, before deploying on MSDB, I
always:
- set to true Save Password checkbox in every DB connection
- choose "Rely On Server Storage" protection level.

I use a sysadmin proxy account to execute the single steps.
Let us know,
M.

On Aug 7, 3:55 pm, Mo <theg...@xxxxxxxxx> wrote:
I have been having a hell of a time with running a dtsx package on my
SQL server 2005. I designed the package on a development machine and
through Visual studio it runs fine. I then imported the package to my
SQL server Integration services. if I right click on the package and
select execute, I can execute the package successfully as long as I
select Connection Manager and select the connections in the package
and manually add the passwords to the connection strings. Apparently
the passwords are not saved. I also tried to Export and Re-import the
package using various protection levels in order to save the
connection passwords without any luck.

When I schedule the package to run under SQL Server Agent, I even go
to the conenctions and manually add the passwords and still the job
fails. Even tried running under different accounts sa, etc without any
luck. Can somebody help me? I am sure I am missing something but I do
not knwo why.

  this is the cryptic message I get:

ate             8/7/2008 9:51:57 AM
Log             Job History (xxx)

Step ID         1
Server          xxxxx-6
Job Name                xxx
Step Name               ss
Duration                00:00:02
Sql Severity            0
Sql Message ID          0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted               0

Message
Executed as user: xxxxx\SYSTEM. The package execution failed.  The
step failed.

.

Relevant Pages

  • Re: Script Controlled Dynamic Task Execution
    ... My package had three connections to three ... and each had a transformation for itself. ... After posting, I just created three packages for each connection, and my ... >> need to execute one transformation on a text file, ...
    (microsoft.public.sqlserver.dts)
  • Re: Check connection to db
    ... The usual way would be to execute a dummy query against the server. ... If the connection is lost ... during package execution then the associated task will fail and you can set ...
    (microsoft.public.sqlserver.dts)
  • Re: Export to Text File Fails from Server Box
    ... If you are on WKSTN1 and you pick up a package from SVR1 and press execute, ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. ... >I should have specified in my question that in re-creating the text> connection, I did point in to a file local to the SQL Server. ... When I click on the>>> Destination tab, there is an execute button. ...
    (microsoft.public.sqlserver.dts)
  • Re: Connection Failure
    ... I can open the package & execute each step in the proper order. ... execute the package I get the Connection Failure on some ...
    (microsoft.public.sqlserver.dts)
  • New Schedule DTSX Job Fails to execute
    ... I have been having a hell of a time with running a dtsx package on my ... SQL server Integration services. ... and manually add the passwords to the connection strings. ...
    (microsoft.public.sqlserver.dts)