Execution package nests itself?

  • 16 February 2024
  • 3 replies

Userlevel 3
Badge +1

Hi all, 

We experience a weird issue where our execution package seems to run itself? This happens for a total of 3 times in the execution. Then, when it succeeds it'll kick off the next package where it will happen again. 

This just started to occur in the past week, before everything worked normally. 


Has anyone else experienced this? 

This is the setup of the package. 


Any help would be appreciated. 


Best answer by Thomas Lind 16 February 2024, 11:44

View original

3 replies

Userlevel 5
Badge +5

Hi @sierd.zuiderveld 

In general, you should not exclude areas, instead exclude individual tables or possibly an perspective.

Instead change the perspective to only run what you want. The whole idea with using perspectives is that you can run only the parts needed for a SSL, which excluding DSA and MDW would negate.

Run the scale DB option on its own and then run this on success of this.

This is because of the merge steps option. If this is set it will start executing the tables while running the powershell script. Running it without Merge steps will make the normal execution slower for the other parts.

Still I do not see those things as what causes the issue.

Look at what starts this package, a job likely, and see if it will do the same if you manually start the execution package.

Userlevel 3
Badge +1

Try it without the “Retry Step” option

Userlevel 6
Badge +5

Hi @sierd.zuiderveld did you get a chance to try the suggested solutions above? were you able to resolve the issue?