I've had long running jobs fail due to network error (specific error below) while writing to a an endpoint via a OLE DB Destination.
I want to implement error handling regarding this network error and subsequently test the error.
I'm wondering if there is an easy way to throw an SSIS package error of a certain type at a predetermined time to test. Should be possible with MS's big push towards "Dev Ops".
There are some hacky ways I can imagine doing it like a script task, but I'm wondering if there is any built-in framework I'm just not aware of.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "[DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.".
There is not much on MSDN regarding throwing specific errors to test your exception handling processes.
User contributions licensed under CC BY-SA 3.0