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 STEPS OUT OF ORDER

Hi People, I'm facing a very strange situation !
I recently imported some jobs using a script and I
realized that all the steps are out of order when I click
on start job, for example I HAVE 4 steps and it shows like
this 4 - 2 - 3 - 1 ! WHAT IS THAT '
I also notice that when I create new JOBS all order for
the steps are wrong ! WHATA IS THAT JESUS !
Please HELP ME ! THANK'S !
.I bet you installed the MS03_031 SQL Server Patch. After
I installed this patch I had the same problem. You / we
will need to wait till the next patch. :(
-Stephen
>--Original Message--
>I know this isn't what you looking for but can you
reorder them? have you
>change your sort order in sql?
>
>Yovan Fernandez
>"Roberto Carrasco" <Roberto_carrasco@.msn.com> wrote in
message
>news:058601c377d8$151d5130$a101280a@.phx.gbl...
>> Hi People, I'm facing a very strange situation !
>> I recently imported some jobs using a script and I
>> realized that all the steps are out of order when I
click
>> on start job, for example I HAVE 4 steps and it shows
like
>> this 4 - 2 - 3 - 1 ! WHAT IS THAT '
>> I also notice that when I create new JOBS all order for
>> the steps are wrong ! WHATA IS THAT JESUS !
>> Please HELP ME ! THANK'S !
>> .
>>
>
>.
>|||Hi,
I Installed ! Jesus ! This is terrible ! This kind of
thing that happen, very sad.
We wait !
Thank's !
>--Original Message--
>I bet you installed the MS03_031 SQL Server Patch. After
>I installed this patch I had the same problem. You / we
>will need to wait till the next patch. :(
>-Stephen
>>--Original Message--
>>I know this isn't what you looking for but can you
>reorder them? have you
>>change your sort order in sql?
>>
>>Yovan Fernandez
>>"Roberto Carrasco" <Roberto_carrasco@.msn.com> wrote in
>message
>>news:058601c377d8$151d5130$a101280a@.phx.gbl...
>> Hi People, I'm facing a very strange situation !
>> I recently imported some jobs using a script and I
>> realized that all the steps are out of order when I
>click
>> on start job, for example I HAVE 4 steps and it shows
>like
>> this 4 - 2 - 3 - 1 ! WHAT IS THAT '
>> I also notice that when I create new JOBS all order for
>> the steps are wrong ! WHATA IS THAT JESUS !
>> Please HELP ME ! THANK'S !
>> .
>>
>>
>>.
>.
>|||I am having the same problem. Were you able to fins a solution?
Ashwin Mahaja
--
amahaja
----
amahajan's Profile: http://www.msusenet.com/member.php?userid=39
View this thread: http://www.msusenet.com/t-322648

Job Step of more than 3200 characters

Hi,
An ActiveX script has 42318 characters in a vbs file. We are trying to use this .vbs file as a job step. We get this error message:
--
Edit Job Step - 192.168.1.75\TrialJob
--
The specified file ('mailscripts\send_auto_con.vbs'), is 42318 characters in size, which is larger than the available free space in the current Job Step command (3200 characters).
Do you want to continue opening this file but have its contents truncated.
--
Yes No
--
Can we execute the vbs file as such? Can somebody help us with this issue. Thanks in advance.
regards,
MadhuTry executing the vbs file using CScript and a CmdExec job
step instead.
-Sue
On Tue, 18 Nov 2003 03:16:08 -0800, "Madhu"
<anonymous@.discussions.microsoft.com> wrote:
>Hi,
>An ActiveX script has 42318 characters in a vbs file. We are trying to use this .vbs file as a job step. We get this error message:
>--
>Edit Job Step - 192.168.1.75\TrialJob
>--
>The specified file ('mailscripts\send_auto_con.vbs'), is 42318 characters in size, which is larger than the available free space in the current Job Step command (3200 characters).
>Do you want to continue opening this file but have its contents truncated.
>--
>Yes No
>--
>Can we execute the vbs file as such? Can somebody help us with this issue. Thanks in advance.
>regards,
>Madhu|||Hi Sue,
Thanks for the information, could you please elaborate on how we could
achieve this? May be a code snippet or something that would help us.
Thanks in advance,
Madhu
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:9ebkrvool9ie3lq2gtmksanndfsd31u16f@.4ax.com...
> Try executing the vbs file using CScript and a CmdExec job
> step instead.
> -Sue
> On Tue, 18 Nov 2003 03:16:08 -0800, "Madhu"
> <anonymous@.discussions.microsoft.com> wrote:
> >Hi,
> >
> >An ActiveX script has 42318 characters in a vbs file. We are trying to
use this .vbs file as a job step. We get this error message:
> >
> >--
> >Edit Job Step - 192.168.1.75\TrialJob
> >--
> >The specified file ('mailscripts\send_auto_con.vbs'), is 42318 characters
in size, which is larger than the available free space in the current Job
Step command (3200 characters).
> >Do you want to continue opening this file but have its contents
truncated.
> >--
> >Yes No
> >--
> >
> >Can we execute the vbs file as such? Can somebody help us with this
issue. Thanks in advance.
> >
> >regards,
> >
> >Madhu
>|||In a CmdExec step:
CScript.exe /NOLOGO C:\Scripts\YourVBScript.vbs
-Sue
On Tue, 18 Nov 2003 21:09:11 +0530, "Madhu"
<anonymous@.discussions.microsoft.com> wrote:
>Hi Sue,
>Thanks for the information, could you please elaborate on how we could
>achieve this? May be a code snippet or something that would help us.
>Thanks in advance,
>Madhu
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:9ebkrvool9ie3lq2gtmksanndfsd31u16f@.4ax.com...
>> Try executing the vbs file using CScript and a CmdExec job
>> step instead.
>> -Sue
>> On Tue, 18 Nov 2003 03:16:08 -0800, "Madhu"
>> <anonymous@.discussions.microsoft.com> wrote:
>> >Hi,
>> >
>> >An ActiveX script has 42318 characters in a vbs file. We are trying to
>use this .vbs file as a job step. We get this error message:
>> >
>> >--
>> >Edit Job Step - 192.168.1.75\TrialJob
>> >--
>> >The specified file ('mailscripts\send_auto_con.vbs'), is 42318 characters
>in size, which is larger than the available free space in the current Job
>Step command (3200 characters).
>> >Do you want to continue opening this file but have its contents
>truncated.
>> >--
>> >Yes No
>> >--
>> >
>> >Can we execute the vbs file as such? Can somebody help us with this
>issue. Thanks in advance.
>> >
>> >regards,
>> >
>> >Madhu
>|||Thanks Sue,
It worked fine. Thanks for your help.
Regards,
Madhu
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:1efkrv8mqqpch05hnp4arl0gbl3gu00fnf@.4ax.com...
> In a CmdExec step:
> CScript.exe /NOLOGO C:\Scripts\YourVBScript.vbs
> -Sue
> On Tue, 18 Nov 2003 21:09:11 +0530, "Madhu"
> <anonymous@.discussions.microsoft.com> wrote:
> >Hi Sue,
> >
> >Thanks for the information, could you please elaborate on how we could
> >achieve this? May be a code snippet or something that would help us.
> >
> >Thanks in advance,
> >
> >Madhu
> >
> >"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> >news:9ebkrvool9ie3lq2gtmksanndfsd31u16f@.4ax.com...
> >> Try executing the vbs file using CScript and a CmdExec job
> >> step instead.
> >>
> >> -Sue
> >>
> >> On Tue, 18 Nov 2003 03:16:08 -0800, "Madhu"
> >> <anonymous@.discussions.microsoft.com> wrote:
> >>
> >> >Hi,
> >> >
> >> >An ActiveX script has 42318 characters in a vbs file. We are trying to
> >use this .vbs file as a job step. We get this error message:
> >> >
> >> >--
> >> >Edit Job Step - 192.168.1.75\TrialJob
> >> >--
> >> >The specified file ('mailscripts\send_auto_con.vbs'), is 42318
characters
> >in size, which is larger than the available free space in the current Job
> >Step command (3200 characters).
> >> >Do you want to continue opening this file but have its contents
> >truncated.
> >> >--
> >> >Yes No
> >> >--
> >> >
> >> >Can we execute the vbs file as such? Can somebody help us with this
> >issue. Thanks in advance.
> >> >
> >> >regards,
> >> >
> >> >Madhu
> >>
> >
>

Job step hanging

Hi,
I am trying to run a VB Script step on A SQL Server 2000
Developer SP3a - OS Win 2000 Professional SP2 and the job
is hanging.
If the same script I am executing from a DTS ActiveX task
it runs without any issue.
Here is the script
Dim fso, Folder, Files, File, datecreated
Set fso = CreateObject("Scripting.FileSystemObject")
'Get handles to folder current location.
Set Folder = fso.GetFolder("E:\Backup_History")
Set Files = Folder.Files
If Files.Count > 0 Then
For Each File In Files
'Get files creation date
MsgBox ( file.DateLastModified)
If file.DateLastModified < date -
7 Then
' Delete the files.
File.Delete
End If
Next
End If
Set fso = Nothing
Set Folder = Nothing
Set Files = Nothing
Set File = Nothing
It meant to delete files older then a week.
Any help is very appreciated.
IonelGet rid of the MsgBox ( file.DateLastModified) :-)
There is no visible desktop to display this message box on so it can never
be acknowledged thus the job hangs
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Ionel" <anonymous@.discussions.microsoft.com> wrote in message
news:016401c3c3fd$a96226b0$a301280a@.phx.gbl...
> Hi,
> I am trying to run a VB Script step on A SQL Server 2000
> Developer SP3a - OS Win 2000 Professional SP2 and the job
> is hanging.
> If the same script I am executing from a DTS ActiveX task
> it runs without any issue.
> Here is the script
> Dim fso, Folder, Files, File, datecreated
> Set fso = CreateObject("Scripting.FileSystemObject")
> 'Get handles to folder current location.
> Set Folder = fso.GetFolder("E:\Backup_History")
> Set Files = Folder.Files
> If Files.Count > 0 Then
> For Each File In Files
> 'Get files creation date
> MsgBox ( file.DateLastModified)
> If file.DateLastModified < date -
> 7 Then
> ' Delete the files.
> File.Delete
> End If
> Next
> End If
>
> Set fso = Nothing
> Set Folder = Nothing
> Set Files = Nothing
> Set File = Nothing
> It meant to delete files older then a week.
> Any help is very appreciated.
> Ionel
>|||Thanks,
I had several MsgBox that I used for debugging the script.
This one just escape my attention.
Thanks again.
Ionel
>--Original Message--
>Get rid of the MsgBox ( file.DateLastModified) :-)
>There is no visible desktop to display this message box
on so it can never
>be acknowledged thus the job hangs
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"Ionel" <anonymous@.discussions.microsoft.com> wrote in
message
>news:016401c3c3fd$a96226b0$a301280a@.phx.gbl...
>> Hi,
>> I am trying to run a VB Script step on A SQL Server 2000
>> Developer SP3a - OS Win 2000 Professional SP2 and the
job
>> is hanging.
>> If the same script I am executing from a DTS ActiveX
task
>> it runs without any issue.
>> Here is the script
>> Dim fso, Folder, Files, File, datecreated
>> Set fso = CreateObject("Scripting.FileSystemObject")
>> 'Get handles to folder current location.
>> Set Folder = fso.GetFolder("E:\Backup_History")
>> Set Files = Folder.Files
>> If Files.Count > 0 Then
>> For Each File In Files
>> 'Get files creation date
>> MsgBox ( file.DateLastModified)
>> If file.DateLastModified < date -
>> 7 Then
>> ' Delete the files.
>> File.Delete
>> End If
>> Next
>> End If
>>
>> Set fso = Nothing
>> Set Folder = Nothing
>> Set Files = Nothing
>> Set File = Nothing
>> It meant to delete files older then a week.
>> Any help is very appreciated.
>> Ionel
>>
>
>.
>|||I've done the same thing myself :-)
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Ionel" <anonymous@.discussions.microsoft.com> wrote in message
news:07e701c3c402$e33f6ff0$a001280a@.phx.gbl...
> Thanks,
> I had several MsgBox that I used for debugging the script.
> This one just escape my attention.
> Thanks again.
> Ionel
> >--Original Message--
> >Get rid of the MsgBox ( file.DateLastModified) :-)
> >There is no visible desktop to display this message box
> on so it can never
> >be acknowledged thus the job hangs
> >
> >--
> >HTH
> >
> >Jasper Smith (SQL Server MVP)
> >
> >I support PASS - the definitive, global
> >community for SQL Server professionals -
> >http://www.sqlpass.org
> >
> >
> >"Ionel" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:016401c3c3fd$a96226b0$a301280a@.phx.gbl...
> >> Hi,
> >>
> >> I am trying to run a VB Script step on A SQL Server 2000
> >> Developer SP3a - OS Win 2000 Professional SP2 and the
> job
> >> is hanging.
> >> If the same script I am executing from a DTS ActiveX
> task
> >> it runs without any issue.
> >>
> >> Here is the script
> >>
> >> Dim fso, Folder, Files, File, datecreated
> >>
> >> Set fso = CreateObject("Scripting.FileSystemObject")
> >>
> >> 'Get handles to folder current location.
> >> Set Folder = fso.GetFolder("E:\Backup_History")
> >>
> >> Set Files = Folder.Files
> >> If Files.Count > 0 Then
> >> For Each File In Files
> >> 'Get files creation date
> >> MsgBox ( file.DateLastModified)
> >> If file.DateLastModified < date -
> >> 7 Then
> >> ' Delete the files.
> >> File.Delete
> >> End If
> >> Next
> >> End If
> >>
> >>
> >> Set fso = Nothing
> >> Set Folder = Nothing
> >> Set Files = Nothing
> >> Set File = Nothing
> >>
> >> It meant to delete files older then a week.
> >>
> >> Any help is very appreciated.
> >>
> >> Ionel
> >>
> >>
> >
> >
> >.
> >

