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.
Showing posts with label wizard. Show all posts
Showing posts with label wizard. Show all posts
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 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.
Friday, March 9, 2012
job failed after domain IP address changed
I've create a maintenance plan using the SQLserver Wizard.
The jobs work correctly until we change the IP address of the server with the following trace :
The job failed. Unable to determine if the owner (DOMAIN\Login) of job Transaction Log Backup Job for DB Maintenance Plan 'BASE' has server access (reason: Could not obtain information about Windows NT group/user 'DOMAIN\login'. [SQLSTATE 42000] (Error 8198)).
Can somebpody explain me what occured ?Howdy
I have seen this a lot on SQL 7 and it seems the NT authentication/ SQL interface neve rreally worked properly.
Easiest way ( and usually the best way of going anyway ) is get sa to own all jobs, then unless its a very secure server, all will run fine and if you change the IP adderess of the server, as sa is local, it wont make any difference.
Cheers
SG.
The jobs work correctly until we change the IP address of the server with the following trace :
The job failed. Unable to determine if the owner (DOMAIN\Login) of job Transaction Log Backup Job for DB Maintenance Plan 'BASE' has server access (reason: Could not obtain information about Windows NT group/user 'DOMAIN\login'. [SQLSTATE 42000] (Error 8198)).
Can somebpody explain me what occured ?Howdy
I have seen this a lot on SQL 7 and it seems the NT authentication/ SQL interface neve rreally worked properly.
Easiest way ( and usually the best way of going anyway ) is get sa to own all jobs, then unless its a very secure server, all will run fine and if you change the IP adderess of the server, as sa is local, it wont make any difference.
Cheers
SG.
Subscribe to:
Posts (Atom)