The inbound content file could not be moved (renamed) to its destination content folder. There are several possible reasons for the failure: 1. The destination file was already present, had zero length, and could not be deleted. 2. The destination file was already present, but its length did not match the file to be renamed, and it could not be replaced. 3. The file might contain fixed content that was already migrated and deleted. If the error does not occur again, then the issue was resolved by Content Engine.
Namespace:
FileNet.Api.Exception
Assembly:
FileNet.Api (in FileNet.Api.dll)
Visual Basic (Declaration) |
---|
Public Shared ReadOnly CONTENT_FCA_UNABLE_TO_RENAME_FILE As ExceptionCode |
C# |
---|
public static readonly ExceptionCode CONTENT_FCA_UNABLE_TO_RENAME_FILE |
Visual C++ |
---|
public:
static initonly ExceptionCode^ CONTENT_FCA_UNABLE_TO_RENAME_FILE |
JavaScript |
---|
FileNet.Api.Exception.ExceptionCode.contenT_FCA_UNABLE_TO_RENAME_FILE |