A SavesetID that contains a checksum high value of 0, may result in multiple .dvs files having the same name.

Problem

A SavesetID that contains a checksum high value of 0, may result in multiple .dvs files having the same name.

Solution

SavesetId's that are generated with a checksum high value of 0, and do not have a unique time stamp may appear as the same item, although the messages may not be the same item.

Example of SavesetId's that do not have a unique time stamp:

000000000000000~200705220622190000~01.DVS
000000000000000~200705220622190000~02.DVS
000000000000000~200705220622190000~03.DVS

Example of SavesetId's that have a unique time stamp:

000000000000000~200705220622190000~01.DVS
000000000000000~200705220623140000~01.DVS
000000000000000~200705220624110000~01.DVS

Issues noticed when this occurs:

- Searching on items by using the SID for SavesetId's that do not have a unique time stamp, may return more results than are expected.
- This can cause issues with collections, if there are more than 32767 SavesetId's with the same name as the largest value a Unique ID can be is 32767.


Solution:

This issue has been addressed as part of the following release:


Enterprise Vault 8.0 - Release Details
http://www.symantec.com/docs/TECH57823


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)