Dimensions maintains a checksum for each file revision stored. Sometimes, as a result of "corrective scripting" or perhaps from using a migration tool, some files are loaded with a -1 which acts as a wildcard for the checksum. The project and workset compare functions require an actual checksum to perform their work and thus this error message is generated:
Dimensions uses it's own checksums to ensure that items have changed before allowing checkins/updates. This same mechanism can be used to verify that items have also been checked out correctly.
Please gather any applicable information from the list below and contact Dimensions Support for help with this error message. What you need to troubleshoot:
Please gather any applicable information from the list below and contact Dimensions Support for help with this error message. What you need to troubleshoot:
Please gather any applicable information from the list below and contact Dimensions Support for help with this error message. What you need to troubleshoot:
Checksum file content Help: Select this option if you want Dimensions CM to also use the file checksum to detect whether files in the work area have changed when the timestamps are the same. Testing these two options found that if option 1 is selected Dimensions doesn't find a conflict even though the modification time is different between the file in Dimensions and the one in the work area (newer).
3) If for some reason the above roles cannot checkout the item, the followign script can be ran to change the checksum values to -1. This will cause Dimensions to recalculate the checksum when teh item is next checked out or browsed. Update item_catalogue ic Set ic.checksum=-1, ic.file_length=-1
FI "QLARIUS:T BAT.A-PC;rep1#1" /USER_FILENAME="pc-12dot1::c:\work\t.bat" /NOEXPAND /NOOVERWRITE Get Item - Warning: Checksum for the gotten file ("t.bat") is different from the checksum recorded when the file was last placed in the Dimensions library.
