JOB With SSIS Step Fails If Package Contains A Script Task

I have a Job Step defined to execute a SSIS Package. This SSIS package contains a Script Task. The Job fails with the message "Package execution failed. The step failed."

I am logging events in the package and when the packages gets to the Script Task the log reports "The script files failed to load". If I disable the Script Task from the package it executes fine.

Curiously, the package runs successfully with the Scritp task enabled using dtexecui and dtexec from the command line.

Only if I include the Package in a job step with the Script Task enabled does it fail.

Any help would be appreciated.I've no real idea about this Steve except to say have you got the script code pre-compiled? If so, try it without (and vica versa).

-Jamie|||

Sorry for not posting this sooner, Jamie...Yes, setting the Script Task "PrecompileScriptIntoBinaryCode" Property to True resolved the issue.

-Steve

|||hey - did you ever get this to work? Im having the same issue - its a SSIS pkg that ran on one box and I moved to another box (64 bit if that makes a diff) - any info is greatly apprecaited - thanks.|||

Juantana,

Yes, set your Script Task "PrecompileScriptIntoBinaryCode" Property=True and then open and close your script. Save, redeploy and it should work. Let me know if you have any questions.

-Steve

|||

Hi,

Inspite of putting the PrecompileScriptintoBinarycode Property = True, it is not working. Do you have any suggestions?

Thanks.

|||After settings Precompile to True, you need to open and close script editor(s) to actually precompile the script in the task. Then re-deploy the pockage to target system.|||Also remove all the break points in the code, having break points prevents from recompilation. I guess this issue would be fixed by SP2|||Just an FYI I had all my scripts set to PrecompileScriptIntoBinaryCode=True however when developing in 32bit and deploying to 64bit seemingly randomly I will get the "script failed to load" error. I just open the script and compile it again and save and that usually does the trick.|||

Also if the problem still persists and you keep getting the same error I am sure you are not taking the dtsx file from bin folder to execute. The file created by designer (Business Intelligence Development Studio) is only useful for debug and development mode. After building the solution one should use dtsx created in bin folder. This solution worked for me.

Thanks

Mohit

|||NOTE: I got this same error message with Precompile option set to True.

Problem was that a variable name script used was not passed in. Go figure|||

I have about 30 dtxs that I would like to recompile its scripts to solve this issue. I would like to avoid to open each package, then open each script in the package and do the save to recomplie.

Is there a way to recompile from the command line?

Thanks!

|||

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

|||

Chris Honcoop wrote:

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

Sounds like it might be a bug. Could you submit it at http://connect.microsoft.com?

-Jamie

|||

I too have similar doubt as that of Paulino. I've 50+ packages with 60+ script tasks. Is there any way, I can compile using a command in command prompt? Any help would be highly appreciated.

My Regards

JOB With SSIS Step Fails If Package Contains A Script Task

I have a Job Step defined to execute a SSIS Package. This SSIS package contains a Script Task. The Job fails with the message "Package execution failed. The step failed."

I am logging events in the package and when the packages gets to the Script Task the log reports "The script files failed to load". If I disable the Script Task from the package it executes fine.

Curiously, the package runs successfully with the Scritp task enabled using dtexecui and dtexec from the command line.

Only if I include the Package in a job step with the Script Task enabled does it fail.

Any help would be appreciated.I've no real idea about this Steve except to say have you got the script code pre-compiled? If so, try it without (and vica versa).

-Jamie|||

Sorry for not posting this sooner, Jamie...Yes, setting the Script Task "PrecompileScriptIntoBinaryCode" Property to True resolved the issue.

-Steve

|||hey - did you ever get this to work? Im having the same issue - its a SSIS pkg that ran on one box and I moved to another box (64 bit if that makes a diff) - any info is greatly apprecaited - thanks.|||

Juantana,

Yes, set your Script Task "PrecompileScriptIntoBinaryCode" Property=True and then open and close your script. Save, redeploy and it should work. Let me know if you have any questions.

-Steve

|||

Hi,

Inspite of putting the PrecompileScriptintoBinarycode Property = True, it is not working. Do you have any suggestions?

Thanks.

|||After settings Precompile to True, you need to open and close script editor(s) to actually precompile the script in the task. Then re-deploy the pockage to target system.|||Also remove all the break points in the code, having break points prevents from recompilation. I guess this issue would be fixed by SP2|||Just an FYI I had all my scripts set to PrecompileScriptIntoBinaryCode=True however when developing in 32bit and deploying to 64bit seemingly randomly I will get the "script failed to load" error. I just open the script and compile it again and save and that usually does the trick.|||

Also if the problem still persists and you keep getting the same error I am sure you are not taking the dtsx file from bin folder to execute. The file created by designer (Business Intelligence Development Studio) is only useful for debug and development mode. After building the solution one should use dtsx created in bin folder. This solution worked for me.

Thanks

Mohit

|||NOTE: I got this same error message with Precompile option set to True.

Problem was that a variable name script used was not passed in. Go figure|||

I have about 30 dtxs that I would like to recompile its scripts to solve this issue. I would like to avoid to open each package, then open each script in the package and do the save to recomplie.

Is there a way to recompile from the command line?

Thanks!

|||

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

|||

Chris Honcoop wrote:

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

Sounds like it might be a bug. Could you submit it at http://connect.microsoft.com?

-Jamie

sql

JOB With SSIS Step Fails If Package Contains A Script Task

I have a Job Step defined to execute a SSIS Package. This SSIS package contains a Script Task. The Job fails with the message "Package execution failed. The step failed."

I am logging events in the package and when the packages gets to the Script Task the log reports "The script files failed to load". If I disable the Script Task from the package it executes fine.

Curiously, the package runs successfully with the Scritp task enabled using dtexecui and dtexec from the command line.

Only if I include the Package in a job step with the Script Task enabled does it fail.

Any help would be appreciated.I've no real idea about this Steve except to say have you got the script code pre-compiled? If so, try it without (and vica versa).

-Jamie|||

Sorry for not posting this sooner, Jamie...Yes, setting the Script Task "PrecompileScriptIntoBinaryCode" Property to True resolved the issue.

