Execute Package task execution failed while child package execution succeeded

Today execute an Execute package Task to invoke other packages, find the task error, and the child package executes successfully.

The error message thrown by the Execute package task is:

Warning:ssis Warning Code dts_w_maximumerrorcountreached. The execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs is the number of errors reaches the number specified in Maximumerrorcount. Change the Maximumerrorcount or fix the errors.

As you can see from the error message, it is certain that the child package has an error with the Execute Package task. However, no errors can be found from the execution results of the child package. Best of all, since you can't think of it, take a look at the error message recorded in Ssisdb.

STEP1, view the execution record of the package recorded in Ssisdb

Open integration Services catalogs-"ssisdb-" solutionname-"projects-" ProjectName, right-click popup shortcut menu, view reports-"standard reports-"all executions.

To see the real error message is:

Error:the connection "{xxxxxxxxxxxxxxxxxxxxx}" is not found. This error was thrown by connections collection when the specific connection element was not found.

The original is Connections Management collection to the parent Task error. Connections Management Collection detects that an ID for a connection does not exist, and the package does not use this connection when it executes, so the package execution process is successful.

Execute Package task execution failed while child package execution succeeded