Article - CS279877
Resynchronizing with restoreTimestamp can fail after turning on AlwaysStoreWorkingArchiveIDInSandbox=true in Integrity Lifecycle Manager
Modified: 22-Jan-2019
Applies To
- PTC RV&S (formerly Integrity Lifecycle Manager) 10.9 to 12.5
Description
- Resynchronizing with restoreTimestamp can fail after turning on AlwaysStoreWorkingArchiveIDInSandbox=true in Integrity Lifecycle Manager
- With the Client default "Restore Timestamp" set and locked in the Source policies, after turning on AlwaysStoreWorkingArchiveIDInSandbox=true, running "si resync --overwriteunchanged" sometimes gives the error message:
- 2018-02-09 11:40:36,568 (Thread-32[null]) ERROR(10) mks.si.api.SIException: mks.si.api.SIException: MKS5613057: Archive path/Archive ID is null, unable to store working archive ID in sandbox. Please contact your Integrity Administrator.
at mks.si.api.WorkingFileMetadataCacheImpl.putWorkingObjectMetadata(WorkingFileMetadataCacheImpl.java:678)
at mks.si.api.DelegateWorkingFileMetadataCache.putWorkingObjectMetadata(DelegateWorkingFileMetadataCache.java:225)....
- 2018-02-09 11:40:36,568 (Thread-32[null]) ERROR(10) mks.si.api.SIException: mks.si.api.SIException: MKS5613057: Archive path/Archive ID is null, unable to store working archive ID in sandbox. Please contact your Integrity Administrator.
This is a printer-friendly version of Article 279877 and may be out of date. For the latest version click CS279877