-Steve

|||hey - did you ever get this to work? Im having the same issue - its a SSIS pkg that ran on one box and I moved to another box (64 bit if that makes a diff) - any info is greatly apprecaited - thanks.|||

Juantana,

Yes, set your Script Task "PrecompileScriptIntoBinaryCode" Property=True and then open and close your script. Save, redeploy and it should work. Let me know if you have any questions.

-Steve

|||

Hi,

Inspite of putting the PrecompileScriptintoBinarycode Property = True, it is not working. Do you have any suggestions?

Thanks.

|||After settings Precompile to True, you need to open and close script editor(s) to actually precompile the script in the task. Then re-deploy the pockage to target system.|||Also remove all the break points in the code, having break points prevents from recompilation. I guess this issue would be fixed by SP2|||Just an FYI I had all my scripts set to PrecompileScriptIntoBinaryCode=True however when developing in 32bit and deploying to 64bit seemingly randomly I will get the "script failed to load" error. I just open the script and compile it again and save and that usually does the trick.|||

Also if the problem still persists and you keep getting the same error I am sure you are not taking the dtsx file from bin folder to execute. The file created by designer (Business Intelligence Development Studio) is only useful for debug and development mode. After building the solution one should use dtsx created in bin folder. This solution worked for me.

Thanks

Mohit

|||NOTE: I got this same error message with Precompile option set to True.

Problem was that a variable name script used was not passed in. Go figure|||

I have about 30 dtxs that I would like to recompile its scripts to solve this issue. I would like to avoid to open each package, then open each script in the package and do the save to recomplie.

Is there a way to recompile from the command line?

Thanks!

|||

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

|||

Chris Honcoop wrote:

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

Sounds like it might be a bug. Could you submit it at http://connect.microsoft.com?

-Jamie

JOB With SSIS Step Fails If Package Contains A Script Task

I have a Job Step defined to execute a SSIS Package. This SSIS package contains a Script Task. The Job fails with the message "Package execution failed. The step failed."

I am logging events in the package and when the packages gets to the Script Task the log reports "The script files failed to load". If I disable the Script Task from the package it executes fine.

Curiously, the package runs successfully with the Scritp task enabled using dtexecui and dtexec from the command line.

Only if I include the Package in a job step with the Script Task enabled does it fail.

Any help would be appreciated.I've no real idea about this Steve except to say have you got the script code pre-compiled? If so, try it without (and vica versa).

-Jamie|||

Sorry for not posting this sooner, Jamie...Yes, setting the Script Task "PrecompileScriptIntoBinaryCode" Property to True resolved the issue.

-Steve

|||hey - did you ever get this to work? Im having the same issue - its a SSIS pkg that ran on one box and I moved to another box (64 bit if that makes a diff) - any info is greatly apprecaited - thanks.|||

Juantana,

Yes, set your Script Task "PrecompileScriptIntoBinaryCode" Property=True and then open and close your script. Save, redeploy and it should work. Let me know if you have any questions.

-Steve

|||

Hi,

Inspite of putting the PrecompileScriptintoBinarycode Property = True, it is not working. Do you have any suggestions?

Thanks.

|||After settings Precompile to True, you need to open and close script editor(s) to actually precompile the script in the task. Then re-deploy the pockage to target system.|||Also remove all the break points in the code, having break points prevents from recompilation. I guess this issue would be fixed by SP2|||Just an FYI I had all my scripts set to PrecompileScriptIntoBinaryCode=True however when developing in 32bit and deploying to 64bit seemingly randomly I will get the "script failed to load" error. I just open the script and compile it again and save and that usually does the trick.|||

Also if the problem still persists and you keep getting the same error I am sure you are not taking the dtsx file from bin folder to execute. The file created by designer (Business Intelligence Development Studio) is only useful for debug and development mode. After building the solution one should use dtsx created in bin folder. This solution worked for me.

Thanks

Mohit

|||NOTE: I got this same error message with Precompile option set to True.

Problem was that a variable name script used was not passed in. Go figure|||

I have about 30 dtxs that I would like to recompile its scripts to solve this issue. I would like to avoid to open each package, then open each script in the package and do the save to recomplie.

Is there a way to recompile from the command line?

Thanks!

|||

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

|||

Chris Honcoop wrote:

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

Sounds like it might be a bug. Could you submit it at http://connect.microsoft.com?

-Jamie

JOB With SSIS Step Fails If Package Contains A Script Task

I have a Job Step defined to execute a SSIS Package. This SSIS package contains a Script Task. The Job fails with the message "Package execution failed. The step failed."

I am logging events in the package and when the packages gets to the Script Task the log reports "The script files failed to load". If I disable the Script Task from the package it executes fine.

Curiously, the package runs successfully with the Scritp task enabled using dtexecui and dtexec from the command line.

Only if I include the Package in a job step with the Script Task enabled does it fail.

Any help would be appreciated.I've no real idea about this Steve except to say have you got the script code pre-compiled? If so, try it without (and vica versa).

-Jamie|||

Sorry for not posting this sooner, Jamie...Yes, setting the Script Task "PrecompileScriptIntoBinaryCode" Property to True resolved the issue.

-Steve

|||hey - did you ever get this to work? Im having the same issue - its a SSIS pkg that ran on one box and I moved to another box (64 bit if that makes a diff) - any info is greatly apprecaited - thanks.|||

Juantana,

Yes, set your Script Task "PrecompileScriptIntoBinaryCode" Property=True and then open and close your script. Save, redeploy and it should work. Let me know if you have any questions.

-Steve

|||

Hi,

Inspite of putting the PrecompileScriptintoBinarycode Property = True, it is not working. Do you have any suggestions?

Thanks.

|||After settings Precompile to True, you need to open and close script editor(s) to actually precompile the script in the task. Then re-deploy the pockage to target system.|||Also remove all the break points in the code, having break points prevents from recompilation. I guess this issue would be fixed by SP2|||Just an FYI I had all my scripts set to PrecompileScriptIntoBinaryCode=True however when developing in 32bit and deploying to 64bit seemingly randomly I will get the "script failed to load" error. I just open the script and compile it again and save and that usually does the trick.|||

