November 27, 2012 at 9:30 am
Hi fellow developers,
I have a SSIS package that is using the execute package task to run a child package this child package is however on a separate SSIS server than the master package. The child package is stored in SQL Server not File system. The problem we are having is that the master package seems to be calling the child package on the master package SSIS server. We originally had a copy of the child package also on the Master Package SSIS server but even after we removed it from the Master Package SSIS it still seems to be running the version on the Master Package SSIS even though it has been deleted. We can see the Child Package name under the “Running Packages” folder when we view Master Package SSIS server inside Management Studio. We haven’t been able to restart the server yet as its in production.
Anyone know of any known issues with calling child packages that our not in the master packages SSIS server?
Thanks
November 27, 2012 at 10:17 am
ok I have an update on this first off when we view the "Running Packages" folder in SSMS this also lists packages that are NOT running on the current SSIS server. I made an assumption that it only showed the packages that were running in the SSIS server which was correct.
I also found the reason why it seemed like my master package was not calling my child package on a seperate SSIS server. My child package grabs its configurations from a SQL server table so does my Master file. The issue was that I needed to add the configuration items in the table that my child package uses to the table that my master package uses.
So the problem has been resolved.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply