RSA DLP Root Enterprise Coordinator (REPC) rejects the patch file pushed by the Enterprise Manager with 400 Bad request
Originally Published: 2015-11-28
Article Number
Applies To
RSA Product/Service Type: Endpoint, Root Enterprise Coordinator (REPC), Enterprise Manager
RSA Version/Condition: 9.6 SP2
Platform: Windows
O/S Version: 2003 SP2, 2008, 2008 R2, 2012
Issue
Enterprise Manager logs shows the following error:
09 Oct 2015 08:40:10,315 | ERROR - HttpFilePublisher.postFile(93) | Could not write file at url /rsadlp/rest/v1/files/agent/agent_patch_msp/20140616123703 400: Bad Request
09 Oct 2015 08:40:10,315 | ERROR - HttpFilePublisher.postFile(102) | Could not write file at url /rsadlp/rest/v1/files/agent/agent_patch_msp/20140616123703
09 Oct 2015 08:40:10,315 | ERROR - AbstractPackageBuilder.synchronizePackageContents(320) | Exception while publishing package Could not write file at url /rsadlp/rest/v1/files/agent/agent_patch_msp/20140616123703
The error indicates that the Enterprise Manager is trying to push a bad file and this can occurs when non-valid file is present in the agent patch directory on Enterprise Manager such as MSI file(s). These valid files should only be present in the agent patch directory (e.g. agent_patch_options file and MSP extension file(s))
Tasks
- Login to the Enterprise Manager server and check the directory RSA\patches\agent within TEM-HOME directory, ensure there are only agent_patch_options file and MSP extension file(s).
- Ensure there are no MSI files present under this directory. Root Enterprise Coordinator (REPC) does not accept patches pushed with an MSI extension. If there exists any MSI file in that directory, remove that file from that directory.
Resolution
- After making sure that there is no MSI file present in the RSA\patch\agent directory, take the back up of the database.
- Run the below 4 database queries on Enterprise Manager database. These 4 database queries removes the existing patch configuration from the Enterprise Manager.
delete from MF_PACKAGE_MANIFEST_FILE_COMPONENTS where FILE_COMPONENT_ID in (select FILE_COMPONENT_ID from MF_FILE_COMPONENT where name='agent_patch_msp'); delete from MF_PACKAGE_MANIFEST_FILE_COMPONENTS where FILE_COMPONENT_ID in (select FILE_COMPONENT_ID from MF_FILE_COMPONENT where name='agent_patch_options'); delete from MF_FILE_COMPONENT where name='agent_patch_msp'; delete from MF_FILE_COMPONENT where name='agent_patch_options'
- After running the above 4 queries, click on the deploy agent patch again. Enterprise Manager will generates a new patch configuration to be pushed to the Root Endpoint Coordinator (REPC).
Related Articles
Blank lines appear in RSA Identity Governance and Lifecycle reports when viewed through a browser or exported via HTML format Number of Views 'UT000047: The number of parameters exceeded the maximum of 1000' error when adding User Attributes in RSA Identity Govern… Number of Views RSA Authentication Manager 8.7 SP1 Azure Virtual Appliance Getting Started Number of Views RSA Authentication Manager 8.7 SP2 Azure Virtual Appliance Getting Started Number of Views Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201… Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?
