IBM FileNet P8, Version 5.2.1

Starting FileNet Deployment Manager with the -clean option

If an unexpected error occurs when you try to do actions such as exporting the assets in an export manifest file, you might need to start FileNet® Deployment Manager with the -clean option.

An unexpected error might occur when you do actions such as exporting the assets in an export manifest file. This error can be caused by an upgrade of FileNet Deployment Manager to match a new version of Content Platform Engine. After the upgrade, artifacts such as residual modules might remain in the cache that is maintained by the environment for FileNet Deployment Manager.

If this type of error occurs, you can start FileNet Deployment Manager with the -clean option to remove the old artifacts from the cache. The -clean option is available when you start FileNet Deployment Manager from a command prompt. To start FileNet Deployment Manager with this option, enter the following command from the directory where FileNet Deployment Manager is installed:

deploymentmanager.exe -clean

Attention: The use of the -clean option forces the reloading of multiple modules. Therefore, the startup process for FileNet Deployment Manager might take more time with this option. Although you can add the -clean option to the Target property of the FileNet Deployment Manager shortcut in the Windows Start menu, this action is not recommended. The use of the -clean option to clean the cache is necessary only the first time that FileNet Deployment Manager is started after an upgrade.