When selecting to start a job manually, the job steps
appear out of order (step 3 is above steps 1 and 2 and
the like).
Any ideas what is causing this, and how to correct it?And, as I said, I don't see this and can't reproduce it. So something must
be different about *your* job, which is why I asked to see the SQL script.
We're not going to be able to guess at what's wrong unless we actually have
a script that we can use to reproduce your scenario!
"Arbiter Becker" <absql@.hotmail.com> wrote in message
news:0b7e01c356a5$12262c30$a601280a@.phx.gbl...
> Note;
> The job runs fine, if running off a schedule, and is
> displayed correctly if looking at the individual job
> steps. It is only when doing the manual start option for
> the job does it display incorrectly.
>
> >--Original Message--
> >When selecting to start a job manually, the job steps
> >appear out of order (step 3 is above steps 1 and 2 and
> >the like).
> >
> >Any ideas what is causing this, and how to correct it?
> >.
> >|||Hi Arbiter,
When you say step 3, 2, 1..., do you refer to the ID shown on Steps tab, or
the number prefix you may have added in the name of each job step?
If you click on "Move step" (up and down arrows), the ID always stays in
ascending order but the actual job steps move.
Richard
"Arbiter Becker" <absql@.hotmail.com> wrote in message
news:0da801c3569f$f4d71130$a101280a@.phx.gbl...
> When selecting to start a job manually, the job steps
> appear out of order (step 3 is above steps 1 and 2 and
> the like).
> Any ideas what is causing this, and how to correct it?
Showing posts with label selecting. Show all posts
Showing posts with label selecting. Show all posts
Wednesday, March 28, 2012
Monday, March 12, 2012
job fails for sql 2005 run SSIS package
Hi, I created an SSIS package and deployed it by using the wizard that is
invoked when selecting the SSISDeploymentmanifest file. The deployment
worked as I can run the package from sql server management studio under MSDB
by right clicking and selecting excecute package, in the object explorer.
When I create a job under SQL Server agent the job is created succesfully.
It has 1 step to execute the package. When I try to run the job it fails and
the only message I get is
**************************************************
Message
The job failed. The Job was invoked by User domain\username. The last step
to run was step 1 (run package called package). I also checked the view
history and it has the same error message. I used windows authentication
when creating the step. Also when creating the step in the new job I
selected type = SQL Server Integration Package, Run as SQL Agent Service
Account, I then specified the server and selected windows authentication and
it found the package. I am running everything on one machine as I just have
the SQL2005 that comes with vs 2005.
thanks.
Paul G
Software engineer.
I got it to work,it was a permissions issue that I fixed with the SQL server
configuration manager. Also had another problem where it would write out a
message box (it worked!) as part of a vb script. I had to disable this and
then rebuild /redeploy the package.
Paul G
Software engineer.
"Paul" wrote:
> Hi, I created an SSIS package and deployed it by using the wizard that is
> invoked when selecting the SSISDeploymentmanifest file. The deployment
> worked as I can run the package from sql server management studio under MSDB
> by right clicking and selecting excecute package, in the object explorer.
> When I create a job under SQL Server agent the job is created succesfully.
> It has 1 step to execute the package. When I try to run the job it fails and
> the only message I get is
> **************************************************
> Message
> The job failed. The Job was invoked by User domain\username. The last step
> to run was step 1 (run package called package). I also checked the view
> history and it has the same error message. I used windows authentication
> when creating the step. Also when creating the step in the new job I
> selected type = SQL Server Integration Package, Run as SQL Agent Service
> Account, I then specified the server and selected windows authentication and
> it found the package. I am running everything on one machine as I just have
> the SQL2005 that comes with vs 2005.
> thanks.
> Paul G
> Software engineer.
invoked when selecting the SSISDeploymentmanifest file. The deployment
worked as I can run the package from sql server management studio under MSDB
by right clicking and selecting excecute package, in the object explorer.
When I create a job under SQL Server agent the job is created succesfully.
It has 1 step to execute the package. When I try to run the job it fails and
the only message I get is
**************************************************
Message
The job failed. The Job was invoked by User domain\username. The last step
to run was step 1 (run package called package). I also checked the view
history and it has the same error message. I used windows authentication
when creating the step. Also when creating the step in the new job I
selected type = SQL Server Integration Package, Run as SQL Agent Service
Account, I then specified the server and selected windows authentication and
it found the package. I am running everything on one machine as I just have
the SQL2005 that comes with vs 2005.
thanks.
Paul G
Software engineer.
I got it to work,it was a permissions issue that I fixed with the SQL server
configuration manager. Also had another problem where it would write out a
message box (it worked!) as part of a vb script. I had to disable this and
then rebuild /redeploy the package.
Paul G
Software engineer.
"Paul" wrote:
> Hi, I created an SSIS package and deployed it by using the wizard that is
> invoked when selecting the SSISDeploymentmanifest file. The deployment
> worked as I can run the package from sql server management studio under MSDB
> by right clicking and selecting excecute package, in the object explorer.
> When I create a job under SQL Server agent the job is created succesfully.
> It has 1 step to execute the package. When I try to run the job it fails and
> the only message I get is
> **************************************************
> Message
> The job failed. The Job was invoked by User domain\username. The last step
> to run was step 1 (run package called package). I also checked the view
> history and it has the same error message. I used windows authentication
> when creating the step. Also when creating the step in the new job I
> selected type = SQL Server Integration Package, Run as SQL Agent Service
> Account, I then specified the server and selected windows authentication and
> it found the package. I am running everything on one machine as I just have
> the SQL2005 that comes with vs 2005.
> thanks.
> Paul G
> Software engineer.
job fails for sql 2005 run SSIS package
Hi, I created an SSIS package and deployed it by using the wizard that is
invoked when selecting the SSISDeploymentmanifest file. The deployment
worked as I can run the package from sql server management studio under MSDB
by right clicking and selecting excecute package, in the object explorer.
When I create a job under SQL Server agent the job is created succesfully.
It has 1 step to execute the package. When I try to run the job it fails an
d
the only message I get is
****************************************
**********
Message
The job failed. The Job was invoked by User domain\username. The last step
to run was step 1 (run package called package). I also checked the view
history and it has the same error message. I used windows authentication
when creating the step. Also when creating the step in the new job I
selected type = SQL Server Integration Package, Run as SQL Agent Service
Account, I then specified the server and selected windows authentication and
it found the package. I am running everything on one machine as I just have
the SQL2005 that comes with vs 2005.
thanks.
Paul G
Software engineer.I got it to work,it was a permissions issue that I fixed with the SQL server
configuration manager. Also had another problem where it would write out a
message box (it worked!) as part of a vb script. I had to disable this and
then rebuild /redeploy the package.
Paul G
Software engineer.
"Paul" wrote:
> Hi, I created an SSIS package and deployed it by using the wizard that is
> invoked when selecting the SSISDeploymentmanifest file. The deployment
> worked as I can run the package from sql server management studio under MS
DB
> by right clicking and selecting excecute package, in the object explorer.
> When I create a job under SQL Server agent the job is created succesfully.
> It has 1 step to execute the package. When I try to run the job it fails
and
> the only message I get is
> ****************************************
**********
> Message
> The job failed. The Job was invoked by User domain\username. The last st
ep
> to run was step 1 (run package called package). I also checked the view
> history and it has the same error message. I used windows authentication
> when creating the step. Also when creating the step in the new job I
> selected type = SQL Server Integration Package, Run as SQL Agent Service
> Account, I then specified the server and selected windows authentication a
nd
> it found the package. I am running everything on one machine as I just ha
ve
> the SQL2005 that comes with vs 2005.
> thanks.
> Paul G
> Software engineer.
invoked when selecting the SSISDeploymentmanifest file. The deployment
worked as I can run the package from sql server management studio under MSDB
by right clicking and selecting excecute package, in the object explorer.
When I create a job under SQL Server agent the job is created succesfully.
It has 1 step to execute the package. When I try to run the job it fails an
d
the only message I get is
****************************************
**********
Message
The job failed. The Job was invoked by User domain\username. The last step
to run was step 1 (run package called package). I also checked the view
history and it has the same error message. I used windows authentication
when creating the step. Also when creating the step in the new job I
selected type = SQL Server Integration Package, Run as SQL Agent Service
Account, I then specified the server and selected windows authentication and
it found the package. I am running everything on one machine as I just have
the SQL2005 that comes with vs 2005.
thanks.
Paul G
Software engineer.I got it to work,it was a permissions issue that I fixed with the SQL server
configuration manager. Also had another problem where it would write out a
message box (it worked!) as part of a vb script. I had to disable this and
then rebuild /redeploy the package.
Paul G
Software engineer.
"Paul" wrote:
> Hi, I created an SSIS package and deployed it by using the wizard that is
> invoked when selecting the SSISDeploymentmanifest file. The deployment
> worked as I can run the package from sql server management studio under MS
DB
> by right clicking and selecting excecute package, in the object explorer.
> When I create a job under SQL Server agent the job is created succesfully.
> It has 1 step to execute the package. When I try to run the job it fails
and
> the only message I get is
> ****************************************
**********
> Message
> The job failed. The Job was invoked by User domain\username. The last st
ep
> to run was step 1 (run package called package). I also checked the view
> history and it has the same error message. I used windows authentication
> when creating the step. Also when creating the step in the new job I
> selected type = SQL Server Integration Package, Run as SQL Agent Service
> Account, I then specified the server and selected windows authentication a
nd
> it found the package. I am running everything on one machine as I just ha
ve
> the SQL2005 that comes with vs 2005.
> thanks.
> Paul G
> Software engineer.
job fails for sql 2005 run SSIS package
Hi, I created an SSIS package and deployed it by using the wizard that is
invoked when selecting the SSISDeploymentmanifest file. The deployment
worked as I can run the package from sql server management studio under MSDB
by right clicking and selecting excecute package, in the object explorer.
When I create a job under SQL Server agent the job is created succesfully.
It has 1 step to execute the package. When I try to run the job it fails and
the only message I get is
**************************************************
Message
The job failed. The Job was invoked by User domain\username. The last step
to run was step 1 (run package called package). I also checked the view
history and it has the same error message. I used windows authentication
when creating the step. Also when creating the step in the new job I
selected type = SQL Server Integration Package, Run as SQL Agent Service
Account, I then specified the server and selected windows authentication and
it found the package. I am running everything on one machine as I just have
the SQL2005 that comes with vs 2005.
thanks.
Paul G
Software engineer.I got it to work,it was a permissions issue that I fixed with the SQL server
configuration manager. Also had another problem where it would write out a
message box (it worked!) as part of a vb script. I had to disable this and
then rebuild /redeploy the package.
--
Paul G
Software engineer.
"Paul" wrote:
> Hi, I created an SSIS package and deployed it by using the wizard that is
> invoked when selecting the SSISDeploymentmanifest file. The deployment
> worked as I can run the package from sql server management studio under MSDB
> by right clicking and selecting excecute package, in the object explorer.
> When I create a job under SQL Server agent the job is created succesfully.
> It has 1 step to execute the package. When I try to run the job it fails and
> the only message I get is
> **************************************************
> Message
> The job failed. The Job was invoked by User domain\username. The last step
> to run was step 1 (run package called package). I also checked the view
> history and it has the same error message. I used windows authentication
> when creating the step. Also when creating the step in the new job I
> selected type = SQL Server Integration Package, Run as SQL Agent Service
> Account, I then specified the server and selected windows authentication and
> it found the package. I am running everything on one machine as I just have
> the SQL2005 that comes with vs 2005.
> thanks.
> Paul G
> Software engineer.
invoked when selecting the SSISDeploymentmanifest file. The deployment
worked as I can run the package from sql server management studio under MSDB
by right clicking and selecting excecute package, in the object explorer.
When I create a job under SQL Server agent the job is created succesfully.
It has 1 step to execute the package. When I try to run the job it fails and
the only message I get is
**************************************************
Message
The job failed. The Job was invoked by User domain\username. The last step
to run was step 1 (run package called package). I also checked the view
history and it has the same error message. I used windows authentication
when creating the step. Also when creating the step in the new job I
selected type = SQL Server Integration Package, Run as SQL Agent Service
Account, I then specified the server and selected windows authentication and
it found the package. I am running everything on one machine as I just have
the SQL2005 that comes with vs 2005.
thanks.
Paul G
Software engineer.I got it to work,it was a permissions issue that I fixed with the SQL server
configuration manager. Also had another problem where it would write out a
message box (it worked!) as part of a vb script. I had to disable this and
then rebuild /redeploy the package.
--
Paul G
Software engineer.
"Paul" wrote:
> Hi, I created an SSIS package and deployed it by using the wizard that is
> invoked when selecting the SSISDeploymentmanifest file. The deployment
> worked as I can run the package from sql server management studio under MSDB
> by right clicking and selecting excecute package, in the object explorer.
> When I create a job under SQL Server agent the job is created succesfully.
> It has 1 step to execute the package. When I try to run the job it fails and
> the only message I get is
> **************************************************
> Message
> The job failed. The Job was invoked by User domain\username. The last step
> to run was step 1 (run package called package). I also checked the view
> history and it has the same error message. I used windows authentication
> when creating the step. Also when creating the step in the new job I
> selected type = SQL Server Integration Package, Run as SQL Agent Service
> Account, I then specified the server and selected windows authentication and
> it found the package. I am running everything on one machine as I just have
> the SQL2005 that comes with vs 2005.
> thanks.
> Paul G
> Software engineer.
Subscribe to:
Posts (Atom)