RSA File Security Manager (FSM)
Microsoft Windows Server 2003 SP1
The folder in this case is not in use. Data in one folder called c:|Private, and Test data in c:\test-private. Can not encrypt c:\Private folder.
In FSM 2.1.0.9, there is a known issue that Security Officer can not encrypt a folder containing ReadOnly files/folders and is addressed in v2.2 and higher. Contact RSA Customer Support for latest version 2.2 of FSM.
Alternative workaround:
- Encrypt an empty folder e.g. c:\private\test\
- Copy the files and folder from c:\private\accounts_public\ to the encrypted folder i.e. c:\private\test\
- Rename the source folder c:\private\accounts_public\ to desired name and rename the encrypted folder (c:\private\test\) to c:\private\accounts_public\.
- Refresh the Adapter Manager Console using Refresh button far right in the right pane.
- User can delete the renamed source folder (unencrypted) after confirming that all data is intact in encrypted folder c:\private\accounts_public\
Related Articles
'Unable to encrypt data as this certificate is not meant for Encryption' or 'Unable to sign ...' 11Number of Views FIM - Null pointer exception -'error encrypting the name id unable to encrypt' 19Number of Views "NoClassDefFoundError" error when attempting to run RSA Authentication Manager Bulk Administration (AMBA) 35Number of Views Error when going into the Event Viewer 23Number of Views Error "A newer version of Microsoft Visual C++ 2010 Redistributable has been detected on the machine" while installing Tok… 16Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide Troubleshooting RSA MFA Agent for Microsoft Windows How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to recover the Application and AFX after an unexpected database failure in RSA Identity Governance & Lifecycle