You may experience errors executing both advanced and quick search in Summation 5.6.X. This can be caused by creating custom fields that have the same name as the pre-defined Summation fields.
The following pre-defined field names exist in Summation Pro 5.6.1:
- 8.3Name
- AccessedDate
- AccessedDate(FAT)
- ActualFile
- AlternateDataStreamCount
- Application
- Archive
- ArchiveType
- AttachDocIDs
- Attachment
- Author
- Authors
- BCC
- BadExtension
- BatesNumber
- BegAttach
- BegDocID
- CC
- CO Comments
- CO Files
- COAssignedTo
- COBeginDate
- COCreator
- COEndDate
- COImpact
- COIsInReport
- COMaterial
- COParent
- COStatus
- COType
- COUser
- Carved
- Case Organizer
- ChiSquaredErrorPercent
- Cluster Topic
- ClusterId
- CodingLog
- Comment
- Container
- ConversationIndex
- ConversationTopic
- CreatedDate
- DataSource
- DeDuplicateType
- Decrypted
- DecryptionKeyType
- Deleted
- Deponent
- DepositionDate
- DocDate
- DocID
- DocType
- EmailBodyMd5Hash
- EmailDirectAttachCount
- EmailFile
- EmailHeader
- EmailMd5Hash
- EmailMessage
- EmailThreadID
- Encrypted
- EndAttach
- EndDocID
- Endorsement
- Entropy
- EntryID
- EvidenceID
- ExhibitCount
- Extension
- FSId
- FileClass
- FileType
- FilenameAccessedDate
- FilenameCreatedDate
- FilenameMFTChangeDate
- FilenameModifiedDate
- FlaggedIgnorable
- FlaggedPrivileged
- Folder
- FolderNameID
- From
- FromEmail
- FromFreeSpace
- FromMSOffice
- FromRecycleBin
- GeoTagAreaCode
- GeoTagCity
- GeoTagCountryCode
- GeoTagMetroCode
- GeoTagPostalCode
- GeoTagRegion
- GeoTaggingLatitude
- GeoTaggingLongitude
- GraphicFile
- HasTrackChanges
- ImagePageCount
- Importance
- Indexed
- InternetMessageID
- Is Representative Topic
- IsHidden
- IsNotKFFIgnoreOLESubs
- IsNotKFFIgnoreOLESubsDups
- Issues
- KFFGroupName
- KFFHashFileID
- KFFHashType
- KFFSet
- KFFSetID
- KFFStatus
- KFFVendor
- Keywords
- Labels
- Language
- LastModifiedDate
- LastUpdated
- LineNumber
- LinkedDocIDs
- LogicalSize
- MD5Hash
- MFTChangeDate
- Media
- Mentioned
- Metadata
- Note
- NoteDate
- OLESubItem
- ObjectID
- ObjectName
- ObjectSubType
- ObjectType
- OriginalFileName
- OriginalFileType
- PSTFilePath
- PSTStoreID
- ParentDocID
- ParentID
- Path
- People
- PeopleEmailAddress
- PeopleFirstname
- PeopleIsDeponent
- PeopleIsOrganization
- PeopleLastname
- PeopleParent
- PeoplePlaysKeyRoleInCase
- PeopleRole
- PeopleType
- PhysicalSize
- ProductionDocID
- Read
- ReadOnly
- ReceivedDate
- Recipients
- RegistryFile
- Repository Author
- Repository BaseType ID
- Repository Content Type
- Repository Created By
- Repository Description
- Repository Document ID
- Repository Editor
- Repository Last Modified By
- Repository ObjectType ID
- Repository Owner
- Repository Title
- Repository Version
- Repository Version Series ID
- RepositoryContent MimeType
- ReviewDescription
- ReviewResponsiveness
- SHA1Hash
- SHA256
- Sensitivity
- SentDate
- SetBy
- Source
- Source ObjectID
- StartCluster
- Subject
- Summary
- System
- Thumbs.dbFile
- Title
- To
- UUID
- Unsent
- UserDecrypted
- Volume
As a best practice, AccessData recommends appending a prefix to all user generated fields, avoiding the chance of collision. E.g. name your custom field "cVolume", rather than "volume"