In EmailXtender, I have the message RECORD FAILED in field Status in Index windows. What mean this message and how I can solve this?? I tried to Re-index All Folder, and the problem still.
Record failed usually means that the process which groups and stores individual messages to a container (.emx file) has failed and this should be unrelated to Indexing. Although, some failures can cause incomplete indexes.
Side note: Often "Container", "Volume" and "EMX file" are interchangeable terms in the world of EmailXtender.
The system will take messages until a target size is reached as defined by your maximum container size. For example, if my container size was 80MB, the system would assign messages to a container until the n-th message where the container is now >= 80 MB. At this time the container will automatically attempt to close (or "record") which simply means no new messages will be assigned and this group of messages will be written into a single .EMX file. This closure process can also be issued by the user via the EX Administrator (right click -> Close) or if the container has not had new mail come in for ~5 days.
If the recording process fails, you'll have a Record Failed status. This can happen for a number of reasons, here are some common examples: - The system is interrupted during the recording process (service killed, reboot) - Another process locks a message file needed for this container, example: Antivirus or backup has a file lock on the file at the time we're recording. - One of the message files needed for this container is missing (data loss due to disk issue, unexpected reboot, file quarantined by AV, etc).
To fix a Record Failed I would suggest: - First: Open the EX Administrator and attempt to close the file container again. The container should go into a "Record Pending" then "Recording" state again. If it fails continue on... - Check to see if this is a false-postive. I've seen Admin get out of sync with reality in that it will report that the container has failed to record, when in fact it has written to disk. Check the location where containers are stored and search for the name with the .EMX extention on the end. If it's there you'll also want to check the EmailXtender\EmailVault_Index_Archive\StorageDir\YEARMONTH and verify there is not a folder left over with the same name and .xvlt files. If this is the case it's very likely that the container actually sucessfully recorded but the state shown in the Administrator is incorrect. Contact support for instructions to verify this and fix the status. - There's a utility called managexvlts which can be run against the volume's storagedir folder. Usually I run this as "managevlts -v -s -d PATH-TO-STORAGEDIR" where PATH-TO-STORAGEDIR is the path to the container's folder in the storagedir folder. This will check each message and verify that it's present in the MsgCenter folder. If you encounter problems or files are reported as missing I would suggest that you contact support and they can assist you in attempting to locate these files or close the volume without them.
Kenta
11 Posts
537
2
Posted December 28th, 2006 07:00
Side note: Often "Container", "Volume" and "EMX file" are interchangeable terms in the world of EmailXtender.
The system will take messages until a target size is reached as defined by your maximum container size. For example, if my container size was 80MB, the system would assign messages to a container until the n-th message where the container is now >= 80 MB. At this time the container will automatically attempt to close (or "record") which simply means no new messages will be assigned and this group of messages will be written into a single .EMX file. This closure process can also be issued by the user via the EX Administrator (right click -> Close) or if the container has not had new mail come in for ~5 days.
If the recording process fails, you'll have a Record Failed status. This can happen for a number of reasons, here are some common examples:
- The system is interrupted during the recording process (service killed, reboot)
- Another process locks a message file needed for this container, example: Antivirus or backup has a file lock on the file at the time we're recording.
- One of the message files needed for this container is missing (data loss due to disk issue, unexpected reboot, file quarantined by AV, etc).
To fix a Record Failed I would suggest:
- First: Open the EX Administrator and attempt to close the file container again. The container should go into a "Record Pending" then "Recording" state again. If it fails continue on...
- Check to see if this is a false-postive. I've seen Admin get out of sync with reality in that it will report that the container has failed to record, when in fact it has written to disk. Check the location where containers are stored and search for the name with the .EMX extention on the end. If it's there you'll also want to check the EmailXtender\EmailVault_Index_Archive\StorageDir\YEARMONTH and verify there is not a folder left over with the same name and .xvlt files. If this is the case it's very likely that the container actually sucessfully recorded but the state shown in the Administrator is incorrect. Contact support for instructions to verify this and fix the status.
- There's a utility called managexvlts which can be run against the volume's storagedir folder. Usually I run this as "managevlts -v -s -d PATH-TO-STORAGEDIR" where PATH-TO-STORAGEDIR is the path to the container's folder in the storagedir folder. This will check each message and verify that it's present in the MsgCenter folder. If you encounter problems or files are reported as missing I would suggest that you contact support and they can assist you in attempting to locate these files or close the volume without them.
Hope this information helps,
-Kenta