Re: Cannot Schedule a SSIS Job

Maybe it is just the SSMS? It uses the DTExecUI controls, which can be found
at C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE,
file Microsoft.DataTransformationServices.DTSExecUI.Controls.dll. Check
whether it is there. Try also to add a job with SSIS step through script. I
created one for you; it loads package from the file system, so please be
sure to change the plcaholder "YOURPATH\YOURPACKAGE.dtsx" in the script with
your actual package.

USE [msdb]
GO
/****** Object: Job [TestSSISJob] Script Date: 03/24/2006 21:59:18 ******/
BEGIN TRANSACTION
DECLARE @ReturnCode INT
SELECT @ReturnCode = 0
/****** Object: JobCategory [[Uncategorized (Local)]]] Script Date:
03/24/2006 21:59:18 ******/
IF NOT EXISTS (SELECT name FROM msdb.dbo.syscategories WHERE
name=N'[Uncategorized (Local)]' AND category_class=1)
BEGIN
EXEC @ReturnCode = msdb.dbo.sp_add_category @class=N'JOB', @type=N'LOCAL',
@name=N'[Uncategorized (Local)]'
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
END
DECLARE @jobId BINARY(16)
EXEC @ReturnCode = msdb.dbo.sp_add_job @job_name=N'TestSSISJob',
@enabled=1,
@notify_level_eventlog=0,
@notify_level_email=0,
@notify_level_netsend=0,
@notify_level_page=0,
@delete_level=0,
@description=N'No description available.',
@category_name=N'[Uncategorized (Local)]',
@owner_login_name=N'sa', @job_id = @jobId OUTPUT
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
/****** Object: Step [TestSSISStep] Script Date: 03/24/2006 21:59:19 ******/
EXEC @ReturnCode = msdb.dbo.sp_add_jobstep @job_id=@jobId,
@step_name=N'TestSSISStep',
@step_id=1,
@cmdexec_success_code=0,
@on_success_action=1,
@on_success_step_id=0,
@on_fail_action=2,
@on_fail_step_id=0,
@retry_attempts=0,
@retry_interval=0,
@os_run_priority=0, @subsystem=N'SSIS',
@command=N'/FILE "YOURPATH\YOURPACKAGE.dtsx" /MAXCONCURRENT " -1 "
/CHECKPOINTING OFF',
@database_name=N'master',
@flags=0
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
EXEC @ReturnCode = msdb.dbo.sp_update_job @job_id = @jobId, @start_step_id =
1
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
EXEC @ReturnCode = msdb.dbo.sp_add_jobserver @job_id = @jobId, @server_name
= N'(local)'
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
COMMIT TRANSACTION
GOTO EndSave
QuitWithRollback:
IF (@@TRANCOUNT > 0) ROLLBACK TRANSACTION
EndSave:


--
Dejan Sarka, SQL Server MVP
Mentor, www.SolidQualityLearning.com
Anything written in this message represents solely the point of view of the
sender.
This message does not imply endorsement from Solid Quality Learning, and it
does not represent the point of view of Solid Quality Learning or any other
person, company or institution mentioned in this message

"Makor" <Makor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E0A9533E-FAD3-400D-9F27-E356F989B261@xxxxxxxxxxxxxxxx
Dejan

The drop down options when we create a new step is where the SSIS package
options does not appear for some reason. We definately have both SQL Agent
and SSIS installed - however the option for creating steps that are SSIS
packages does not appear.

"Dejan Sarka" wrote:

I have a install of SQL 2005 and have SSIS installed and configured. I
also
have SQL Agent running. However, When I go to schedule a SSIS job - I
do
not
get the drop down options in the Job Schedular to select a SSIS job.

Are you talking about Category drop-down list in the General page when
you
create a new job? This is not a problem, category is just for your help.
Add
a step using the Steps page and you should be able to select SSIS package
step type.

--
Dejan Sarka, SQL Server MVP
Mentor, www.SolidQualityLearning.com
Anything written in this message represents solely the point of view of
the
sender.
This message does not imply endorsement from Solid Quality Learning, and
it
does not represent the point of view of Solid Quality Learning or any
other
person, company or institution mentioned in this message





.

Relevant Pages

  • Re: more detail on issue
    ... I went to SSIS ... package, on the package properties i selected 'EncryptallwithPassword', gave ... strings not being visible to the SQL Agent user. ...
    (microsoft.public.sqlserver.dts)
  • Re: DTS to SSIS lost functionality
    ... Try this with both a wizard in DTS and a wizard in SSIS: ... Crate a package that exports data from a SQL table and dumps into an Excel ...
    (microsoft.public.sqlserver.dts)
  • Re: Editing an SSIS package created by Import/Export Wizard
    ... SQL 2000 and migrated to a SSIS object in SQL 2005 or did you simply ... migrate it to a legacy DTS package within SQL 2005? ... I created the SSIS package using the BIDS ...
    (microsoft.public.sqlserver)
  • Re: Cannot Schedule a SSIS Job
    ... Could you pherhaps be more specific on how i use your script since I am not ... Should I try and run the package form a SQL Job using ... Try also to add a job with SSIS step through script. ...
    (microsoft.public.sqlserver.setup)
  • Re: more detail on issue
    ... then have SQL and SQL Agent running as an ... When you installed the package to your SQL ... Server, did it prompt you for the password you packaged with? ... strings not being visible to the SQL Agent user. ...
    (microsoft.public.sqlserver.dts)
Loading