title: SQL Server Agent Job stops SSIS Step with "unexpected error" and without any error informations
body: <p>I am dealing with my problem on some Windows Server 2019 (Core) with one running SQL Server 2019 CU4 instance each.</p>
  
  <p><strong>What we try to do</strong> </p>
  
  <p>We are currently building a data warehouse with distributed databases. The individual layers of the DWH are located on one database server each. The data exchange between the layers/servers takes place via SSIS ETLs, which use Linked Servers to reach the other layers and drag and drop data. Each layer also has its own SSIS service instance and executes the corresponding SSIS packets.
  The SSIS packages are called by SQL Server Agent jobs. We have a job that executes the SSIS packets (#1), which in turn calls another job (#2) as the last step, which after a short wait time executes the calling job (#1). Thus, controlled by schedules, a loop is created and data is continuously transferred with ETLs.</p>
  
  <p>I hope this was not too much unnecessary background</p>
  
  <p><strong>The error</strong></p>
  
  <p>Basically the job is running and there are numerous successful executions. However, we are observing interruptions at job #1 without helpful information regarding the error. This means that the job history log refers to the SSIS log, which again only contains an "unexpected termination". In the SSIS log, we only see behavior that indicates that the ETL packet active at that time stopped after validation. Depending on the log level, nothing is logged at all, not even the execution of single packages of the project. The package where this error occurs is different and not limited to a specific one.</p>
  
  <p><strong>What I have already tried</strong></p>
  
  <ul>
  <li>Re-create the jobs and SSIS Enviroments by hand (scripted before)</li>
  <li>Using the 32Bit Runtime</li>
  <li>Upgrade the SSIS project/package version to
  2019</li>
  <li>Increase the log level to "verbose"</li>
  <li>Patching the SQL Server to CU4</li>
  <li>Save ssis dump files (couldn't find them or they weren't created)</li>
  <li>Search Windows and SQL Server Logfiles</li>
  </ul>
  
  <p>Does anyone have some suggestions or some ideas how to become more error specific informations?</p>
  
  <p>Thank you very much and take care :)</p>
  
  <p><strong>UPDATE</strong> We have an error message (OLE DB 0xC0202009 and 0X80004005)!
  <a href="https://i.stack.imgur.com/xwsqe.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/xwsqe.png" alt="0xC0202009 and 0X80004005 error in SSIS Report"></a>
  In order to exclude the use of environments as a cause, I manually set the parameters in the SSIS job step instead of overwriting them by selecting an environment. </p>
  
  <p>Long story short: Today it turns out that the parameter for an OLE DB Connection String is not passed correctly.</p>
  
  <p>The following is specified as a parameter in the job step:
  <a href="https://i.stack.imgur.com/s6ONT.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/s6ONT.png" alt="parameter specified in ssis job step"></a></p>
  
  <p>However, the following connection string is specified in the context of the error message:
  <a href="https://i.stack.imgur.com/QaQEf.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/QaQEf.png" alt="context of ssis error message"></a>
  Please note that some arguments are added twice to the parameter (red).</p>
  
  <p>What could have caused that?</p>