September 1, 2013 at 8:09 am
This is driving me nuts. I hope someone can assist me with the resolution.
Out of the dozens and dozens of SSIS solutions we have at the office, only one solution does this. When I open the solution, open a single package and try to debug that package, the solution opens up other packages and starts running those instead.
Now this solution is unique in that I have multiple projects. One for SSIS packages, and one for SSRS objects. But the SSRS objects aren't even opening. This is the SSIS project only that has this issue and none of our other SSIS solutions / projects have this problem.
Can someone point me to what setting or problem I might be having that could cause this? It's getting so bad that I have to remember to export the package to a misc. solution in order to fix any issues then import the package back into that solution on top of the old copy.
September 1, 2013 at 9:35 am
Maybe the start action is set to a specific package?
Check Project properties\Debugging\Start Action\StartObjectID
Is it set for <Active Package>?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply