Creating a job in SQL 2005

Posted on 2006-12-01
Last Modified: 2012-05-05
I'm creating a job in SQL 2005 and this error is coming out when I click OK.

TITLE: Microsoft SQL Server Management Studio

Create failed for JobStep 'InsertingPoliciesintoPoliciesTemp'.  (Microsoft.SqlServer.Smo)

For help, click:


An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)


The specified '@subsystem' is invalid (valid values are returned by sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)

For help, click:



Question by:amedexitt
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
LVL 13

Accepted Solution

Atlanta_Mike earned 500 total points
ID: 18054585
Did you install Integration Services?

Expert Comment

ID: 18054724
Atlanta Mike is on the right lines (and may be bang on) the job is using a feature that is not installed, I have seen this on SSIS when someone didnt put the option on, the same would be true of other options services which a Job could access.

Find out what the job is attempting to do and check whether that feature is installed,
LVL 13

Expert Comment

ID: 18054825
Yep, thats the usually the issue.

Author Comment

ID: 18055268
No I have not installed it; I will install it and I will try to create the job again.

I let you guys know.

LVL 13

Expert Comment

ID: 18419895
The answer is highly likely that he didn't install SSIS, his comment amedexitt: "No I have not installed it; I will install it and I will try to create the job again." Which was the answer I gave.

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Introduction SQL Server Integration Services can read XML files, that’s known by every BI developer.  (If you didn’t, don’t worry, I’m aiming this article at newcomers as well.) But how far can you go?  When does the XML Source component become …
JSON is being used more and more, besides XML, and you surely wanted to parse the data out into SQL instead of doing it in some Javascript. The below function in SQL Server can do the job for you, returning a quick table with the parsed data.
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.

732 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question