The main issue here was that the drops and non-payers files did not generate and thus the emails associated with these were not sent.

We were able to regenerate all of these, but there are a number of obstacles to overcome.

1) the DMS and CPFBACS databases need to be as they would have been on the date/time of the failed run. Since the live databases are constantly changing we had to restore the closest backup we could get onto a temporary database on VM2016DBA03. Note that many files and database records are generated as part of the disbursement process, there was a need to confirm which of these had completed and which had not. Many of them are accessed later in the process and their absence would have caused another failure.
2) the required packages will not run on the current version of Visual Studio, we had to use Visual Studio 2015 to get them to run. This is true for the two specific packages needed to regenerate the missing files, but it is likely also true for other packages of a similar age, so something to bear in mind!
3) The package is pointed at the required database by editing the file SSIS_Management_Framework.dtsConfig. The file should be in root of the folder C:\SSIS. If it doesn't exist it can be copied there. If the folder doesn't exist it needs to ne created. The file can be opened using notepad. By way of an example this is the content of the file that was needed for this incident:
    <DTSConfiguration>
    <DTSConfigurationHeading>
    <DTSConfigurationFileInfo GeneratedBy="CCCSNT\IT" GeneratedFromPackageName="Package" GeneratedFromPackageID="{435ED159-1E87-40B2-B296-C40A3A39AA5C}" GeneratedDate="01/01/2019 00:00:00"/>
    </DTSConfigurationHeading>
    <Configuration ConfiguredType="Property" Path="\Package.Connections[SSIS_Config].Properties[ConnectionString]" ValueType="String">
    <ConfiguredValue>Data Source=vm2016dba03;Initial Catalog=SSIS_Config;Provider=SQLOLEDB.1;Integrated Security=SSPI;Auto Translate=False;Application Name=SSIS-Package-{D512ECCD-86B5-48A8-A751-AF01A5D8396D}    VM2016DBA03.SSIS_Config;</ConfiguredValue>
    </Configuration>
    </DTSConfiguration>
4) The database SSIS_Config holds a lot of values that the package needs to run, including connection strings and values assigned to package variables.It is likely that several of these entries will need to be edited depending on circumstance. Again for example, these are the edits that were required for this particular incident:
    UPDATE SSISConfigurations
      SET ConfiguredValue = '20251027'
      WHERE ConfigurationFilter = 'DailyDisbursement'
      AND PackagePath = '\Package.Variables[User::DisbursementDate].Properties[Value]'
 
        UPDATE SSISConfigurations
      SET ConfiguredValue = 2760
      WHERE ConfigurationFilter = 'DailyDisbursement'
      AND PackagePath = '\Package.Variables[User::DisbursementID].Properties[Value]'
 
        UPDATE SSISConfigurations
      SET ConfiguredValue = 'AD17187'
      WHERE ConfigurationFilter = 'DailyDisbursement'
      AND PackagePath = '\Package.Variables[User::DisbursementBatchID].Properties[Value]'
Others may be required, the database should be manually checked to identify these.
5) With the above steps complete it should now be possible to run the packages locally from the Visual Studio IDE. note that the folder location to which the files will be dropped is and in the SSIS_config database. this should be edited to point to a folder on your local machine.
6) When the package runs successfully locally the required files should appear in the specified local folder (step 4) These can be checked and if correct copied to the expected location in Live.