job script

Hi all,
I'm doing some scripts in a schedule job. Looks like I have some limitations
on the size of the code inside of the steps.
It's a way to fix this?
Tks
JFBPut the "scripts" into stored procedures, and call the stored procedures
from the job steps?
"JFB" <help@.jfb.com> wrote in message
news:OaGKFciFGHA.3588@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> I'm doing some scripts in a schedule job. Looks like I have some
> limitations on the size of the code inside of the steps.
> It's a way to fix this?
> Tks
> JFB
>|||Why I didn't think about that? :)
Tks
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23WbqzeiFGHA.216@.TK2MSFTNGP15.phx.gbl...
> Put the "scripts" into stored procedures, and call the stored procedures
> from the job steps?
>
> "JFB" <help@.jfb.com> wrote in message
> news:OaGKFciFGHA.3588@.TK2MSFTNGP10.phx.gbl...
>

job schedule information

Hi,
Does anyone has a script to find out what are the scheduled timining for all sql server agent jobs.
I'm trying to get the result with the following query, it doen't seem working..

select sj.name,
case sjs.freq_type
when '1 ' then 'Once'
when '4' then 'Daily'
when '8' then 'Weekly'
when '16' then 'Monthly'
when '32' then 'Monthly relative'
when '64' then 'When SQL Server Agent starts' end as Frequency,
case sjs.freq_interval
when '1' then 'Sunday'
when '2' then 'Monday'
when '4' then 'Tuesday'
when '8' then 'Wednesday'
when '16' then 'Thursday'
when '32' then 'Friday'
when '64' then 'Saturday' end as DAY
from sysjobs sj, sysjobschedules sjs
where sj.job_id = sjs.job_id

Any help would be greately appreciated.
ThanksThat should work fine. Just remember to run that against the msdb database!

Or you could just do...

select sj.name,
case sjs.freq_type
when '1 ' then 'Once'
when '4' then 'Daily'
when '8' then 'Weekly'
when '16' then 'Monthly'
when '32' then 'Monthly relative'
when '64' then 'When SQL Server Agent starts' end as Frequency,
case sjs.freq_interval
when '1' then 'Sunday'
when '2' then 'Monday'
when '4' then 'Tuesday'
when '8' then 'Wednesday'
when '16' then 'Thursday'
when '32' then 'Friday'
when '64' then 'Saturday' end as DAY
from msdb..sysjobs sj, msdb..sysjobschedules sjs
where sj.job_id = sjs.job_id|||It not working the way i wanted. I wanted to get something like..
if the job runs every 10 min between 6 am to 6 pm.. i need to get that info also.
Any suggessions.