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

Article:TECH53242  |  Created: 2007-01-22  |  Updated: 2013-07-05  |  Article URL http://www.symantec.com/docs/TECH53242
Article Type
Technical Solution

Product(s)

Issue



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


Supplemental Materials

Value1099311
Description

Checksum value not being generated resulting in all of the files getting the same name


Legacy ID



290765


Article URL http://www.symantec.com/docs/TECH53242


Terms of use for this information are found in Legal Notices