Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Here's my situation:

I have two servers, Server A has the Database Server installed and the SQL Agent (SQL Server 2008 Enterprise Edition, 64-bit). Server B has a vendor specific application that needs SSIS to reside in the same server for some reason. As per MSDN licensing I can't have more than 1 instance of SSIS per license of SQL Server. So we went ahead and installed SSIS only to Server B, and applied the configuration instructions found in as to tell it that the database is in Server A.

I am able to run the package manually using DTEXEC on Server B and it ran without errors. However, I am unable to configure an SQL Agent job on Server A that will execute the package against Server B's SSIS install. I get an error about needing to have SSIS installed in Server A.

The question is, how do I tell the Agent in A to execute the package using SSIS on B?

share|improve this question
up vote 1 down vote accepted

It seems that this is just not possible. After wasting about 10 hours or so of our "Microsoft Premier" support hours, the only answer that keeps coming up is "execute dtexec remotely on the machine that has SSIS".

So I'm going to post this as the answer in hopes that some SQL MVP will show up and prove me wrong.

As far as how to do that, I'll probably take advantage of our existing Control-M agents or make a small .Net app that invokes the command via WMI.

The thing that bothers me the most is that I have found licensing documents from Microsoft that state that you can have SSIS living in a separate server from the Database Engine and that it should just work.

share|improve this answer
I also haven't been able to get my SSIS instance to use a remote msdb instance to store packages. Oh well - take documentation with a grain of salt I guess :( – Sam Aug 10 '10 at 17:03
Well configuring SSIS to use a remote msdb is covered by We did this at work and it worked ok (both launching the package through dtexec and within SSMS). – enriquein Aug 12 '10 at 19:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.