Unable to install SSIS package with Notify Operator task on a different machine

• BackT0Work

  Mr or Mrs. 500

  Points: 525

  More actions

  May 4, 2011 at 1:47 am

  #150221

  Earlier I had a simple SSIS Package created on my local machine and used to deploy and install on another machine, where the SQL Agent jobs are scheduled. I have many other packages like this, and they all work fine.

  Last week I had to add a 'Notify Operator task' in one of the package. When I tested from my local it works perfectly fine. And only after adding this task, when I try to deploy and install this package on the other machine, Installation always fails without any proper error message. The old package before modification and all the other packages works fine.

  But I am able to install it casually on my local machine and created jobs on that.

  So, what is it stopping me from installing this package in another machine? Will there be any access issues?

  Add. Details: The Operator to Notify is created on a central server where all the dbs exists. What I normally do is, create and test packag on my machine, deploy it on my machine, then copy the deployment files (Manifest,config,dtsx) on the second machine, install from there and create job on it (second machine).

  Screen shot here

  Can someone think of any possibilities?

  Thanks in Advance.

• Koen Verbeeck

  SSC Guru

  Points: 259105

  More actions

  May 5, 2011 at 6:29 am

  #1320325

  Check out the following thread:

  http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/3c1605e6-8fb3-4e7a-ab6c-3e99017529f4

  😉

  Need an answer? No, you need a question
  My blog at https://sqlkover.com.
  MCSE Business Intelligence - Microsoft Data Platform MVP