MDW Data Collector Server Activity collection step 3 suddenly stopped working

For many weeks my data collections from my database instace have been uploading to my MDW server. Suddenly step 3 of the Server Activity Collector has stopped working giving the following error:

Job Name          DataCollector Server Stats Coll n Upload
Step Name         collection_set_3_noncached_collect_and_upload_upload
Duration          00:00:05
Sql Severity      0
Sql Message ID    0
Operator Emailed            
Operator Net sent           
Operator Paged                
Retries Attempted 0

>Message: Executed as user: domain\_svcAccount. SSIS error. Component name: DFT - Find and save sql text, Code: -1071636471, Subcomponent: LKUP - Look up query text on target server , Description: SSIS Error Code DTS_E_OLEDBERROR. >An OLE DB error has occurred. Error code: 0x80040E14. An OLE DB record is available. >Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80040E14 Description: "The handle that was passed to dm_exec_sql_text was invalid.". >SSIS error. Component name: DFT - Find and save sql text, Code: -1071611309, Subcomponent: LKUP - Look up query text on target server , Description: OLE DB error occurred while fetching parameterized rowset. Check SQLCommand and SqlCommandParam properties. SSIS error. Component name: DFT - Find and save sql text, Code: -1073450974, Subcomponent: SSIS.Pipeline, Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "LKUP - Look up query text on target server" (2) failed with error code 0xC0208253 while processing input "Lookup Input" (16). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure. >The master package exited with error, previous error messages should explain the cause. >Process Exit Code 5. The step failed. Has anyone encountered this error before?