Also if the problem still persists and you keep getting the same error I am sure you are not taking the dtsx file from bin folder to execute. The file created by designer (Business Intelligence Development Studio) is only useful for debug and development mode. After building the solution one should use dtsx created in bin folder. This solution worked for me.

Thanks

Mohit

|||NOTE: I got this same error message with Precompile option set to True.

Problem was that a variable name script used was not passed in. Go figure|||

I have about 30 dtxs that I would like to recompile its scripts to solve this issue. I would like to avoid to open each package, then open each script in the package and do the save to recomplie.

Is there a way to recompile from the command line?

Thanks!

|||

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

|||

Chris Honcoop wrote:

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

Sounds like it might be a bug. Could you submit it at http://connect.microsoft.com?

-Jamie

JOB With SSIS Step Fails If Package Contains A Script Task

I have a Job Step defined to execute a SSIS Package. This SSIS package contains a Script Task. The Job fails with the message "Package execution failed. The step failed."

I am logging events in the package and when the packages gets to the Script Task the log reports "The script files failed to load". If I disable the Script Task from the package it executes fine.

Curiously, the package runs successfully with the Scritp task enabled using dtexecui and dtexec from the command line.

Only if I include the Package in a job step with the Script Task enabled does it fail.

Any help would be appreciated.I've no real idea about this Steve except to say have you got the script code pre-compiled? If so, try it without (and vica versa).

-Jamie|||

Sorry for not posting this sooner, Jamie...Yes, setting the Script Task "PrecompileScriptIntoBinaryCode" Property to True resolved the issue.

-Steve

|||hey - did you ever get this to work? Im having the same issue - its a SSIS pkg that ran on one box and I moved to another box (64 bit if that makes a diff) - any info is greatly apprecaited - thanks.|||

Juantana,

Yes, set your Script Task "PrecompileScriptIntoBinaryCode" Property=True and then open and close your script. Save, redeploy and it should work. Let me know if you have any questions.

-Steve

|||

Hi,

Inspite of putting the PrecompileScriptintoBinarycode Property = True, it is not working. Do you have any suggestions?

Thanks.

|||After settings Precompile to True, you need to open and close script editor(s) to actually precompile the script in the task. Then re-deploy the pockage to target system.|||Also remove all the break points in the code, having break points prevents from recompilation. I guess this issue would be fixed by SP2|||Just an FYI I had all my scripts set to PrecompileScriptIntoBinaryCode=True however when developing in 32bit and deploying to 64bit seemingly randomly I will get the "script failed to load" error. I just open the script and compile it again and save and that usually does the trick.|||

Also if the problem still persists and you keep getting the same error I am sure you are not taking the dtsx file from bin folder to execute. The file created by designer (Business Intelligence Development Studio) is only useful for debug and development mode. After building the solution one should use dtsx created in bin folder. This solution worked for me.

Thanks

Mohit

|||NOTE: I got this same error message with Precompile option set to True.

Problem was that a variable name script used was not passed in. Go figure|||

I have about 30 dtxs that I would like to recompile its scripts to solve this issue. I would like to avoid to open each package, then open each script in the package and do the save to recomplie.

Is there a way to recompile from the command line?

Thanks!

|||

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

|||

Chris Honcoop wrote:

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

Sounds like it might be a bug. Could you submit it at http://connect.microsoft.com?

-Jamie

JOB With SSIS Step Fails If Package Contains A Script Task

I have a Job Step defined to execute a SSIS Package. This SSIS package contains a Script Task. The Job fails with the message "Package execution failed. The step failed."

I am logging events in the package and when the packages gets to the Script Task the log reports "The script files failed to load". If I disable the Script Task from the package it executes fine.

Curiously, the package runs successfully with the Scritp task enabled using dtexecui and dtexec from the command line.

Only if I include the Package in a job step with the Script Task enabled does it fail.

Any help would be appreciated.I've no real idea about this Steve except to say have you got the script code pre-compiled? If so, try it without (and vica versa).

-Jamie|||

Sorry for not posting this sooner, Jamie...Yes, setting the Script Task "PrecompileScriptIntoBinaryCode" Property to True resolved the issue.

-Steve

|||hey - did you ever get this to work? Im having the same issue - its a SSIS pkg that ran on one box and I moved to another box (64 bit if that makes a diff) - any info is greatly apprecaited - thanks.|||

Juantana,

Yes, set your Script Task "PrecompileScriptIntoBinaryCode" Property=True and then open and close your script. Save, redeploy and it should work. Let me know if you have any questions.

-Steve

|||

Hi,

Inspite of putting the PrecompileScriptintoBinarycode Property = True, it is not working. Do you have any suggestions?

Thanks.

|||After settings Precompile to True, you need to open and close script editor(s) to actually precompile the script in the task. Then re-deploy the pockage to target system.|||Also remove all the break points in the code, having break points prevents from recompilation. I guess this issue would be fixed by SP2|||Just an FYI I had all my scripts set to PrecompileScriptIntoBinaryCode=True however when developing in 32bit and deploying to 64bit seemingly randomly I will get the "script failed to load" error. I just open the script and compile it again and save and that usually does the trick.|||

Also if the problem still persists and you keep getting the same error I am sure you are not taking the dtsx file from bin folder to execute. The file created by designer (Business Intelligence Development Studio) is only useful for debug and development mode. After building the solution one should use dtsx created in bin folder. This solution worked for me.

Thanks

Mohit

|||NOTE: I got this same error message with Precompile option set to True.

Problem was that a variable name script used was not passed in. Go figure|||

I have about 30 dtxs that I would like to recompile its scripts to solve this issue. I would like to avoid to open each package, then open each script in the package and do the save to recomplie.

Is there a way to recompile from the command line?

Thanks!

|||

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

|||

Chris Honcoop wrote:

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

Sounds like it might be a bug. Could you submit it at http://connect.microsoft.com?

-Jamie

sql

JOB With SSIS Step Fails If Package Contains A Script Task

I have a Job Step defined to execute a SSIS Package. This SSIS package contains a Script Task. The Job fails with the message "Package execution failed. The step failed."

