Description of Issue
How to clear java and empirecache folders from a users workstation when:
- Errors received when attempting to launch the CM Full client:
...is locked by something else. Please close other Java processes that may be holding your empirecache. - Errors received within the full client when completing certain processes such as batch scanning:
An unexpected error has occurred. Java heap space
Self-suppression not permitted caused by java.lang.OutOfMemoryError: Java heap space - The empirecache folder itself has grown in size or is outdated based on a Content Manager upgrade.
Context
- Content Manager
- CM
- CM Full Client
Cause
Occasionally the CM Full Client will hang up or get stuck on certain processes, such as batch scanning.
This may be an indication that the background cache used by Content Manager on the workstation needs to be cleared in order for the process to complete.
Resolution
- Clearing empirecache:
- You will need to log out of the CM Full Client before completing these steps
- On your PC, navigate to File Explorer > C:\Users\yourusername
- Right-click on the empirecache folder
- Click Delete
- Right-click on the Recycle Bin icon on the desktop and click Empty Recycle Bin
- Clearing Java Cache:
- If you are using the Jlink option to launch CM, this step is not necessary
- This is only necessary if you are using the Webstart option to launch the CM Full Client, which uses Java.
- On your PC > Start
- Search for and open the Control Panel > Programs > Java > Settings (under General tab)
- Select Delete Files
- Leave all pre-checked options selected
- Click OK
- Right click on the Recycle Bin icon on the desktop and click Empty Recycle Bin
- You will need to launch the CM Full Client as a fresh link: How to Access and Launch the CM Full Client
Additional Information
If the problem continues after completing the above steps try launching CM with the 64-Bit version: How to launch CM Full Client 64-Bit version
Add Comment