I am logging events in the package and when the packages gets to the Script Task the log reports "The script files failed to load". If I disable the Script Task from the package it executes fine.

Curiously, the package runs successfully with the Scritp task enabled using dtexecui and dtexec from the command line.

Only if I include the Package in a job step with the Script Task enabled does it fail.

Any help would be appreciated.I've no real idea about this Steve except to say have you got the script code pre-compiled? If so, try it without (and vica versa).

-Jamie|||

Sorry for not posting this sooner, Jamie...Yes, setting the Script Task "PrecompileScriptIntoBinaryCode" Property to True resolved the issue.

-Steve

|||hey - did you ever get this to work? Im having the same issue - its a SSIS pkg that ran on one box and I moved to another box (64 bit if that makes a diff) - any info is greatly apprecaited - thanks.|||

Juantana,

Yes, set your Script Task "PrecompileScriptIntoBinaryCode" Property=True and then open and close your script. Save, redeploy and it should work. Let me know if you have any questions.

-Steve

|||

Hi,

Inspite of putting the PrecompileScriptintoBinarycode Property = True, it is not working. Do you have any suggestions?

Thanks.

|||After settings Precompile to True, you need to open and close script editor(s) to actually precompile the script in the task. Then re-deploy the pockage to target system.|||Also remove all the break points in the code, having break points prevents from recompilation. I guess this issue would be fixed by SP2|||Just an FYI I had all my scripts set to PrecompileScriptIntoBinaryCode=True however when developing in 32bit and deploying to 64bit seemingly randomly I will get the "script failed to load" error. I just open the script and compile it again and save and that usually does the trick.|||

Also if the problem still persists and you keep getting the same error I am sure you are not taking the dtsx file from bin folder to execute. The file created by designer (Business Intelligence Development Studio) is only useful for debug and development mode. After building the solution one should use dtsx created in bin folder. This solution worked for me.

Thanks

Mohit

|||NOTE: I got this same error message with Precompile option set to True.

Problem was that a variable name script used was not passed in. Go figure|||

I have about 30 dtxs that I would like to recompile its scripts to solve this issue. I would like to avoid to open each package, then open each script in the package and do the save to recomplie.

Is there a way to recompile from the command line?

Thanks!

|||

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

|||

Chris Honcoop wrote:

Previously I said "randomly" but I think I have it figured out when this error occurs:

If I am working on a package, open a different package and copy a script object and paste into the one I am working on it will not work in 64-bit without a recompile (but will work in 32 bit).

Sounds like it might be a bug. Could you submit it at http://connect.microsoft.com?

-Jamie

Job to Execute SSIS package fails

This question has been asked earlier in this forum. But, I still didn't get the correct resolution of my problem.

I am trying to run the DTS package from my filesystem.

Command Line:
/FILE "C:\SSIS\IS\bin\Package1.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF

Executed as user: FILESERVER\SQLServiceQA. The command line parameters are invalid. The step failed.

Can anyone please let me know whats the problem with it.

I am not using any Script Task in the package.

Thanks.Does it run if you execute the same command line as the same user using DTExec? If so then you should probably post to the agent forum. If not then what errors do you get when running it from DTExec?

Thanks,
Matt

Job step cmdexec for applicaiton

Hi,
In a job, as one of the last steps, I want to execute an application.

Can someone please let me know the command (cmdexec) to be put

Right now, I have put "E:\Program Files\Postscript\gsview\gsview32.exe" which is not working

I know for dts packages, the command is
dtsrun /FE:\temp\Let-Stat MIS\Letters_Import.dts /NLetters_Import

Thanks and regards
AbhiUse the xp_cmdshell procedure to execute commands from a system prompt.

blindmansql

job security and permission required

Hi,
What permission is required to create and execute the job successfully?
Switch job ownership to A, but A can't execute job successfully. In the job
, there is DTS and stored procedure. What permission is required?
Thank you.
YulingSee:
269074 INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Job scheduling

Hi,

I have two jobs scheduled on the Agent. Each job has ten steps. The next step is executed only if the previous suceeds.

I want Job 2 to execute only if Job 1 suceeds. How do I schedule that?

I was thinking that I can have the ten steps of Job 2 as steps (11 to 20) of Job 1 with each step executing after the previous one succeeds. If I do that then I can get rid of Job 2.

Let me know what approach you would advise.

Thanksthats what i would do|||I think that is the only option. I am not aware of any other way of controlling the job sequence.|||You don't have to merge two jobs into one. At the end of job1, on step 10 choose "go to next step if succeeds" and then add one more step with command:

exec sp_start_job @.job_name = job2

Job Schedules Not Schedu;ling

I can execute the following file to create jobs/ job
steps/ and related job schedules in SQL Analyzer ...
however the job is never scheduled. I can not identify
anything that is incorrect.
The commands process properly... and I can browse the
resulting msdb table entries in sys_jobs, sys_jobsteps,
and sys_jobschedules... however nothing ever gets
scheduled.
Please provide assistance where appropriate.
USE MSDB
EXEC sp_add_job
@.job_name='MailPointDBEmailFTCTPopulation',
@.enabled=1,
@.notify_level_eventlog=3
EXEC sp_add_jobstep
@.job_name='MailPointDBEmailFTCTPopulation',
@.step_name='EmailFTCTPopulation',
@.subsystem='TSQL',
@.command='EXEC sp_fulltext_table Email, ''update_index'''
EXEC sp_add_jobschedule
@.job_name='MailPointDBEmailFTCTPopulation',
@.name='MailPointDBEmailFTCTPopulation',
@.enabled=1,
@.freq_type=4,
@.freq_interval=1,
@.active_start_time=183000
EXEC sp_add_job
@.job_name='MailPointDBDocumentFTCTPopulation',
@.enabled=1,
@.notify_level_eventlog=3
EXEC sp_add_jobstep
@.job_name='MailPointDBDocumentFTCTPopulation',
@.step_name='DocumentFTCTPopulation',
@.subsystem='TSQL',
@.command='EXEC sp_fulltext_table
Document, ''update_index'''
EXEC sp_add_jobschedule
@.job_name='MailPointDBDocumentFTCTPopulation',
@.name='MailPointDBDocumentFTCTPopulation',
@.enabled=1,
@.freq_type=4,
@.freq_interval=1,
@.active_start_time=183000
GOis agent running on your server ?
jobi
"Philip" <plippard@.nc.rr.com> wrote in message
news:154f01c35247$39bb07a0$a001280a@.phx.gbl...
> I can execute the following file to create jobs/ job
> steps/ and related job schedules in SQL Analyzer ...
> however the job is never scheduled. I can not identify
> anything that is incorrect.
> The commands process properly... and I can browse the
> resulting msdb table entries in sys_jobs, sys_jobsteps,
> and sys_jobschedules... however nothing ever gets
> scheduled.
> Please provide assistance where appropriate.
> USE MSDB
> EXEC sp_add_job
> @.job_name='MailPointDBEmailFTCTPopulation',
> @.enabled=1,
> @.notify_level_eventlog=3
> EXEC sp_add_jobstep
> @.job_name='MailPointDBEmailFTCTPopulation',
> @.step_name='EmailFTCTPopulation',
> @.subsystem='TSQL',
> @.command='EXEC sp_fulltext_table Email, ''update_index'''
> EXEC sp_add_jobschedule
> @.job_name='MailPointDBEmailFTCTPopulation',
> @.name='MailPointDBEmailFTCTPopulation',
> @.enabled=1,
> @.freq_type=4,
> @.freq_interval=1,
> @.active_start_time=183000
> EXEC sp_add_job
> @.job_name='MailPointDBDocumentFTCTPopulation',
> @.enabled=1,
> @.notify_level_eventlog=3
> EXEC sp_add_jobstep
> @.job_name='MailPointDBDocumentFTCTPopulation',
> @.step_name='DocumentFTCTPopulation',
> @.subsystem='TSQL',
> @.command='EXEC sp_fulltext_table
> Document, ''update_index'''
> EXEC sp_add_jobschedule
> @.job_name='MailPointDBDocumentFTCTPopulation',
> @.name='MailPointDBDocumentFTCTPopulation',
> @.enabled=1,
> @.freq_type=4,
> @.freq_interval=1,
> @.active_start_time=183000
> GO
>

Job not working

The output message is :
" DTSRun: Cannot create COM Server to load and execute
DTS Package. Error -2147221164 (80040154): Class not
registered "Was the package created on a different version of SQL Server ?
have you registered the DTS dlls?
If you have then you may want to reregister them.
Redistributing DTS with your program
http://www.sqldts.com/default.aspx?6,105,225,0,1
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
news:084a01c3b8bc$74b5a690$a501280a@.phx.gbl...
> The output message is :
> " DTSRun: Cannot create COM Server to load and execute
> DTS Package. Error -2147221164 (80040154): Class not
> registered "
>

Job from Local DTS Package not running

Hi,

I created a DTS to run a VB.net exe from local packages dts.
If I execute the package, it would do what I want.
I scheduled it to be a job running every minute of every day to test out the schedule.

The job status only stays at "Excuting Job Step 1"...and this hangs there forever.

I've check my SQLServerAgent is started.

Some info:
my sqlserveragent service is run under a username specifically for SQLServer I call "SQLService".
I'm using SQL Server Developer Edition.

Anyone can explain why this is happenning? I'm running into dead alleys here.Why do you want to do that using SQL . Can It not be done through Windows task Scheduler ?|||Cause it needs to be refresh almost a few minutes...or hour..depending..

Windows Task shceduler...I'm using w2k...only details the time of the day, and repeats only on "daily" basis.

So...anything I should check?|||Try going to the advanced schedule properties in windows task scheduler ... you can schedule for every hour nad minute|||Thanks, I can see the detail settings from my home pc...(XP)...
Will try that once I'm at work.

Well...if it works...anything goes...but for knowledge sake, what could have possibly cause the job to just hang? Any ideas?|||I dont think you can call an external exe from a job or xp_cmdshell ... havent found out a way to do so yet.

Job failure notification

Hello,
I created a job that will execute two dts packages at night. Both back up
different databases from the remote server to the local server, so they are
not dependent on each other. Also, if the first one fails, the job steps to
the second one. However, I would like to be notified if either/both of them
fail (and know which one failed).
Can I do this or should I have two separate jobs. If possible, I would
rather get an email saying DTS Package 1 failed versus having to look at the
each log file to determine which one failed.
--
Thanks in advance,
StevenWhy are you using DTS to do backups ?
You can have a job fire that will backup databases. You would have a job
per server you wanted to backup. You can specify the location of the backup
file using UNC. When you say backup do you actually mean data transfer ?
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Steven K" <sckeels@.lucent.com> wrote in message
news:uspA2dlRDHA.2116@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I created a job that will execute two dts packages at night. Both back up
> different databases from the remote server to the local server, so they
are
> not dependent on each other. Also, if the first one fails, the job steps
to
> the second one. However, I would like to be notified if either/both of
them
> fail (and know which one failed).
> Can I do this or should I have two separate jobs. If possible, I would
> rather get an email saying DTS Package 1 failed versus having to look at
the
> each log file to determine which one failed.
> --
> Thanks in advance,
> Steven
>|||Sorry Allan,
What I meant to write was data transfer.
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:OtAVkklRDHA.3132@.tk2msftngp13.phx.gbl...
> Why are you using DTS to do backups ?
> You can have a job fire that will backup databases. You would have a job
> per server you wanted to backup. You can specify the location of the
backup
> file using UNC. When you say backup do you actually mean data transfer ?
> --
>
> Allan Mitchell (Microsoft SQL Server MVP)
> MCSE,MCDBA
> www.SQLDTS.com
> I support PASS - the definitive, global community
> for SQL Server professionals - http://www.sqlpass.org
> "Steven K" <sckeels@.lucent.com> wrote in message
> news:uspA2dlRDHA.2116@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > I created a job that will execute two dts packages at night. Both back
up
> > different databases from the remote server to the local server, so they
> are
> > not dependent on each other. Also, if the first one fails, the job
steps
> to
> > the second one. However, I would like to be notified if either/both of
> them
> > fail (and know which one failed).
> >
> > Can I do this or should I have two separate jobs. If possible, I would
> > rather get an email saying DTS Package 1 failed versus having to look at
> the
> > each log file to determine which one failed.
> >
> > --
> > Thanks in advance,
> >
> > Steven
> >
> >
>

Job Failes due to Error = -2147467259 (80004005)

Hello,

I am importing an excel spreadsheet into SQL Server 2000. The dts package runs perfectly when you execute it under the Local Package pane.

My problem is when i schedule a job to execute the DTS package giving me the same error. I can only successfully execute the package under local Packages. Under Jobs i receive this error:

Executed as user: H-OB\Administrator. ...rt: Copy Data from 'Xagent - Report$' to [CIMPRO1].[dbo].[Xagent_Star_Coater_Points] Step DTSRun OnError: Copy Data from 'Xagent - Report$' to [CIMPRO1].[dbo].[Xagent_Star_Coater_Points] Step, Error = -2147467259 (80004005) Error string: 'R:\shared\star coater\Monthly Points Rpt\Current_Month_Points.xls' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. Error source: Microsoft JET Database Engine Help file: Help context: 5003044 Error Detail Records: Error: -2147467259 (80004005); Provider Error: -534774783 (E01FFC01) Error string: 'R:\shared\star coater\Monthly Points Rpt\Current_Month_Points.xls' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. Error source: Microsoft JET Database Engine ... Process Exit Code 1. The step failed.

Any help on this error would be more than appreciated.The dts package runs perfectly when you execute it under the Local Package pane.
With this I assume you mean that it works when you execute it from your workstation which is not the SQL Server Machine.

At that moment the package is execute on your own computer (not at the server), under your own credentials.

When the job executes it's running under SQL Server credentials at the server and it seems it has never heard of an R-drive at that end or has no access to the mentioned folders or files. Make sure the account under which the SQL Server service is running can access that file.|||Thanks for the advice. I looked at the accounts that is used for the mssqlserver service and that was fine.

It turns ou that for some reason the server is not pickin gup the mapped drice. I had to type the full path in so that it could recognize the file that i am retreiving form the other server.

Thanks again.

JOB failed and QA

Hi,
I had created a sp run as a job, daily. if I execute this sp from QA, it's
work, clean.
but if I run the job, it failed with message (job details):
...ta would be truncated. [SQLSTATE 22001] (Error 8152) String or binary
data would be truncated. [SQLSTATE 22001] (Error 8152) String or binary
data would be truncated. [SQLSTATE 22001] (Error 8152) String or binary
data would be truncated. [SQLSTATE 22001] (Error 8152) String or binary
data would be truncated. [SQLSTATE 22001] (Error 8152) String or binary
data would be truncated. [SQLSTATE 22001] (Error 8152) String or binary
data would be truncated. [SQLSTATE 22001] (Error 8152) String or binary
data would be truncated. [SQLSTATE 22001] (Error 8152) String or binary
data would be truncated. [SQLSTATE 22001] (Error 8152) [SQLSTATE 01000]
(Error 0) The statement has been terminated. [SQLSTATE 01000] (Error 3621)
[SQLSTATE 01000] (Error 0) [SQLSTATE 01000] (Error 0) The statement has
been terminated. [SQLSTATE 01000] (Error 3621) [SQLSTATE 01000] (Error 0)
[SQLSTATE 01000] (Error 0) [SQLSTATE 0... The step failed.
the sp create a temporary table, fill some fields with sum() from other
table, then calculate the stock field from these fields value. at the end of
sp, the temporary table will update a table.
did I missed something?
I use SQL 7 sp 1 on NT4.
thanks in advance.
TeguhI think it's a data types problem too. so I've copied the exact columns from
the target table. all numeric type is decimal(18,2). There's no error
message when run from QA, it's fully worked.
both from QA and JOB I use the same command:
exec spproc_McUnscanQCMFG
but the job still fail. is there any different conditions for job and QA?
here the script:
Select [Item Code], [Item Name], [Stock PPS], [Stock Calc], [Differences],
[Beg. Stock], [Not Finish1Lot], Claim,
[MPC In], [MPC Out], [Scan MC], [WH Location], UOM, [Type]
Into #CheckInvMfg
From (Select IL_ItemCode as [Item Code], PartBom_Partname as [Item
Name],
IL_QuantityOnLocation as [Stock PPS],
IL_QuantityOnLocation as [Stock Calc],
IL_QuantityOnLocation as [Differences], IL_QuantityOnLocation
as [Beg. Stock],
IL_QuantityOnLocation as [Not Finish1Lot],
IL_QuantityOnLocation as Claim, IL_QuantityOnLocation as [MPC
In], IL_QuantityOnLocation as [MPC Out],
IL_QuantityOnLocation as [Scan MC], IL_WHLocation as [WH
Location],
PartBom_UnitOfMeasure as UOM, PartBOM_Type AS [Type]
From Tb_Ic_ItemLocation, Tb_Mst_PartBom Where Il_ItemCode =PartBom_partCode ) Mfg
-- Get / calculate Claim for Mfg
Update #CheckInvMfg
Set Claim = QtyClaim
From (Select cl_MatCode,
CASE CL_UOMClaim WHEN 'KG' THEN Sum( cl_ClaimQty) *
1000)
ELSE Sum(cl_ClaimQty)
END as QtyClaim
From tb_IC_Claim
Where Month(cl_lastupdate) = @.i_Periode and
Year(cl_lastupdate) = @.i_Tahun
and cl_moveto = @.i_MfgWarehouse and cl_postedstatus ='Posted'
Group by cl_matcode, CL_UOMClaim ) claim
Where cl_MatCode = [Item Code]
......
"jobi" <jobi@.reply2.group> wrote in message
news:bdph9e$jio$1@.reader08.wxs.nl...
> execute the same query in QA and put a "select min(sum_result ) ,
> max(sum_result ) from (yourquery) q " on it.
> Check for allowed values for them.
> Look at BOL for "Data Types"
> jobi|||The behaviour of the sp should be the same in QA than in sqlagent.
Are you sure you are running the same object ? (you don't specify e.g.
dbo.spproc_McUnscanQCMFG)
Check out if there exists more than one spproc_McUnscanQCMFG (with different
owners)
If not, check ms-site for issues with sql7 sp1 (btw sp4 is the current one)
jobi
"Teguh R" <priska@.hotpop.com> wrote in message
news:ORQmXgSQDHA.3144@.tk2msftngp13.phx.gbl...
> I think it's a data types problem too. so I've copied the exact columns
from
> the target table. all numeric type is decimal(18,2). There's no error
> message when run from QA, it's fully worked.
> both from QA and JOB I use the same command:
> exec spproc_McUnscanQCMFG
> but the job still fail. is there any different conditions for job and QA?
>
> here the script:
> Select [Item Code], [Item Name], [Stock PPS], [Stock Calc], [Differences],
> [Beg. Stock], [Not Finish1Lot], Claim,
> [MPC In], [MPC Out], [Scan MC], [WH Location], UOM, [Type]
> Into #CheckInvMfg
> From (Select IL_ItemCode as [Item Code], PartBom_Partname as [Item
> Name],
> IL_QuantityOnLocation as [Stock PPS],
> IL_QuantityOnLocation as [Stock Calc],
> IL_QuantityOnLocation as [Differences],
IL_QuantityOnLocation
> as [Beg. Stock],
> IL_QuantityOnLocation as [Not Finish1Lot],
> IL_QuantityOnLocation as Claim, IL_QuantityOnLocation as
[MPC
> In], IL_QuantityOnLocation as [MPC Out],
> IL_QuantityOnLocation as [Scan MC], IL_WHLocation as [WH
> Location],
> PartBom_UnitOfMeasure as UOM, PartBOM_Type AS [Type]
> From Tb_Ic_ItemLocation, Tb_Mst_PartBom Where Il_ItemCode => PartBom_partCode ) Mfg
> -- Get / calculate Claim for Mfg
> Update #CheckInvMfg
> Set Claim = QtyClaim
> From (Select cl_MatCode,
> CASE CL_UOMClaim WHEN 'KG' THEN Sum( cl_ClaimQty) *
> 1000)
> ELSE Sum(cl_ClaimQty)
> END as QtyClaim
> From tb_IC_Claim
> Where Month(cl_lastupdate) = @.i_Periode and
> Year(cl_lastupdate) = @.i_Tahun
> and cl_moveto = @.i_MfgWarehouse and cl_postedstatus => 'Posted'
> Group by cl_matcode, CL_UOMClaim ) claim
> Where cl_MatCode = [Item Code]
> ......
>
>
> "jobi" <jobi@.reply2.group> wrote in message
> news:bdph9e$jio$1@.reader08.wxs.nl...
> > execute the same query in QA and put a "select min(sum_result ) ,
> > max(sum_result ) from (yourquery) q " on it.
> >
> > Check for allowed values for them.
> > Look at BOL for "Data Types"
> > jobi
>
>|||IMO the "change the data type to exact type of target table" solved your
problem.
The upgrade to sp4 should make you sqlserver more reliable.
jobi
"Teguh R" <priska@.hotpop.com> wrote in message
news:uXfmJDATDHA.2148@.TK2MSFTNGP11.phx.gbl...
> I've installed sp4 and change the data type to exact type of target table,
> it's work now.
> But I still wonder, why previously it's works in QA but failed in JOB
> execution?
> I mean, QA has loose checking, less strong type setting parameters than
JOB
> execution?
>
> "jobi" <jobi@.reply2.group> wrote in message
> news:be39nd$gda$1@.reader08.wxs.nl...
> > The behaviour of the sp should be the same in QA than in sqlagent.
> >
> > Are you sure you are running the same object ? (you don't specify e.g.
> > dbo.spproc_McUnscanQCMFG)
> > Check out if there exists more than one spproc_McUnscanQCMFG (with
> different
> > owners)
> > If not, check ms-site for issues with sql7 sp1 (btw sp4 is the current
> one)
> >
> > jobi
> >
> >
> > "Teguh R" <priska@.hotpop.com> wrote in message
> > news:ORQmXgSQDHA.3144@.tk2msftngp13.phx.gbl...
> > > I think it's a data types problem too. so I've copied the exact
columns
> > from
> > > the target table. all numeric type is decimal(18,2). There's no error
> > > message when run from QA, it's fully worked.
> > >
> > > both from QA and JOB I use the same command:
> > >
> > > exec spproc_McUnscanQCMFG
> > >
> > > but the job still fail. is there any different conditions for job and
> QA?
> > >
> > >
> > >
> > > here the script:
> > >
> > > Select [Item Code], [Item Name], [Stock PPS], [Stock Calc],
> [Differences],
> > > [Beg. Stock], [Not Finish1Lot], Claim,
> > > [MPC In], [MPC Out], [Scan MC], [WH Location], UOM,
> [Type]
> > > Into #CheckInvMfg
> > > From (Select IL_ItemCode as [Item Code], PartBom_Partname as
> [Item
> > > Name],
> > > IL_QuantityOnLocation as [Stock PPS],
> > > IL_QuantityOnLocation as [Stock Calc],
> > > IL_QuantityOnLocation as [Differences],
> > IL_QuantityOnLocation
> > > as [Beg. Stock],
> > > IL_QuantityOnLocation as [Not Finish1Lot],
> > > IL_QuantityOnLocation as Claim, IL_QuantityOnLocation as
> > [MPC
> > > In], IL_QuantityOnLocation as [MPC Out],
> > > IL_QuantityOnLocation as [Scan MC], IL_WHLocation as [WH
> > > Location],
> > > PartBom_UnitOfMeasure as UOM, PartBOM_Type AS [Type]
> > > From Tb_Ic_ItemLocation, Tb_Mst_PartBom Where Il_ItemCode => > > PartBom_partCode ) Mfg
> > >
> > > -- Get / calculate Claim for Mfg
> > > Update #CheckInvMfg
> > > Set Claim = QtyClaim
> > > From (Select cl_MatCode,
> > > CASE CL_UOMClaim WHEN 'KG' THEN Sum( cl_ClaimQty)
*
> > > 1000)
> > > ELSE Sum(cl_ClaimQty)
> > > END as QtyClaim
> > > From tb_IC_Claim
> > > Where Month(cl_lastupdate) = @.i_Periode and
> > > Year(cl_lastupdate) = @.i_Tahun
> > > and cl_moveto = @.i_MfgWarehouse and
cl_postedstatus
> => > > 'Posted'
> > > Group by cl_matcode, CL_UOMClaim ) claim
> > > Where cl_MatCode = [Item Code]
> > > ......
> > >
> > >
> > >
> > >
> > > "jobi" <jobi@.reply2.group> wrote in message
> > > news:bdph9e$jio$1@.reader08.wxs.nl...
> > > > execute the same query in QA and put a "select min(sum_result ) ,
> > > > max(sum_result ) from (yourquery) q " on it.
> > > >
> > > > Check for allowed values for them.
> > > > Look at BOL for "Data Types"
> > > > jobi
> > >
> > >
> > >
> >
> >
>

Job Execution Issue - SQL Server 2005

All,
I have a job set up to automatically execute an SSIS package. The
package itself, when ran, works fine. But when the job runs, it fails.
I looked at the sysjobhistory table in the 'msdb' database to see what
the error was. There were two entries:
1) The job failed. The Job was invoked by User DOMAIN\Administrator.
The last step to run was step 1 (Execute LBL Package).
2) Executed as user: DOMAIN\System. The package execution failed. The
step failed.
Ok, so then I went into services and changed the SQLSERVERAGENT to run
as "Administrator" instead of "System".
So, I ran the job again. Got an error. Here's what the sysjobhistory
table said this time:
1) The job failed. The Job was invoked by User DOMAIN\Administrator.
The last step to run was step 1 (Execute LBL Package).
2) Executed as user: DOMAIN\Administrator. The package execution
failed. The step failed.
WTF'!?
Thanks in advance,
JeremyProbably best asked over in the dts forum.
You need some more detail, turn on logging, but could it have something to
do with the "protection levels" of SSIS packages? Can you run it from the
command line on the same machine where it fails? Was it developed on a
different machine from where it fails? Look into how SSIS encrypts
"sensitive information" (mostly passwords), and how that has to be handled
for deployment. Also look to see who owns the job, there's something about
job owner and cmd steps, or something like that.
I've been having the same fun over the past few days. Got mine working, but
not at all certain I could enumerate all the hurdles passed.
Josh
"jrcapp@.cre8iveweb.com" wrote:
> All,
> I have a job set up to automatically execute an SSIS package. The
> package itself, when ran, works fine. But when the job runs, it fails.
> I looked at the sysjobhistory table in the 'msdb' database to see what
> the error was. There were two entries:
> 1) The job failed. The Job was invoked by User DOMAIN\Administrator.
> The last step to run was step 1 (Execute LBL Package).
> 2) Executed as user: DOMAIN\System. The package execution failed. The
> step failed.
> Ok, so then I went into services and changed the SQLSERVERAGENT to run
> as "Administrator" instead of "System".
> So, I ran the job again. Got an error. Here's what the sysjobhistory
> table said this time:
> 1) The job failed. The Job was invoked by User DOMAIN\Administrator.
> The last step to run was step 1 (Execute LBL Package).
> 2) Executed as user: DOMAIN\Administrator. The package execution
> failed. The step failed.
>
> WTF'!?
> Thanks in advance,
> Jeremy
>|||Thanks for the reply, Josh! I'll play around w/some of your
suggestions and get back to you.
Thanks,
Jeremy

Job Execution Issue - SQL Server 2005

All,
I have a job set up to automatically execute an SSIS package. The
package itself, when ran, works fine. But when the job runs, it fails.
I looked at the sysjobhistory table in the 'msdb' database to see what
the error was. There were two entries:
1) The job failed. The Job was invoked by User DOMAIN\Administrator.
The last step to run was step 1 (Execute LBL Package).
2) Executed as user: DOMAIN\System. The package execution failed. The
step failed.
Ok, so then I went into services and changed the SQLSERVERAGENT to run
as "Administrator" instead of "System".
So, I ran the job again. Got an error. Here's what the sysjobhistory
table said this time:
1) The job failed. The Job was invoked by User DOMAIN\Administrator.
The last step to run was step 1 (Execute LBL Package).
2) Executed as user: DOMAIN\Administrator. The package execution
failed. The step failed.
WTF'!?
Thanks in advance,
JeremyProbably best asked over in the dts forum.
You need some more detail, turn on logging, but could it have something to
do with the "protection levels" of SSIS packages? Can you run it from the
command line on the same machine where it fails? Was it developed on a
different machine from where it fails? Look into how SSIS encrypts
"sensitive information" (mostly passwords), and how that has to be handled
for deployment. Also look to see who owns the job, there's something about
job owner and cmd steps, or something like that.
I've been having the same fun over the past few days. Got mine working, but
not at all certain I could enumerate all the hurdles passed.
Josh
"jrcapp@.cre8iveweb.com" wrote:

> All,
> I have a job set up to automatically execute an SSIS package. The
> package itself, when ran, works fine. But when the job runs, it fails.
> I looked at the sysjobhistory table in the 'msdb' database to see what
> the error was. There were two entries:
> 1) The job failed. The Job was invoked by User DOMAIN\Administrator.
> The last step to run was step 1 (Execute LBL Package).
> 2) Executed as user: DOMAIN\System. The package execution failed. The
> step failed.
> Ok, so then I went into services and changed the SQLSERVERAGENT to run
> as "Administrator" instead of "System".
> So, I ran the job again. Got an error. Here's what the sysjobhistory
> table said this time:
> 1) The job failed. The Job was invoked by User DOMAIN\Administrator.
> The last step to run was step 1 (Execute LBL Package).
> 2) Executed as user: DOMAIN\Administrator. The package execution
> failed. The step failed.
>
> WTF'!?
> Thanks in advance,
> Jeremy
>|||Thanks for the reply, Josh! I'll play around w/some of your
suggestions and get back to you.
Thanks,
Jeremy